Microsoft Acknowledges Fixes in Windows 11 24H2 KB5044384 for SFC/Scannow and WebView2 Issues

Microsoft Acknowledges Fixes in Windows 11 24H2 KB5044384 for SFC/Scannow and WebView2 Issues

In our report from yesterday, we highlighted a frustrating situation reported by users who are unable to erase 8.63 GB of outdated update data following their upgrade to Windows 11 24H2. One comment from our readers pointed out another issue related to the System File Checker (SFC) that seems to be occurring after the 2024 feature update.

For those unfamiliar, the System File Checker, or SFC.exe, is an integrated tool within Windows designed to repair corrupted or damaged system files by restoring them to their original state.

When users execute the SFC/scannow command, it informs them that their system has corrupt files. However, in many cases, attempts to “repair”these files prove unhelpful, as SFC subsequently indicates that the same files remain broken. A reader named Sladen shared further insights into this issue, mentioning it might be linked to a hash mismatch with WebView2.

Sladen stated:

There is another identified problem with /sfc. When a user executes sfc /scannow, it will indicate that corrupted files exist and proceed to repair them. However, when the user runs sfc /scannow again, it will report and fix the same corrupted files a second time. The affected file is Microsoft.Web.WebView2.Core.dll, which has a hash mismatch between the Microsoft Store version and the one installed on the system.

This issue seems to be affecting multiple users, with numerous discussions taking place across various Google forums. Fortunately, Microsoft has acknowledged the problem and has provided a solution in the latest release preview build, 26100.2152, available under KB5044384. According to the release notes from Microsoft:

[sfc /scannow command] Fixed: Users encounter errors each time the command is executed.

As a result, those subscribed to the Release Preview Insider channel should find the issue rectified. Furthermore, this fix is expected to reach non-Insiders by the end of this month as part of the non-security preview update (C-release) under the same KB.

Source

Leave a Reply

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