Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
SFC /scannow
DISM /online /cleanup-image /restorehealth
Windows Resource Protection found corrupt files and successfully repaired them.Hi
Something to try;
You can run the SFC /scannow command from any console, including the command prompt, PowerShell, or Windows Terminal. Open one of these as Admin and type or past that command and press enter, then wait for it to finish.
Then,if it reports problems, run the following command:
DISM /online /cleanup-image /restorehealth
Type (or copy and paste) the following command:
Code:SFC /scannow
Were there any errors?
When completed, type (or copy and paste) the following command:
Code:DISM /online /cleanup-image /restorehealth
Yes possibly, but I don’t.Windows Resource Protection found corrupt files and successfully repaired them.
Shouldn't I check health before?
DISM /online /cleanup-image /checkhealth
No component store corruption detected.
The operation completed successfully.
I think I ran sfc a while ago as well and then it also found errors and repaired them.
TheShouldn't I check health before?
DISM /online /cleanup-image /checkhealth
Dism /Online /Cleanup-Image /CheckHealth
command uses Windows Update to see if the system files are healthy, repairable, or non-repairable. Repair a Windows ImageDism /Online /Cleanup-Image /RestoreHealth
command also will report whether it detected corruptions so if it turns out that it did, it will report whether it was able to successfully repair them. The difference is that, if you're interested in trying to investigate what's caused the corruptions, then you can't always do these kinds of investigations after the corruptions have already been repaired. But then, in a lot of cases you don't really need to investigate, as you can just blame Windows instead. Windows is, and always has been, a funny OS above anything else so, the day when funny OS stops being funny, prepare for cataclysmic event.sfc /scannow
command didn't detect any corruptions, it means that there aren't any, but sometimes it can happen that there still are, in which case Dism /Online /Cleanup-Image /RestoreHealth
should do the trick. Only if problems like this persist after, that's when other troubleshooting methods such as, e.g., trying to repair Windows via an in-place upgrade will typically be recommended next. Some also recommend to just skip the sfc /scannow
simply for the fact that it doesn't always find the corruptions if present. Even so, sfc /scannow
takes much less time to finish compared to Dism /Online /Cleanup-Image /RestoreHealth
so, more often than not, sfc /scannow
helps to save valuable time still nevertheless, i.e. due to the simple fact that it usually is already sufficient to remedy the problem.PS C:\WINDOWS\system32> DISM /online /cleanup-image /restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.22621.2792
Image Version: 10.0.22631.3296
[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
PS C:\WINDOWS\system32>