The System File Checkerallows an administrator to scan all protected files to verify their versions. If the System File Checker detects that a file has been overwritten, it retrieves the correct version of the file from the cache folder (% Systemroot% \ System32 \ Dllcache) or from the Windows installation source files, and then replaces the incorrect file. To run the System File Checker, you must login as an administrator or a member of the Administrators group. If the cache folder is damaged or unusable, you can use the sfc / scannow.

The sfc / scannow (System File Checker) examines the integrity of all protected system files and replace damaged, altered or damaged versions with the correct versions (if possible) but we see together how to proceed:

1. Open a command prompt with administrative privileges, type sfc / scannow followed by Enter.

NOTE: This may take a few minutes.

2.When the scan is complete, Windows will return a message integrity; If everything is successful the message back "No violation of integrity found."

NOTE: If the command sfc / scannow unable to resolve the problem, then you can groped perform a system restore using a previous restore point that we return the error log file.

3. To view and analyze the files can take different paths: the action is being felt both in the C: \ WINDOWS \ logs \ cbs \ CBS.log, but to make things easier we can see only the specific items of SFC with [SR] tag in the file CBS.log. This can be useful to show what files SFC could not automatically correct if you want to manually intervene.

4. Open a command prompt with administrative privileges and type:
findstr / c:"[SR]"% windir% \ logs \ cbs \ cbs.log>% userprofile% \ Desktop \ sfcdetails.txt followed by Enter, in seconds sfcdetails.txt file will appear on your desktop with the details of the SFC will scan CBS . log.

NOTE: A avolta checks are completed, we can delete the file.

MORE INFORMATION
1 Official Website		Official Site 2