I never run a cleanup on my main system, only on the iP VM's after upgrading and on my wife's laptablet (32GB emmc drive), which is always full or for testing purposes I do run cleanup and /resetbase when creating an uptodate iso.
Really appreciate all your help I learn a ton from your posts and replies. I'll discontinue running cleanup after each update. sound like a good idea just to be safe from future issues.
Well, hopefully people are learning what being on an insider ring really means. Don't expect stability or to be able to use Windows without issues if you decide to opt in.
Agreed, this is a great community and I am glad to be apart of it. I am in the IT profession but mostly Linux (Redhat/Debian) but wife hates Linux so we keep a Windows 10 system at the house for her and the kids.
It is impossible to modify updates, since they are signed by Microsoft. The update package is missing components — but installs anyway on an unpatched system because the components are the same as on unpatched system, so it uses the already existing ones. The file i posted simply contains these components extracted from the official ISO.
Code: C:\WINDOWS\system32>dism /online /add-package /packagepath:D:\patch\18362\x64\windows10.0-kb4505903-x64_841aa3285c3577225819f8753fd59bf343bfbdbf-cu.cab Deployment Image Servicing and Management tool Version: 10.0.18362.1 Image Version: 10.0.18362.264 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~18362.266.1.5 [==========================100.0%==========================] The operation completed successfully. 264 to 266 no error(264 cleanup but not resetbase).
No, they do not have a clue. To them, it is just the latest Windows for free. They tend to spam forums with typical Insider problems, I always ignore them.
I can confirm that your fix works (I had to expand cab with the proper command shell syntax command) but I hope MS will fix this for himself before public release of further cumulative updates.