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

Bree said:

Love the workaround

It's the Microsoft way of telling you, if you have a problem, don't bother telling us. We will fix it in the future (whenever this might be).
Now what happens in the meantime... we don't care. Find a way to live with it!!!

@Mooly

Something has not yet been completed in the Windows post install process that has dependencies. Let the system settle down, reboot and let the system settle down one more time. Make sure nothing is trying to update. Then you can run your DISM command.

It is fully possible that something is a bit jammed or broken too...let us know. I haven't tried to cleanup the components and reset the base in a very long time.

Mooly said:

@cereberus I'm on the standard 1809 installation clean installed via MCT.

More weirdness. I tried running the DISM cleanup command:
Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase

and get the following error message:

Code:

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

Deployment Image Servicing and Management tool
Version: 10.0.17763.1

Image Version: 10.0.17763.348

[=====                      9.8%                           ]
[=================          29.6%                          ]

Error: 6824

The operation cannot be performed because another transaction is depending on the fact that this property will not change.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

C:\Windows\system32>

Edit...
See:
Current Status of Windows 10 October 2018 Update version 1809

Now down to 39.2Gb after attempting the WINSX clean up. Time for a restore methinks :)

Two ways I've found to correct that. Just reboot and re-run, or for cleanest safest, do all the DISMs in Safe Mode. Added benefit to Safe Mode, is you should re-boot anyway after the cleanups, and you will by booting back to Normal.

All of these should be done, in order, not just the one posted.

Code:

fsutil resource setautoreset true c:\&fsutil usn deletejournal /d /n c:

Dism.exe /online /Cleanup-Image /StartComponentCleanup

Dism.exe /Online /Cleanup-Image /RestoreHealth

Dism.exe /Online /Cleanup-Image /StartComponentCleanup /ResetBase&pause

roy111 said:

To all those on RP not receiving this KB4482887:

KB4482887 was on RP February the 20th, I infer it has now landed to regular 1809 so it is already installed on RP( @Wynona ) or no longer available, for whom that did not updated between feb 20 - feb 28 @f14tomcat

The file released on Feb. 20 was for Insiders on Release Preview. I am not an Insider of any type on my 1809 Production partition. I downloaded the .MSU file and it installed just fine.

Mooly said:

I'm confused (its early, it might be me ) and/or no one noticed the elephant in the room with my earlier post and images (lol, I certainly didn't)

I'm not on .348 PLUS the update check I ran installed a different KB. Looks like I got February's cumulative instead.

I've run another manual update check today and got another .net update but no KB4482887. Has it been pulled?

Attachment 225928

Attachment 225929

Mooly, did you join the Insider Program on 1809; probably the Release Preview? If so, you probably already have KB4482887.

Edit: Never mind. I saw your post made later.

Thanks a lot for posting this info here Brink. :)

roy111 said:

To all those on RP not receiving this KB4482887:

KB4482887 was on RP February the 20th, I infer it has now landed to regular 1809 so it is already installed on RP( @Wynona ) or no longer available, for whom that did not updated between feb 20 - feb 28 @f14tomcat

Roy, I am all updated fine everywhere, was before. RP is .346 and 1809 is .348. All good. Missing nothing. It's not the first time MS had reissued a KB with a bump to the OS patch level. But thanks.