How to Fix Corrupted System Files with SFC /scannow in Windows
SFC /scannow is a common command line of System File Checker that you can use in Windows OS to scan for and restore missing or corrupted Windows system files. When you encounter some annoying Windows system issues like blue screen of death (BSoD), it is better to use the SFC command to repair the specific faulty files that cause the problem.
Today I am going to talk about how to run SFC /scannow command in Windows 10, 8, 7, Vista and XP.
How to Run SFC /scannow or System File Checker in Windows 10, 8.1, 8, 7, Vista and XP
SFC command Windows XP is integrated with real-time file protection, called Windows File Protection (WFP) and can be used to check specific folder paths, while in Windows Vista and onwards, SFC /scannow is integrated with Windows Resource Protection (WRP). But despite the differences, when you run the SFC command, it will automatically replace broken files with the correct one.
Run SFC /scannow in Command Prompt as Administrator
- Open Command Prompt (Admin) in your Windows. (Note: Except for Windows XP, you can easily launch Command Prompt via the searching box.)
- Type into the command line SFC /scannow.
- Hit the key Enter.
Then the System Files Checker will scan all protected system files. If there are corrupted files, it will replace them with a cached copy located in a compressed folder. It will take some time to do that and you need to wait until this process is finished.
Common Messages You May Receive after Running SFC Command
When System Files Checker completes its work, the scan result will be shown. You’ll see a message that tells about the scanning.
“Windows Resource Protection did not find any integrity violations.”
If everything is fine in your Windows computer, this message will show on the dialog box. You can close it and continue to fix your system issue with other methods.
“Windows Resource Protection found corrupt files and successfully repaired them.”
This means System File Checker has detected and repaired the corrupted system files during the running of SFC /scannow command. If you care about the details, go to view them via the given path or in Event Viewer.
This related post may also interest you: How to Enter Event Viewer in Windows 10, 8, 7, Vista, XP.
“Windows Resource Protection found corrupt files but was unable to fix some of them.”
If you receive this message, you can view details via the given path and find the corrupted files, and then replace them with the right copy ones. Also, you can enter the safe mode, and then run the sfc /scannow command again to repair the files.
It is better to use SFC /scannow command line to fix the blue screen bug check code listed below:
0x0000003B System_Service_Exception Error
Driver_Power_State_Failure Error in Windows
Blue Screen Caused by Internal_Power_Error
Thank you for visiting my blog. Hope this article can be a reference for you to run SFC /scannow in your Windows computer. If you have any question on this topic, comment below please. Hope you continue to have access to this Blog as well as provide support.
I truly wanted to type a small word to appreciate you for all the awesome items you are giving on this website. My time consuming internet look up has at the end of the day been recognized with pleasant facts and techniques to exchange with my two friends. I would say that most of us visitors actually are undoubtedly lucky to exist in a remarkable community with many outstanding individuals with interesting solutions. I feel rather lucky to have discovered your entire web page and look forward to so many more thrilling minutes reading here. Thanks again for everything.
I find your blog very much useful to me because here i find some of the good information which i face daily in my life. So, here i am easily finding solutions for it without being searched for long time. Thank you keep it up.
sfc found corrupt files but “was unable to fix”.
Got a different message than the ones listed above. First it said that verification was 100% complete. Then, “Windows Resource Protection could not perform the requested operation.”