1. murphy78

    murphy78 MDL DISM Enthusiast

    Nov 18, 2012
    7,419
    11,688
    240
    KMS 3.8 lasts like 15 years instead of the old 180 days so you don't have to install an activator. You just run the activator once after installing.
    You would use KMS activation for LTSC.
    For IOT or a converted LTSC-to-IOT version, that's how you activate with hwid.

    Detailed specifics on changing key and searching for activator here: https://forums.mydigitallife.net/th...rprise-n-ltsc-2021.84509/page-84#post-1716699
     
  2. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,681
    103,548
    450
    Why do you now call it KMS 3.8? It's called KMS38 (initially we called it KMS19) because in 2019 it was created and the activation lasted 19 years, it's nothing like normal KMS activation, i've asked the original devs to write some factual info about it but that never happened.

    From what i remember it was a side effect of one of the first tests with hwid based on kms activated systems, then you needed to kms activate the install and run the magical 10586 gatherosstate.exe to generate a genuineticket.xml and apply it all combined with keys extracted from a dll.
     
  3. fatpuppy1996

    fatpuppy1996 MDL Novice

    Jan 27, 2022
    11
    0
    0
    And from where can I get the IoT enterprise ltsc ISO? I just want to reinstall it and see if the HWID activation works.
     
  4. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,681
    103,548
    450
    From the download section at the OP.

    And HWID works on IoT Enterprise 2021 LTSC, KMS doesn't, using KMS it will switch it back to normal Enterprise 2021 LTSC.
     
  5. AveYo

    AveYo MDL Expert

    Feb 10, 2009
    1,836
    5,730
    60
    Nothing magical or secret about KMS38. It takes advantage of the time field being unix epoch time stored in a 32bit integer, so if you ffff it you get Tuesday, January 19, 2038 3:14:07 AM (GMT).
    There's gonna be a Year 2038 problem for many software using epoch time (time will leap back to 1901), it's even worse than Y2K problem.

    KMS38 is more of a registry hack. If you can use it, do so, it's the most private option.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. murphy78

    murphy78 MDL DISM Enthusiast

    Nov 18, 2012
    7,419
    11,688
    240
    I dunno. I think I read it somewhere. It's not the official MS name. It seems to be just an MDL thing.
     
  7. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,681
    103,548
    450
    Better, It's an original MDL development.
     
  8. jasburbak

    jasburbak MDL Novice

    Aug 18, 2019
    2
    0
    0
    Just for clarification, the title for this repository link says Win 10 Enterprise (IoT) 2021 LTSC SVF(SFX) Repo (EVAL en-US > xx-XX FULL).
    Is this the EVAL for the IoT or the LTSC version as it lists both in the title?

    Since I want LTSC, instead of using luzeadev's method of activation, can I use massgravels kms38? Is there a difference of convenience?

    And also, if im running 2019 LTSC, after mounting the iso, and running setup.exe ; do I have to reapply kms38 or is my previous activation still valid with the upgrade to LTSC 2021?

    Thanks!
     
  9. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,681
    103,548
    450
    The EVAL ISO is the source ISO for creating all shown SVF(SFX) patches, including the IoT Enterprise 2021 LTSC en-US ISO.

    Both can be set to use KMS38 instead of HWID.

    I don't believe KMS38 activation is online registered/saved, so for clean installs it will be needed to re0run it, but i never upgraded a KMS38 activated 2019 LTSC to 2021 LTSC, i always use HWID.
     
  10. jasburbak

    jasburbak MDL Novice

    Aug 18, 2019
    2
    0
    0
    Understood, so if I want to create a full version of IoT I use the
    023602a75645d334b6d81b0ce9115a99922505fb *en-us_windows_10_iot_enterprise_ltsc_2021_x64_dvd_257ad90f.exe

    and if I want to create a full version of LTSC I use the
    0481d50580b49f9f64be26b62655858ca06b8993 *en-us_windows_10_enterprise_ltsc_2021_x64_dvd_d289cf96.exe

    from the same source ISO - applicable to both.

    Thanks Enthousiast.

    When I upgrade from 2019 to 2021, I'll post the results whether activation is still valid or requires reapplication.
     
  11. JJR70

    JJR70 MDL Novice

    Jun 17, 2019
    1
    0
    0
    Hi guys,

    Did a search, but nothing came up for this.

    Is there any specific version I should install / use for Australia?

    And LTSC 2021 does work with Alder Lake CPUs, yes?

    Many thanks :)
     
  12. Kevinot

    Kevinot MDL Novice

    Jun 10, 2018
    43
    13
    0
    IS there any registry tweak/hack that enables clipboard to show history from text Copied from Private Tabs? THe clipboard history used to work fine with 2018 but in 2021 ISOs they have nuked this feature.
     
  13. oigroigm

    oigroigm MDL Novice

    Jan 29, 2022
    3
    0
    0
    I have installed w10 ltsc non-iot, i activated with the change to w10 iot now how do i get a w10 non-iot back?
     
  14. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,681
    103,548
    450
    #1740 Enthousiast, Jan 31, 2022
    Last edited: Jan 31, 2022
    (OP)
    Run winactivate (check my sig), it will simply activate it with KMS38 or run KMS_VL_ALL and it will activate it with KMS.

    HWID activation will switch it back to IoT Enterprise 2021 LTSC.