after using string -u gatherosstate you find a lots of key only key for LTSC ending with -P39PB nonslp key working strange , LTSC nonslp key with rs5 others than -P39PB not working only nonslp key working for making a hwid, mak or oem Dm key are not a winner because mak are online key only and oem Dm are motherboards specific slic 3.0 gvlk key are specific to kms activations like kms_vl_all
Tested, worked flawless on an 5 month old install of Win10 "LTSC 1809 - 10.0.17763.1339". used MAS1.4 HWID.
I'm no expert, but isn't the ticket method only usable for retail channel installs? Why are people trying to use Volume MAK keys?
Enterprise don't have retail channel if you upgraded from Win 7/8.1 activated with KMS to Win 10 build 10586, you get permanent HWID based on MAK key so it's the same concept with EnterpriseS
For regular windows 10 like home or pro retail key are used, For enterpriseS ( ltsb or ltsc ) Oem:nonslp ( oem Non System Locked Preinstallation key are valid ) Nonslp = no motherboards specific Oem : DM motherboards specific For clean ltsc or ltsb if you use hwid for activation Open command prompt and write slmgr.vbs -dlv Windows indicate oem:nonslp for key type
AFAIK In other SKU's all non GVLK keys are valid for HWID, for instance, EnterpriseN (and Enterprise SN 10240, 14393) only have MAK in non GVLK section and HWID works fine with it. I once tested pro with MAK and it also worked. However, in the case of LTSC I tested it after your comment, and yes MAK and OEM: DM is not working for HWID. As per @awuctl
I guess maybe I don't understand it because I don't see all the different activations laid out in a graphic. I'm like one of those boomer execs that needs a simple graphic because I'm too dumb to understand without visualizing it.
windows 10 LTSC 1809 got hwid (infos only) No personal fights no links to external tools. It's about to get removed completely ...last chance... Btw 2 members have been sent to vacation until next Monday. I do not tolerate any name calling especially at such a thread...WTF?!
https://forums.mydigitallife.net/th...b-17763-xxx-pc-rs5.77945/page-51#post-1467631 N is available on the initial 17763.1 and the second refresh iso 17763.316.
actually this is no longer true as I recently found few other oem nonslp keys that do work with LTSC 2019 and activate via HWID see spoiler below (I'll discuss in secret by spoiler or PM only) Spoiler I used this key other than -P39PB to activate LTSC 2019 thru HWID; modded/edited the MAS HWID cmd script file to use a different key that uses the same "activation ID" as the P39PB key and it activated without problem
yes if you activate first time with PB39 key , later you have possibility to use multiple key ( OEMM / retail try this create vmware vm install ltsc only P39PB works for first time of activation