08-23-2013, 05:14 PM
- Microsoft Support
Join Date: Jun 2008
OS: XP, Vista, Seven, & a whole host you would never have heard of.Windows Ten 64 bit Pro
Hi, the RE (repair your computer) option is installed with Seven (not so Vista), boot to safe mode advanced and select the "repair your computer" option go to command prompt to run Tomken's cmd. OR this is what I would do:-
Originally Posted by jenae
Hi, the question of running a sfc gets asked quite often, it is confusing especially if you are faced with the prospect that it finds errors and was unable to repair them.How do you find these errors?
When sfc completes it gives a summary it will say it found no integrity violations (corrupt files), you are good to go. It might say it found integrity violations (corrupt files) and repaired them, you are good to go. If it say's it found integrity violations (corrupt files) and was unable to repair them, you might have a problem (not all errors are cause for concern, I have modified my system and sfc always finds problems, when you check them they are benign, as far as effecting the system goes) This does not mean errors should not be checked they may well cause problems.
First problem is the Log cbs, it's used for other purposes (The Windows Modules Installer service also writes to the CBS.log file. The Windows Modules Installer service installs optional features, updates, and service packs) and can be quite large, so it's best if you clear the log before running sfc.
Go to start search and type:- cmd, right click on the returned cmd.exe and select "run as administrator" at the prompt type:-
CD %windir%\logs\CBS (press enter)
DEL *.* (press enter) press Y at the are you sure prompt.
Exit (press enter) cmd prompt will close.
Open cmd prompt again (as admin) as shown.At the prompt type:-
Be patient can take awhile when finished if you have no corruption or the corruption has been repaired, you can simply continue using your computer. If you have a message that it found errors and was unable to repair them, OR you just want to view the logs, open a cmd as admin (as shown):-
To read the log:- at the prompt (copy paste)
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log > 0 & notepad 0
(press enter), the log will open in notepad.
To read the log with only the errors showing:- (copy paste)
findstr /c:"[SR] Cannot" %windir%\logs\cbs\cbs.log >0 & notepad 0
(press enter) You can post this notepad outcome here for us to assist you.