Short answer
Run PCHealthLab with the System Integrity & Logs area and press ANALYZE. The program checks the system files and, if it finds corruption, offers the Run SFC and DISM repair fix. One click on Fix ▸ next to the finding (or Run ▸ in the Fix Engine) repairs the Windows component store first and then the files themselves, with progress in percent.
Step by step
-
Run PCHealthLab
The program asks for administrator rights at start. Without them neither checking nor repairing system files would work.
-
Check system integrity
Tick System Integrity & Logs. Quick test checks the system files with DISM, Long test also runs an SFC check. Then press ANALYZE.
-
Run the repair
When the check finds corruption, the finding has a Fix ▸ link in the Fix column. Clicking it starts Run SFC and DISM repair. The fix is rated Caution, so the program asks first.
-
Wait for it to finish
The repair runs in the right order: DISM first repairs the component store that SFC takes healthy copies from, and only then SFC repairs the corrupted files. You see the progress in percent. It can take tens of minutes.
-
Restart and check again
After a restart run the analysis once more. If integrity is fine, the finding disappears.
Why DISM first and SFC second
sfc /scannow replaces corrupted system files with healthy copies from the Windows component store. If that store is corrupted too, SFC has nowhere to take them from and the repair fails. That is why DISM /Online /Cleanup-Image /RestoreHealth runs first to repair the store, and SFC only afterwards. PCHealthLab does both, in that order, for you.
Things to keep in mind
- The repair changes the system. Diagnostics alone change nothing, and fixes run only when you click.
- When repairing the store, DISM usually downloads healthy files from Windows Update, so the computer should be online.
- If files keep getting corrupted, the cause is usually elsewhere: a failing drive or faulty memory. Check them in the Storage & S.M.A.R.T. and RAM & Memory areas.
- To see what exactly is going wrong in the system, go through the logs in EventAnalyzer. It proposes fixes with a complete script for its findings and starts each with a restore point.