Some perform inplace upgrades from 19045.xxxx non LTSC (some even still enrolled in the IP channels) to 19044 LTSC and they end up with weird behaving LTSC installs, they get feature upgrades offered which don't install and so on.
Troque apenas o SKU, às vezes usando um Pro em vez do LTSC original. Já vi casos assim. C:\Windows\System32\spp\tokens\skus
It was accomplished as described in the OP. Acquired an ISO of 21H2 LTSC, updated it using Win10UI with @Enthousiast's suggested updates found in the first message of this thread, modified the resultant ISO with @Enthousiast's Update Matrix Fix Tool, mounted the ISO, ran setup, prayed to the Bit G0ds.
Uh, when I asked about performing this upgrade, and was told it would work using @Enthousiast's Upgrade Enabler Tool, no one mentioned the result would be some freak weirdly behaving Frankenstein. I was hoping to SAVE myself some time by not having to reinstall a ton of apps, not WASTE time and end up having to perform a clean install anyway. Guess I'll be holding off even longer to update my main desktop than I was originally planning to see if the system I upgraded flakes out.
EP = Enablement Package Originally, all the 1904x builds are actually all 19041, but the later ones get an Enablement Package applied. It is just a small update that sets the new (fake) build number in the registry and enables the features for that version. The 19045 EP is still installed after the "upgrade" which makes the system think it is 19045 and causes the weird wrong offers and behavior. To make matters worse, the features it was supposed to enable just don't work on LTSC due to product policies. Removing the 19045 EP and reinstalling the 19044 EP should fix things to normal. But no idea if the system allows that at this point.
Hurm. @Paul Mercer told me that both 21H2 LTSC and the 22H2 I was upgrading were both really 19041, but from what you're saying that was true in the past, but not now. After performing the "upgrade" as previously outlined, and running Windows Update, systeminfo shows the OS build as 19044 and these as the only installed updates: Code: KB5042097 KB5004331 KB5003791 KB5007401 KB5011048 KB5043131 KB5043130 KB5005699 So, only the 19044 EP is installed, not the 19045 one, so I should be fine? Is there some more definitive method for determining if the 19045 EP is still installed? I guess a manual method would be extract the 19045 EP, compare them against 19044 EP, and search the filesystem for the files only in 19045?
19041 = 19041, 19042, 19043, 19044, 19045 do not overcomplicate stuff, 19042-19045 builds are fake ones, each of it with their own EP 19045 is KB5015684 19044 is KB5003791 if your OS is LTSC 2021 then remove KB5015684 and install KB5003791 if your fake build is 19044 on LTSC 2021 then everything is fine if it's 19045 - remove KB5015684, install KB5003791
EVAL didn't get the useless N crappy edition, all MVS ISOs have N onboard but it is not advised to use it, they are crippled because EU law wants it, not a special feature.