@adric SSUs are permanent updates by default, not because of resetbase if you enabled the full resetbaese, then all their superseded components are removed anyway if you want to uninstall the updates themselves: https://forums.mydigitallife.net/posts/1154312/ @Enthousiast it depend on files names remove x64- from Dotnet48_NL
has any info About the KB4504360 - Compatibility update for upgrading to Windows 10, Version 1903 (Dynamic Update) , have new update replace for it ?
Something is still not very clear to me. Doing full resetbase (using the registry trick) in 1809 even in a live system breaks the "Reset this PC"? Cleanup without resetbase takes too long
It does take a long time but if you want to use Reset This PC you dont have a choice. If you aint going to use it or capture the image then doing the full reset is ok.
I thought the problem was only when it was done offline. Well, I plan to go into audit mode, sysprep, and capture the image
That will take much longer and still breaks resetpc when full resetbase is used, it will add about 200MB to the captured image too, going the sysprep route has nothing to do with resetbase in any way.
New 19H2 SLOW ring 18362.10005 updates: https://forums.mydigitallife.net/th...19h1_release_svc_19h2_rel.79968/#post-1536588
In my tests the opposite happens, no full resetbase takes much longer than activating resetbase. I use the W10UI script. This is related I think with the delta compression that is done when cleanup does not resetbase. Remembering that I am referring to the 1809 version. I did not know of those 200 MB more in the captured image. According to the @rayleigh_otter there is a bug when doing the resetbase and capturing the image. After deploying the machine an error appears during OOBE. I have not tested it yet.
Installing in audit mode, sysprepping and capturing takes way much longer then just waiting till /cleanupcomponent is finished (and it has nothing to do with it), and on 1903 you can simply use W10UI with the /resetbase option, nothing will be broken. I did the capture stuff monthly and learned that 1903 captured images, not upgraded well and never used /resetbase on them at that time. Rayleigh otter thinks 17763.107 is a clean source...
Yes we do not have much to do we are forced to use Windows not far from what Microsoft has designed for this to work. The more new versions of Windows come out the more resetbase has caused more problems and at one time or another we will have to stop using this since it seems to be in Microsoft's plans to permanently remove this.
MSFT disabled resetbase for a reason a few years back, and @abbodi1406 his W10UI tool enables it (if desired), but skips it for 1903 LCU's.