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

@f14tomcat and @slicendice

I've run the first two commands and it looks like its worked so far. This took around 20 minutes or so at a guess and free space now at 41.4Gb. That's probably not far off the mark considering all the other updates and stuff.

Should mention that after the failed DISM attempt I did restore back to an image made earlier today which had all updates installed and had been restarted. At the time the image was made the system was 'quiet' and had been for some time as I just left it running to be sure.

The restored image launched into high CPU activity. This one IIRC:

https://answers.microsoft.com/en-us/...c-0abf719c589d

And this took 15/20 minutes or so to reduce to normal CPU usage. I've no idea why the restored image should have launched into this wheras the state it was in when the image was made did not.

Anyhoo

Code:

Microsoft Windows [Version 10.0.17763.348]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\Windows\system32>fsutil resource setautoreset true c:\&fsutil usn deletejournal /d /n c:
The operation completed successfully.

C:\Windows\system32>Dism.exe /online /Cleanup-Image /StartComponentCleanup

Deployment Image Servicing and Management tool
Version: 10.0.17763.1

Image Version: 10.0.17763.348

[==========================100.0%==========================]
The operation completed successfully.

C:\Windows\system32>

Bree said:

The board software will only add one notification at a time when you post. The trick to get multiple notifications in a post is to edit the post (making no changes) and submit it again. One more notification will be added. Repeat until all notifications turn blue.

Or you do!

And this took 15/20 minutes or so to reduce to normal CPU usage. I've no idea why the restored image should have launched into this wheras the state it was in when the image was made did not.
@Mooly - a restored image needs to completely rebuild the search index and similar. Not say that is all of it, but a decent portion of it.

Mooly said:

He's right It worked. Another trick learned (until I forget it)



That's interesting... although I'm not sure how 'universal' that might be. I say that because I ran the next DISM command:
Dism.exe /Online /Cleanup-Image /StartComponentCleanup /ResetBase&pause

and again got the same error message. I also wasn't in safe mode. Once this error message occurs it seems to eat up a large amount of disc space and so I restored again to an image made immediately after running the first DISM.

There is no CPU activity, all is calm.

I'll have to leave it for now, but later I will try the above again.

Note... I'm using AOMEI with their own VSS option and not the default option because I find that doesn't restore everything (in common with Macrium because that uses the same MS/Windows VSS). Not sure if that would make any difference as to what got restored and in what state because I don't know what, if any, files get excluded from an image... however......

Just a last comment. Try the Safe Mode method. I've never had it fail in Safe Mode. Cheers!

Speaking of DISM and cleanup. I'm in the process of creating an ISO for ARM64 using UUP-Dump and right now the scripts are cleaning up the image because they injected latest CU into the image.

To me it looks more like it's mining Bitcoins than actually doing some real work. CPU-usage at constant 35-42% and not much of disk activity. This is the same behavior we sometimes see with WU. It just consumes a lot of CPU resources but it looks like it's not doing much.