Microsoft confirms July 9, 2019 Updates breaks sfc in Windows

[German]After Microsoft released its Windows Update for July 9, 2019, the system file checker (sfc) command to repair broken files under Windows finds some damaged files, but can’t fix them. Now Microsoft has confirmed this issue.


Advertising

Windows: July 9, 2019 Updates breaks sfc

In Windows, you can use an administrative command prompt window to check the system for corrupted files. To do this, simply use the command:

sfc /scannow

If the command finds corrupted files, the System File Checker (sfc) should be able to repair them. However, it happens again and again that this repair isn’t successful. And this case happened again, after Microsoft has released the July 9, 2019 updates for Windows. I’ve discussed this issue within the blog post Windows: July 9, 2019 Updates breaks sfc.

Microsoft confirms the issue

Blog Reader EP pointed out within this comment, that Microsoft has confirmed this issue. Within KB4513240 (System File Checker (SFC) incorrectly flags Windows Defender PowerShell module files as corrupted), Microsoft writes:

The System File Checker (SFC) tool flags files in %windir%\System32\WindowsPowerShell\v1.0\Modules\Defender as corrupted or damaged. You see error messages such as the following:

Hashes for file member do not match.

This is a known issue in Windows 10, version 1607 and later versions, and Windows Defender version 4.18.1906.3 and later versions. The files for the Windows Defender PowerShell module that are located in


Advertising

%windir%\System32\WindowsPowerShell\v1.0\Modules\Defender

ship as part of the Windows image. These files are catalog-signed. However, the manageability component of Windows Defender has a new out-of-band update channel. This channel replaces the original files with updated versions that are signed by using a Microsoft certificate that the Windows operating system trusts. Because of this change, SFC flags the updated files as “Hashes for file member do not match.”

Future releases of Windows will use the updated files in the Windows image. After that, SFC will no longer flag the files. Because SFC incorrectly flags the files in %windir%\System32\WindowsPowerShell\v1.0\Modules\Defender, you can safely ignore the SFC error messages regarding these files.

Addendum: The issue has been fixed, see Microsoft fixes the Windows Defender sfc bug (August 2019).

Similar articles:
Patchday: Updates for Windows 7/8.1/Server (July 9, 2019)
Patchday Windows 10 Updates (July 9, 2019)
Windows Server 2016: May 2018 Update bricks sfc
Windows 10 V1703: Fix for DISM error 0x800F081F


Advertising
This entry was posted in issue, Windows and tagged , . Bookmark the permalink.

1 Response to Microsoft confirms July 9, 2019 Updates breaks sfc in Windows

  1. Pingback: Home windows Defender malware scans are failing after a number of seconds - ZDNet -

Leave a Reply

Your email address will not be published. Required fields are marked *