Early adopters of the recently released Windows 11 version 24H2 have noticed a strange behavior of the new OS. When you perform a disk cleanup with with Windows Update files checked, the OS leaves several gigabyte of data untouched. This caused a lot of speculation that it is a bug in the OS.
The data left of the drive is exposed in the cleanmgr.exe tool and also appears in the Settings app under System > Storage > Temporary files. However, it is impossible to remove it using any of these tools.
While there is no official information of this case, the data left on the drive may be related to new checkpoint cumulative updates. It works as follows. Once a Windows 11 24H2 cumulative update is released as a checkpoint, future cumulative updates will generate binary differentials from the latest checkpoint binaries instead of the RTM version. This means the differentials will be smaller and more manageable for devices already synced to the latest checkpoint, resulting in a quicker update process.
Ghacks made a guess that the data left on the drive is related to such cumulative updates. If so, then the bug is that the files are shown in cleanup tools. Microsoft is yet to clarify what is going on.
Obviously, if you are affected and see nearly 8 GB of Windows Update files that you cannot delete, you should not do anything right away. Do not use any third-party tool to get rid of those files, and do not reset Windows Update.
Support us
Winaero greatly relies on your support. You can help the site keep bringing you interesting and useful content and software by using these options:
If you like this article, please share it using the buttons below. It won't take a lot from you, but it will help us grow. Thanks for your support!
Advertisеment
That’s is really bad bugs, i hate Microsoft
Haha, what if everyone would switch to Linux who are not happy with Windows these days ;)
My main OS has been Linux for 20 years. Been a lot of problems in the early years, but nowadays it just rolls on. I have Windows 11 on a PC, but don’t use it very often.
Is this on an update to 24H2, or on a clean install as well?