I have no clue when they added it to the Store so it may just be a temporary issue. Seems like a simple f**kup on Microsoft's part to me so I wouldn't expect it though. I'll look into it some other time.
@whatever127 published all on MDL approx. 4 years ago, maybe it's still there, in the gatherosstate thread.
Did you modify 1.3 or is this an official new version, because the correctly modified 1.3 did the trick: https://forums.mydigitallife.net/th...-1809-got-hwid-infos-only.82183/#post-1612571 ps, did you enter the partial key or full key?
I think LTSC HWID is having some issues, when I tried the first time it didn't work for me, however in my later attempts after few hours it worked, and later on another machine, it worked without a problem. Try it in VM and see if it works for you.
Did he use another version than i did when it worked the first try? Because his code is partially shown, mine was fully shown.
The Key is fully shown when the script installs it but partially shown when the key is already installed.
Risking to get a ban, keeping the discussion going, in what scenario would that key already be inserted?
I think that MSFT servers are having hiccups with it, when I was testing that 2016 LTSB installation thing, at that time I already tested the script with adding the key, and it didn't work (later worked). In 1.4 only key is added and a slight change in PowerShell command switch (which is not a problem) and it works on a fresh installed Windows on my side.