@ch100 it was about the format of the updates overview, splitting it into public 20H1/2 and IP 21H1 into two separate posts.
I downloaded cabs from the UUP Dump and installed with DISM. The process was very typical, and uneventful. No biggie.
After many attempts .. i manage to build 19043.906 from the base 19041.1 CORE and so far so good ... but this is not the way updates should be delivered to the customers , if they are creating so many issues on a regular base setup Just my opinion... Until they will release a new stable LTSC without the crap , i will get stacked to 14393.4288 LTSB ...
19043.xxx is beta channel, not regular and simply enrolling into the beta channel on 19043.xxx will offer you the needed updates, except dotnetcu. Running W10UI_9.8 with these updates and a 19041.1 base image will create a 19043.906 ISO without problems:
As far as i am concerned is about the idea or releasing something which it breaks thinks , and what about a regular update for the one who want to try ... you need to reinstall always a fresh image every time an update gives errors? My build i always created with NTLite ...and i like to clean and completely remove the left overs ... and i used only : ssu-19041.903-x64.cab = KB5000981 Windows10.0-KB4601554-NDP48_CU_4341.2 Windows10.0-KB5000736_21H1_EP_844.cab windows10.0-kb5000842_LCU_Beta_906.1.13.cab Windows10.0-KB5001460_FxP_678.cab
It's like this: .867 --> .868 --> .870 + .899 = .906 Technically, if you're not enrolled in Beta (or Release-Preview), you shouldn't be beyond 19042.870 until April 13th patch Tuesday. With MSFT, everything is a temporary build anyway.