The error displayed in the Command Prompt window also suggests that the user check the log file and display that the log file shows that the hash values of the file members (PowerShell module files) do not match.MicrosoftThe issue was quickly acknowledged on July 16. The company claimed that the SFC function incorrectly marked the Windows Defender PowerShell module file as corrupted, causing this error.
Users will encounter this error on Windows Defender version 4.18.1906.3 and various versions of Windows 10 with versions lower than 4.8.1908.
In an update to its supporting documentation, Microsoft confirmed yesterday that the latest Windows Defender update has fixed a bad error message, and that the SFC feature should now work without any errors.
To fix SFC /scannow failure, you must have Windows Defender version 4.8.1908 or higher installed. After installing the update, Windows 10's SFC feature will no longer incorrectly mark PowerShell files as corrupt. Or you can use the DISM tool in the command prompt to repair the Windows 10 image file:
Dism /online /cleanup-image /restorehealth
Windows Defender updates are automatically installed unless the user manually turns off automatic updates or disables the Windows Update service. The problem is fixed automatically without external intervention. This update has been pushed to all affected versions of Windows 10.