The point is that there is a right time and a wrong time to apply an Enablement Package (EP). MSFT has provided a mixed answer to this question. It would be nice to know the build number for the earliest crossover build to which the 19043 EP could be applied and still activate all the features embedded in the build.
With the 20H2 EP it was also possible to jump to 19042 with one or two earlier released LCUs than MSFT published.
Small question when I build an iso from "Cumulative Update for Windows 10 Version Next (10.0.21296.1010) amd64" does it also include the base windows 10 install or only the update in an iso format?
is a windows 10 version Dev channel With updates SSU and LCU KB4602812 + KB4602816 something like this is actually only installed for test purposes current one is this one 21390.1
When UUP set is final, it does not change so even though MyPhone App is contained within that edition esd, aggregatedmetadata.cab still define microsoft.modernapps.clientn.all.esd as needed for all editions they fixed that in later Dev builds
haha yesterday I was testing my new ssd and for this previously downloaded the iso of Windows 10 using the MediaCreation Tool21H1 in sequence as always start the installation without Internet of course only the funny thing was that this time I forgot...well when starting the installation program presented some versions and improperly chose the version Education x64 and thought whatever God wants let's what gives! when the system started MSFT asked for the activation code (HWID) so I used my Windows 7 HWID and after a few seconds MSFT solemnly confirmed the activation of the system...and as I had downloaded a large update previously decided to install and after the system restarted I opened cmd and typed winver and what was my surprise! MSFT activated my system as Windows 10 PRO and ignored the version I had mistakenly chosen LOL...