Windows 11 24H2 Update Faces New Bug
In the latest chapter of Windows 11’s ongoing evolution, users have encountered a persistent issue with the 24H2 update. This bug manifests itself when running the familiar command sfc /scannow, a tool designed to detect and repair corrupt system files. Unfortunately, many users report that this command now consistently identifies corrupt files, even after multiple attempts to rectify the situation.
The Windows 11 Feedback Hub has become a platform for users to voice their frustrations. One user expressed their discontent, 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 echoed similar sentiments, noting, “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.’“
To further investigate this issue, Windowslatest.com conducted tests and encountered the same frustrating scenario. After executing the sfc /scannow command, they received a message indicating that “Windows Resource Protection found corrupt files and successfully repaired them.” However, upon re-running the scan, the same message appeared, leading to a cycle of confusion and concern among users.
This situation is not entirely unprecedented. Major software updates often come with their share of bugs. For instance, the previous Windows 11 22H2 update was plagued by a bug that caused File Explorer to freeze or crash intermittently. The current 24H2 update has already revealed two notable issues: disappearing cursors and an undeletable 8.63 GB update cache.
Microsoft is likely aware of these complications and is presumably working on patches to address them. As the tech community watches closely, users are encouraged to stay informed about potential resolutions to these ongoing challenges.
