Cumulative Update KB4482887 Windows 10 v1809 Build 17763.348 - March 1 Win Update

Access Denied said:

I had ESET NOD32 Antivirus installed when the CU was installed. No issues here. Mine is just the AV, not the Security version.

Thanks - interestingly the antivirus was working but firewall, web and e-mail filtering weren't. When I have some spare time I might have another go and see if it works. Perhaps it was something unique in my config which happened to cause problems at the time.

I'm wondering if this update could be preparing the way for the next big feature update.

As for myself, I carried on playing around with this and in the end restored a Feb 28th full image and then applied the March CU and other updates manually from the update catalogue. Still down on disk space although not by quite so much. Curiously an update check still wants to install a .net cumulative update from Feb, that is despite having the March one already installed.

A normal disk clean following all this gave virtually nothing back and there was also nothing to clean related to Windows update.

Fabler2 said:

It took a long time for Windows Update Clean-up to complete - even though just 1.81 GB.

While playing around yesterday and when I had the February updates installed I did get a similar figure to clean up, and yes it took ages. I just wasn't happy with the final result.

Today I got from near to 43Gb free space all the way down to 39.3Gb with the update saga. That's when I went back and did an off-line installation from the catalogue. Now at 40.7Gb which is plausible although in this state disk cleanup reports nothing update related to clean.

I have this update on an old AMD870 chipset pc and it is currently downloading on a slightly less old AMD970 chipset one, but my laptop with a Skylake-U is still on 1803.

slicendice said:

I've had this issue too in this particular Windows version. Usually Disk Cleanup takes about 10 minutes, no matter the size, now it takes hours. And the cleanup result isn't that impressive either.

We seem to have come to accept that this is "normal" behavior, but it certainly isn't. Cleanup on Windows 7 takes at most minutes, and this was carried over in the earlier versions of 10; this practice of taking a protracted period of time to clean up small amounts of files is a recent phenomenon.
Aside from the sheer frustration of waiting for the system to end its seemingly endless thrashing, I suspect that serious damage is been done to the system's integrity: Exotic problems invariably crop up after these torturous episodes. I now make certain that I never tick that box during disc cleanup. Is there a less traumatic way of cleaning these files?