Windows 10 Enterprise LTSC 2021 is 19041 an enablement package was used to bring it up to 19044 If windows 10 Enterpsie LTSC 2021 did not get feature updates it would be stuck at 19041
You keep on crossposting about this, facts: 1. There is no official 22H2 EP available atm. 2. The .mum method caused problems for a lot of people when the actual 22H2 EP was released. 3. Nobody can foresee what more it will cause using it on very specific releases that were intended to never get a feature update aka upgrade offered, which would undo the whole purpose of LTSC. Yes, the LTSC build is 19041.1 + Updates + 21H2 EP, but it was released as pre-build 19044.1288 + the LTSC features. We know that whatever127 showed how to reproduce it but that doesn't mean it should become the common method, it won't be 100% the same.
Professional for Workstation is Enterprise based, Enterprise has all functionality of ProFWS. But: He is using Enterprise 2021 LTSC not normal Enterprise but added the store... Both versions of KMS_VL_ALL, AIO or traditional, have those options.
.. oops> should;d have left it to THE EXPERTS...< thanks for corrections> Enthousiast, ---I have an install with win7 to win11 Enterprise, plus added the MS STORE <using the add on scripts> and it worked for me (( only differance might be - for novice me- = was/is that I had the SDK kit installed also))
You don't need to enable developer mode to install Store-LTSC2021-2021-11-17, just run the included batch file as admin
Calling an enablement pack a feature update is an exaggeration, is not like going from 1507 to 1607, it's just a number changed on the same build, almost surely going to 19044 to 19045 does practically nothing different than a normal cumulative update. Nothing lost noting gained either.
all an enablemt package does is change registry entries that up the build number and turns on features. the registry key 2093230218 is for 20H2 the registry key 633829003 is for 21H1 the registry key 2083071627 is for 21H2 the registry key 405124747 is for 22H2 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\0 installing the E.P or nums creates these keys and sets EnabledState to 2 which turns on the features i found this by viewing the manifest files from the e.p then i noticed the 22h2 nums created 405124747 installing the 22H2 nums sets the EnabledState to 1 in the registry key 405124747. this why your microsoft account and windows update know which e.p you have installed
405124747 is not for 22H2 installing the LCU "nums" does not create any of those keys, only EPs you are repeating the same delusion we have revoked 3 times before