RECOMMENDED: Click here to fix Windows errors and optimize system performance
To date, Windows 10 users have noticed that the sfc scannow function no longer works and indicates that it has found damaged Windows Defender PowerShell files but has been unable to repair them.
The Windows System File Checker tool, commonly called SFC, has a /scannow argument that checks the integrity of all protected Winodws system files and fixes any problems found.
Since this morning, users have been reporting in a thread of wildersecurity.com that the program, when they launch sfc /scannow, states that “Windows Resource Protection found corrupted files, but could not repair some of them”. I was also able to reproduce this problem on a virtual machine where Windows Defender was configured as the main antivirus program.
Sfc Scannow does not work under Windows 10
Whenever you encounter problems running the SFC utility, the first thing we recommend is to restart and execute the sfc /scannow command. This is likely to help if a conflict in the boot service causes the problem.
Check that the Windows module installation program is running.
- The TrustedInstaller service has full access to Windows Resource Protection (WRP) files and registry keys, and this service must be executed to recover missing or corrupted WRP resources.
- The TrustedInstaller service starts on demand when the System File Checker is running. Let’s make sure that the TrustedInstaller service (Windows Modules Installer) is disabled.
How do it:
- Press Windows + R, type services.msc and ok.
- Scroll down and search for the Windows Modules Installer service.
- Right-click on the Windows Modules Install service and select Restart,
- Right-click again on the Windows Modules installer and select Properties.
- Under Start Type, select Automatic.
- Click on Apply and OK,
- Do the same with Volume Shadow Copy and the Superfetch service.
- Restart the windows and run the command again to check the system file, sfc /scannow.
How can I correct the SFC/Scanow error?
The error must come from 1,297,823.0 and not from Windows 10 1903 KB4507453 Cumulative Update or Windows 10 KB4507469 Update.
In fact, as some users have reported, there are currently some patches for this patch. Below are some of the commands you can try.
• DISM /Online /Cleanup-Image /CheckHealth
• DISM /Online /Cleanup-Image /ScanHealth
• DISM /Online /Cleanup-Image /RestoreHealth
If nothing has worked, consult our detailed troubleshooting guide to find out how to troubleshoot some of the most common SFC errors that can occur on your Windows 10 PC.
Redmond has not yet confirmed the problem.
Microsoft has not provided any information on this unexpected behavior of the cumulative update, and the company still has to detect errors here, so it is difficult to say whether or not it is a widespread problem at this point. However, users who have successfully installed KB4507453 and are then prompted to restart may try to restart the device from Windows Update as this seems to disable repeated behavior for some.
It is not recommended to delete the cumulative update. Because it was released on Tuesday patch, KB4507453 also solves security problems in the operating system and in pre-installed applications, so that a device without the update could remain vulnerable to potential attacks.
RECOMMENDED: Click here to troubleshoot Windows errors and optimize system performance
CCNA, Web Developer, PC Troubleshooter
I am a computer enthusiast and a practicing IT Professional. I have years of experience behind me in computer programming, hardware troubleshooting and repair. I specialise in Web Development and Database Design. I also have a CCNA certification for Network Design and Troubleshooting.