A bug has been identified in the new 24H2 update of Windows 11.

A new bug has been discovered in the Windows 11 24H2 update that causes the sfc /scannow command to detect corrupt files on every execution. This tool is well-known among users as it is entered in the Windows Terminal and conducts a thorough scan, reporting on corrupt or missing files and indicating whether it has been able to repair or replace them.

The current issue causes sfc to find damaged files, repair them, and when run again, identify another "corrupt file" and "repair/replace" it once more, regardless of how many times it is executed. This suggests that the detected issues are false positives. Since users utilize sfc for system maintenance, this repetitive behavior of corrupt files leads to confusion and drives them to try to resolve a problem that does not actually exist.

Users have begun reporting this anomaly on the Microsoft feedback hub for Windows 11. One mentioned: "With the latest Windows 11 updates, when I try to run sfc /scannow, it shows errors every time, even though it should have already fixed them." Another user expressed: "The SFC scan in the new 24H2 version shows errors and does not fix them despite attempts to resolve the issue. Every time I run the scan, it says 'Windows Resource Protection found corrupt files and successfully repaired them.'"

Tests were conducted to observe the error in action. After running sfc /scannow, the message received was: "Windows Resource Protection found corrupt files and successfully repaired them. For online repairs, details are included in the CBS.log file located in windir\Logs\CBS\CBS.log. For example, C:\Windows\Logs\CBS\CBS.log. For offline repairs, details are provided in the file logged by the /OFFLOGFILE option." When the scan was run again, the same message appeared, repeating exactly the same content.

It is not uncommon for large-scale software updates to experience bugs. In the Windows 11 22H2 update, a failure in File Explorer was reported that caused frequent freezing or crashes. So far, two issues have been documented in the 24H2 update: the cursor disappearing and an 8.63 GB update cache that cannot be cleared.

Microsoft is aware of the bugs and is likely working on some patches at this time.