ghostlight
-
Posts
48 -
Joined
-
Last visited
-
Just ran another sfc /scannow. Results: Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection did not find any integrity violations. So, it appears everything is good. Browser functioning good. Last things could be helping me to speculate why I couldn't get check disk to function even after your implementations.
-
Okay. Just rebooted computer. It finally gave me this msg during startup "scanning and repairing drive" or something to that effect. Should I run sfc /scannow again, or next step? A log I should post?
-
Here is what happened after the sfc /scannow: Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection found corrupt files and successfully repaired them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios. The system file repair changes will take effect after the next reboot. Should I post this CBS log? Reboot?
-
Awaiting completion. Did any of the stuff I did in post #55-57 help? I'm curious if that easeus thing did anything. I already removed it from my computer since I don't need it anymore.
-
Okay. Running it. I don't know what you mean from an elevated command prompt. I interpreted want you meant as run sfc /scannow under command prompt admin as I had done previously.
-
Typed in what you stated in post #60. Got the following: Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image Version: 10.0.16299.248 [==========================100.0%==========================] The restore operation completed successfully. The operation completed successfully.
-
Working on it.
-
After doing what you outlined in #58, I got this message: Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image Version: 10.0.16299.248 The component store is repairable. The operation completed successfully.
-
From the above post in #56, I followed method #1 and that did not find any bad sectors or issues.
-
I'm following step 1 here to check disk: https://www.easeus.com/partition-master/chkdsk-not-working.html The scan disk that I have run still seems like that is not working. Will have to look for the work around on that one.
-
I can't get command prompt to check disk, but perhaps you can give another option. However, I did right click on my C drive, go to tools, error checking and scanned the drive that way. No errors found. I am also trying to run a sfc /scannow.
-
I tried everything a 2nd time. Altered boot execute, run check disk, reboot, and nothing. Checked boot execute, and it was changed again to what I previously posted.
-
So after altering the boot execute to what you stated, I followed the instructions as outlined to run the check disk. Rebooted computer but nothing. I checked the boot execute again and it showed: autocheck autochk /p \??\C: autocheck autochk * I wondered why it automatically went back to that.
-
So, Slimware Utilities is no longer found, although when searching my C drive in File Explorer I guess it finds where it used to be C:\Users\Brian\App Data\Local. I click on that, but it is unavailable showing it might have been moved or deleted. So, is this just a leftover folder of it? Also, I altered my boot execute and will now try the check disk.
-
Currently, under Boot Execute this is what is shown: autocheck autochk /r \??\C: autocheck autochk * Should I change it to just autocheck autochk * Is doing all this to be able to run the check disk /r going to fix the corrupt files but risk losing, not being able to access, or open any data that I currently have? Hypothetically speaking it check disk found and fixes these corrupt files/data, doesn't it delete, erase, or make this data obsolete?