Microsoft seemingly makes deleting 8.63GB impossible after Windows 11 24H2 update Hallie Frederick | usagoldmines.com

Since updating Microsoft’s newest Home windows 11 function replace, version 24H2, a number of customers are reporting that they’re unable to carry out a Home windows Replace Cleanup that enables customers to release house. As such, seemingly each consumer updating to Home windows 11 24H2 is discovering that they don’t seem to be capable of proceed with deleting 8.63GB of previous cumulative updates, a factor that was attainable on earlier variations of the OS.

Picture through Acrobatic_Face_7404(Reddit)

For instance, an Eleven Discussion board member thecaretaker who began a thread on the problem, says:

Simply up to date to Win 11 Professional 24H2. All is working wonderful. Nevertheless, I’ve received a further 8.63GB of Replace information that will not delete (see picture).

I’ve run Element Retailer cleanup but it surely hasn’t made any distinction. Additionally ran it in secure mode.

When somebody steered that they run a Disk Cleanup, one other consumer confirmed that it was not working both, as they wrote:

No, at the least not on my PCs.

An entry labelled “Home windows Replace Cleanup” at 8.63GB stays. Disk Cleanup won’t take away it.

I looked for a method to repair that. It seems that it is a bug, the Microsoft should repair.

The consumer and several other others imagine this can be a bug in Home windows 11 24H2, however that’s unlikely since virtually each system displays this ‘symptom.’

A consumer on My Digital Life discussion board suggests this is probably not a bug in spite of everything and is how Microsoft supposed it to be. They write:

Once more, this isn’t actually an issue/bug however the results of the present Updates growth, the information have to be saved by the system.

The consumer is referring to the brand new Home windows cumulative replace supply technique that Microsoft launched with Home windows 11 24H2 and Server 2025. Referred to as “Checkpoint Cumulative updates” (CCU), the corporate has primarily delivered these as checkpoints as an alternative of your entire replace since RTM, thus lowering the dimensions of every replace. As a consequence of that, it’s definitely believable why deleting this “8.63 GB” of undesirable information will not be working.

Nevertheless, that is merely hypothesis, and it’s attainable that the problem is certainly a bug that must be fastened. In any case, the corporate had already confirmed a CCU-related downside that results in the “Operation is not supported” error message.