This pattern usually means the underlying Windows image or component store still needs repair, even if DISM /ScanHealth and DISM /RestoreHealth completed without reporting an error.
Use this sequence from an elevated Command Prompt:
- Run:
DISM.exe /Online /Cleanup-Image /RestoreHealth - After it completes, run:
sfc /scannow - Restart Windows.
- Run
sfc /scannowagain and check whether it still reports the same files.
If SFC continues to report corruption after restart, use a repair source instead of Windows Update:
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess
sfc /scannow
Replace C:\RepairSource\Windows with the actual repair source location.
If the repair source is a WIM file, this form can be used:
DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:c:\install.wim:1 /LimitAccess
sfc /scannow
Important: sfc /scannow must be allowed to reach 100% completion, and the Command Prompt window should not be closed before that.
Expected results:
-
DISMshould report that the restore operation completed successfully. - A healthy result from
SFCis:Windows Resource Protection did not find any integrity violations. - If
SFCstill says it repaired files on every run, the image source used for repair is likely not matching the installed build correctly.
- Use the System File Checker tool to repair missing or corrupted system files | Microsoft Support
- Use the System File Checker tool to repair missing or corrupted system files | Microsoft Support
- Repair a Windows Image
- Windows 11
- Sfc scan now found corrupted files and doesn’t fix after reboot - Microsoft Q&A