At 2 AM, when awuctl came up with the info that 2016 ltsb wasn't even needed, it all worked flawlessly at 2:17 AM, as shown.
I tried it at least 1 hour before that but didn't work. When MSFT servers have an issue, it doesn't necessarily affect all.
I can't test 1.4, as you know, once established it keeps working on my VMs when the key gets inserted.
You can try virtual box if you want. EnterpriseSN LTSC still doesn't work on my end, anyways I've added the key.
Sorry. But I don't understand how I'm related with it? I have not given you or recommended any activation keys or methods. So please explain your comment.
I did last night, not working, not with the other keys from @awuctl either, will run another test when i am back, have to go out in a minute.
Now that all information was discussed, can any admin / moderator please remove this thread? It’ll be the best for MDL.
use key ending with P39PB for regular ltsc , other key ( ltsc 2019 mak from gatherosstate not workings )
Probably true, though I have to admit this was (?) a fun thread. I managed to create quite a few LTSC HWIDs on several systems. All I need to do now is incorporate the set-key commands in my PE Apply/ Autohotkey/ HoutjeTouwtje code, but this shouldn't be a problem as it worked before with LTSB. Thank you all! (Entuzjasta: Nice Gifs!)
EnterpriseSN is not supported by the Store (as was the case with EnterpriseS before). If and when they add it, all of the keys mentioned before will work normally. I don't expect that to change though.