Microsoft-Activation-Scripts
Microsoft-Activation-Scripts copied to clipboard
massgravel
HWID activation using OEM folder always fails
The latest version 1.7 uses the OEM folder HWID to activate LTSC 2021. It always fails.
@mpamxl I suppose you are using Iot Enterprise LTSC ISO, in that case system blocks running OEM folder for preactivation.
On Windows 8 and later, running setupcomplete.cmd is disabled if the default installed key for the edition is OEM Channel. For example - Preactivation won’t work for Windows 10 Iot Enterprise because installed key is of OEM channel.
https://massgrave.dev/oem-folder.html#Overview
If you want to preactivate it then use non-iot enterprise LTSC ISO.
I am using LTSC 2021, not Iot Enterprise LTSC, but LTSC 2021 seems to be activated as Iot Enterprise LTSC. It has been fine before and can be activated normally, but now it always fails.
@mpamxl It's expected, LTSC 2021 doesn't support HWID, hence script installs Iot Key. https://massgrave.dev/hwid.html#Supported_Products
I know that the current problem is that after the OEM installs the Iot Key, it prompts to activate the network when it is turned on, but the activation always fails after connecting to the network.
I know that the current problem is that after the OEM installs the Iot Key, it prompts to activate the network when it is turned on, but the activation always fails after connecting to the network.
Restart doesn't help?
Yes, after restarting, it still shows that the network is activated, but I am already connected to the network, and sometimes it will directly change to Windows not activated after a while.
If you have such systems available at the moment or if you find this issue next time, pls reach out to us on https://discord.gg/gjJEfq7ux8 for a more detailed discussion.
The latest version 1.7 uses the OEM folder HWID to activate LTSC 2021. It always fails.
How's it know?
How's it know added a syncro universal line to the add shuffle auto flashes with bridging the gap performance Happens