the root cause of your problem is cleanup/resetbase, it's not compatible with mixed LCUs from different branches (i.e. IP channels) doesn't matter how you installing this updates if you want to test it then install base 22621.1 build, update it to 819 and then to the 885, it should work or build 819 ISO without cleanup and update it to 885, it should work too
I always made UUPD ISO with cleanup & reset base options enabled Never got any issues earlier, but now, LCU installation technique is getting more complex day by day, I started using W10UI tool to install those As you're saying root cause is cleanup/resetbase, so while creating UUPD ISO, should I exclude those options (unchecked), and in that way, LCU update will be done without any error/fail?
cleaning up the image with reset base and component cleanup and especially superceeded commands is bad tbh, lcu's look for previous installations of certain old files/installs/build numbers etc before they update sometimes., its there purely to reduce disk space on small drives
so what's the best practice while creating the Win ISO (Via UUPD) to avoid such errors/failures? No cleanup & reset base at all or only Cleanup but no reset base? Cleanup & reset base does reduce the ISO size, apart from that, is there any other reason(s) to use those functions?
the creator of this thread should tell you more, im just going by experience and researching the commands, and failures to update personally no, theres no need for those commands unless you want to run it of a usb or you have a very small system drive only Restore health is the only command you need just dont run cleanup in the conversion tool, Disk cleanup is safe not had issues using regular cleanup
the most safest method is to not enable basic cleanup at all, resetbase doesn't matter in our case because it works only with cleanup option in combo cleanup and resetbase is only used for reducing ISO and install OS size, nothing else it's completely safe to use cleanup or cleanup+resetbase if you are going to stick to one channel, but if you are going to install different updates then cleanup will break it and you can fix it fast enough with in-place upgrade
got it. Thanks to all of you for the clarification. @abbodi1406 @Paul Mercer @boe323 & @Enthousiast One last question, as I believe my current host got corrupted for LCU installation due to Cleanup & resetbase function active & switching channels via different LCU, Cleanup-Image /Restorehealth command would do the work to fix this, or I've to perform in-place upgrade with a freshly created UUPD ISO with no cleanup & resetbase?
I think Restorehealth thing will not help you, otherwise it would be everywhere so you are going to install Beta 885 build, but the latest one is 891, I suggest to build new 22623.891 ISO without cleanup and in-place upgrade it also it's possible to fix LCU installation without in-place upgrade, some members here did that successfully, but I don't have any manuals for that
In place usually fixes anything but there are rare cases where it is not enough and it will fail. I have found that in these cases you need to build an image that matches your current build (do not select cleanup) and then integrate the target LCU you want to upgrade to (again, no cleanup). Doing an in place upgrade with this image should work in cases where going directly to the new image fails.
Where can I find checksum for 22621.819.221105-0030.NI_RELEASE_SVC_PROD1_CLIENTPRO_OEMRET_X64FRE_EN-US?
looks like this is homebrew ISO made with UUP dump or something, there is no checksums for that kind of stuff
Oh I thought it was official latest release. It says on MS own website that latest build is 22621.819, so I thought the iso from UUP was official.