Microsoft says the Windows 11 24H2 8.63 GB Bug is real, and a fix for it is coming soon
The bug has created a lot of confusion among Windows users.
2 min. read
Published on
Read our disclosure page to find out how can you help Windows Report sustain the editorial team Read more
Microsoft has acknowledged a bug related to Windows 11 24H2, released earlier this month. The issue concerns the operating system incorrectly reporting how much disk space Windows’ native Disk Cleanup utility can free up. The bug reportedly shows 8.63 GB of recoverable space in Windows 11, even if there isn’t any.
The company explained the issue in a post on its Windows Health Dashboard, stating:
After using the Windows Disk Cleanup application may display an incorrect amount of disk space that can be freed up in the ‘Windows Update Cleanup’ category. Please note this is a reporting error. When ‘Windows Update Cleanup’ is selected and Disk Cleanup is run for the first time, some or all files in that category (for example, 15 GB) are cleaned up correctly and the related disk space is freed as expected. However, after this initial run, the tool may inaccurately report an amount of space still available for cleanup (for example, 88 GB) in the ‘Windows Update Cleanup’ category. This inaccurate amount of disk space is reported even though the space was already freed in the initial run.
Microsoft says it’s investigating the root cause of the problem and will release a fix once available.
The issue has been present since Windows 11 24H2’s release and doesn’t appear to have been addressed in this month’s Patch Tuesday update, which fixed a bug leading to boot loops and Bluetooth/USB connectivity failures for some users.
If you’ve experienced the Windows 11 8.63 GB bug related to the Disk Cleanup utility, know it’s a false alarm. The utility doesn’t know it yet.
In other news, the 24H2 update seems to deactivate Windows 11 on some devices. Although the issue is not yet widespread, it has affected dozens of users. The Redmond-based tech giant hasn’t updated the Health Dashboard to include this as a known error.
User forum
0 messages