1. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,810
    94,909
    340
  2. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    52,048
    114,407
    450
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. javaspain

    javaspain MDL Member

    Jul 29, 2009
    241
    130
    10
  4. dorfd1

    dorfd1 MDL Senior Member

    Sep 10, 2015
    277
    98
    10
    #2224 dorfd1, Jun 26, 2022
    Last edited: Jun 26, 2022
    upload_2022-6-26_10-35-17.png

    upload_2022-6-26_10-52-48.png
     
  5. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    52,048
    114,407
    450
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. dorfd1

    dorfd1 MDL Senior Member

    Sep 10, 2015
    277
    98
    10
    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
     
  7. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    52,048
    114,407
    450
    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.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. dorfd1

    dorfd1 MDL Senior Member

    Sep 10, 2015
    277
    98
    10
    I did an in place upgrade to LTSC 2021 and i have no problems
     
  9. MDeaks

    MDeaks MDL Member

    Aug 25, 2017
    154
    75
    10

    Attached Files:

  10. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    52,048
    114,407
    450
    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.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. MDeaks

    MDeaks MDL Member

    Aug 25, 2017
    154
    75
    10
    ..

    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))
     
  12. timster01

    timster01 MDL Junior Member

    Dec 21, 2017
    53
    92
    0
    You don't need to enable developer mode to install Store-LTSC2021-2021-11-17, just run the included batch file as admin
     
  13. pm67310

    pm67310 MDL Guru

    Sep 6, 2011
    3,681
    2,934
    120
    clean LTSC 2021 and WSReset -i works for me you need execute two time ! this command
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  14. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    52,048
    114,407
    450
    Attach it to the post (more options > upload a file).
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    52,048
    114,407
    450
    You need a minimum of 5 posts to be able to publish links or attach files, iirc.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. qwesta

    qwesta MDL Senior Member

    Jul 22, 2011
    374
    190
    10
    He will spam all over the place to achieve this...:p
     
  17. acer-5100

    acer-5100 MDL Guru

    Dec 8, 2018
    4,003
    2,956
    150

    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.
     
  18. dorfd1

    dorfd1 MDL Senior Member

    Sep 10, 2015
    277
    98
    10
    #2238 dorfd1, Jul 1, 2022
    Last edited: Jul 1, 2022
    all an enablemt package does is change registry entries that up the build number and turns on features.

    upload_2022-6-30_20-27-34.png

    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
     
  19. dorfd1

    dorfd1 MDL Senior Member

    Sep 10, 2015
    277
    98
    10
    1806 is a release preview update, the iso image u downloaded and installed is not official
     
  20. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,810
    94,909
    340
    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