What to do when SFC /scannow found corrupt files but unable to fix them

Andy

Administrator
Creative Team
User ID
1
Joined
7 Jan 2019
Messages
1,134
Reaction score
57
Points
48
So you tried to check and repair your Windows system files using System File Checker utility aka sfc.exe, but then you got the following error message:
Code:
C:\windows\system32>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 but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.


Here's what you can try, open an elevated command prompt again and use the following command:
When you run this command, the Deployment Image Servicing and Management tool make use of the Windows Update to provide the files that are required to fix corruptions.
Code:
PS C:\windows\system32> DISM.exe /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.771

Image Version: 10.0.17763.973

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
PS C:\windows\system32>


Back to the Command Prompt and then rerun the system file checker and see if it can repair the corrupt files now:
Code:
C:\windows\system32>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.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\windows\system32>


That means the system files has been successfully repaired, if you run the SFC again, it will tell that Windows Resource Protection did not find any integrity violations:
Code:
C:\windows\system32>sfc /scannow

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.

C:\windows\system32>
Ultimately, restart your computer, and your issues should be fixed, if they're not, try updating your device drivers as well as upgrading your computer firmware (i.e. BIOS update)

If you find this article useful, feel free to post your comment down below 👇
 
 Short URL:
Back
Top