Beware: Critical SFC Bug Discovered in latest Windows 11 24H2 Update – Patch Alert

Another Windows 11 24H2 Update Bug: Wrongly Identifying Corrupt Files in Every Scan

The Windows 11 24H2 update has been hit with another bug, causing the built-in sfc /scannow command to incorrectly identify corrupt files on every run. This issue is a real head-scratcher, as it can lead to confusion and frustration for users who rely on this tool for system maintenance.

For those who aren’t familiar, the sfc /scannow command is a Windows utility that scans the system for corrupt or missing files and attempts to repair or replace them. It’s a power tool that users often run to ensure their system is in top shape.

The problem arises when this command, intended to help diagnose and fix issues, starts reporting false positives – that is, it identifies corrupt files when there are none. This can happen repeatedly, even after running the scan multiple times, which can be disconcerting and may lead users to continue trying to fix a non-existent problem.

One user reported experiencing this issue, stating, "With the latest Windows 11 updates, when I try to do SFC /scannow, it shows errors every time even though it should have fixed them already." Another user echoed this sentiment, "SFC Scan on the new 24H2 shows errors and does not correct itself despite repeated attempts to correct it. Each time I run the SFC Scan, it shows ‘Windows Resource Protection found corrupt files and successfully repaired them’".

In an experiment, Windowslatest.com ran tests to demonstrate this problem. After running the sfc /scannow command, the system reported finding corrupt files and successfully repairing them. However, when the scan was run again, the same message appeared, stating the exact same thing. This is clearly a false positive, and it’s essential to identify it as such.

It’s not uncommon for large software updates like the Windows 11 24H2 update to experience bugs. In the past, we’ve seen issues like frequent File Explorer freezes or crashes in the Windows 11 22H2 update, as well as the disappearance of cursors and an undeletable 8.63 GB update cache in the current update.

Microsoft is, at this time, aware of this bug and is likely working on patches to address it. Keep an eye out for updates and stay informed about any potential fixes.

Fixing Corrupt Files or False Positives?

If you’re experiencing this issue, it’s essential to be aware that the system is identifying false positives. In the meantime, you can try restarting your system or seeking assistance from Microsoft Support or another reliable source.