Windows 11 24H2 Update Bug: sfc /scannow Detects Corrupt Files with WebView2

Yesterday, I highlighted that Windows 11 24H2 had several issues, but recent feedback suggests that situation has improved.

Currently, we have identified two unreported problems. One bug results in the cursor vanishing, while another issue prevents 8.63GB of storage from being freed up due to the Windows Update cache. Moreover, a new bug in the Windows 11 2024 Update triggers the system file checker (sfc /scannow) to flag corrupted files each time it is executed.

The System File Checker (SFC) has gained significant popularity among users who undertake routine maintenance of their Windows systems. It’s frequently promoted by various YouTubers, explaining why many individuals run the sfc /scannow command regularly.

Nonetheless, a particular glitch in Windows 11 24H2 complicates matters, as SFC consistently identifies damaged files. Upon upgrading to Windows 11 24H2, Windows Latest discovered that executing sfc /scannow generates this outcome:

Windows Resource Protection identified corrupt files and repaired them successfully. For online repairs, detailed information is stored in the CBS log file located at windir\Logs\CBS\CBS.log, such as C:\Windows\Logs\CBS\CBS.log. For offline repairs, the information can be found in the log created by the /OFFLOGFILE option.

This suggests that there is an issue within your Windows 11 installation, possibly due to discrepancies between local hash files and their corresponding versions on Microsoft’s servers, and SFC has proactively resolved it, which is beneficial.

However, upon running the scan once more, the same notification will appear, indicating that SFC has repaired the Windows installation again. Regardless of how frequently you execute sfc /scannow via Command Prompt, the Windows File Checker will seemingly fix something each time.

This concern was initially raised by testers within the Windows Insider Program and has since transitioned into the production pathway with Windows 11 24H2.

“Why is it that SFC /scannow frequently identifies corrupt Bluetooth files after a Windows update, even with Bluetooth disabled on my system? It appears that every update triggers SFC to find corrupt Bluetooth-related files.”

SFC and WebView2 Issue in Windows 11 24H2

In our findings, Windows Latest noted that the System File Checker (SFC) detects discrepancies in the hash values of specific WebView2 files.

Although SFC manages to repair these files, the same problem recurs with every scan. This may stem from a bug that emerged in Windows 11 24H2, incorrectly marking these WebView2 files as corrupt.

Specifically, SFC is indicating that the hashes for the file member [l:31] ‘Microsoft.Web.WebView2.Core.dll’ do not align.

This does not imply that WebView2 is malfunctioning; in our tests, all web applications are functioning as expected.

It’s probable that a hash mismatch is causing SFC to persistently flag and attempt to rectify these files. The purpose of file hashes is to ensure the original file matches and isn’t a modified version.

On a positive note, Microsoft is aware of these issues and is actively working on a resolution, which may be delivered through a server-side update.

Source

---

---