Windows 11 24H2 Update Bug: False Corrupt File Warnings from System File Checker

In a baffling twist of fate for Windows 11 users, the latest 24H2 update has introduced a bug that triggers the System File Checker (sfc /scannow) command to report corrupt files every single time it’s executed. What’s more perplexing is that despite these false flags, everything appears to be functioning without a hitch in users’ systems, particularly concerning WebView2 applications.

Understanding the Nature of the Bug​

As reported, this issue first surfaced to the attention of Windows Insider testers before manifesting in the public production release. The chaos began after users updated to Windows 11's 24H2 version, where running sfc /scannow prompts a message reading: “Windows Resource Protection found corrupt files and successfully repaired them." However, upon re-running the command, the same corrupt files are detected once again, creating an endless loop of repairs with no actual resolution.
In essence, for every scan executed, sfc claims it has fixed corrupted files, which in reality, may not even exist.
Here's the kicker — the bug particularly targets files related to WebView2, with the command detecting hash mismatches for key system files, specifically Microsoft.Web.WebView2.Core.dll. Although this might sound ominous, it doesn’t imply that the WebView2 framework itself is dysfunctional; users can still run web applications without issue.

A Closer Look at System File Checker​

For those not in the know, System File Checker is a utility in Windows that allows users to scan for and restore corruptions in Windows system files. It serves as a safety net for maintaining a healthy operating system. Here’s how it traditionally works:

• File Hash Verification: Every system file has a hash — a unique string of characters that verifies its integrity. If the file changes (due to corruption, accidental deletion, or even malicious activity), Windows can spot the discrepancy during a scan.
• Automatic Repairs: If a file is found to be corrupt, sfc attempts to replace it with a cached copy stored in the Windows folder, effectively restoring function without requiring user intervention.

The Implications of This Bug​

The repeated false alarms from the sfc command could lead to several frustrations for users, particularly for those who rely on it for regular system maintenance. Imagine diligently running sfc each week — only to be faced with the same message promising ‘repairs’ despite no tangible change! This issue could result in confusion, misplaced trust in Windows' maintenance utilities, and even an anxiety-fueled renaissance of IT support calls.
Moreover, it raises broader concerns about the quality assurance processes that Microsoft employs before rolling out major updates. The Feedback Hub has seen an influx of comments from frustrated users pointing out the apparent lack of rigorous testing regarding quality control, especially with regard to critical system functions.

What’s Microsoft Doing About It?​

The silver lining is that Microsoft has acknowledged the issue and is reportedly working on a fix, which may be rolled out through server-side updates. However, until that remedy arrives, affected users are left in limbo, pondering whether to trust the utility designed to preserve their systems.

Conclusion​

The Windows 11 24H2 bug affecting sfc /scannow serves as a reminder that even the most robust software can encounter flaws. As we await a corrective measure from Microsoft, users are encouraged to remain patient and cautious. After all, while the lure of running a routine maintenance check is strong, it’s essential to remember that sometimes, there’s nothing broken to fix — even if your computer insists otherwise. Keep an eye on your updates, make sure your system is backed up, and, for now, try not to sweat the small stuff that sfc claims might be broken!
In the meantime, if you find yourself pulled into discussions about this ongoing saga, feel free to share your experiences and any insights with fellow users on the Windows Forum!
Source: Windows Latest Windows 11 24H2 bug causes sfc /scannow to detect corrupt files in every scan (WebView2)