(Windows Pre-Activation)
To create a pre-activated Windows installation .iso, do the following things:
Extract $OEM$
folder to the desktop using the MAS
script.
Copy the $OEM$
folder to the sources
folder in the Windows installation media (.iso or USB).
The directory will appear like this: \sources\$OEM$
in your altered .iso or on your bootable USB drive.
Now use this .iso or bootable USB drive to install Windows and it will either already be activated (KMS38) as soon as it boots or will self-activate (HWID or Online KMS) at the first internet contact.
You can check here about activation method details and select the activation method as per your requirement.
As stated above, you can copy the $OEM$
folder to
your bootable USB so you don’t have to edit the ISO file, however if you
need to then follow below steps.
Extract the ISO file with an archive software like 7-zip or Winrar.
Add the mentioned folder to the specified location.
Run MakeISO.reg by Aveyo. Mirror.
Right click on extracted ISO folder and select
MakeISO
option.
That’s it.
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
LTSC because installed key is of OEM channel.
The solution for this issue is to use (Non-Iot) Windows 10 Enterprise LTSC ISO and HWID method in preactivation will use Iot LTSC key to change the edition.
Windows Server Cor/Acor (No GUI) editions don’t have
clipup.exe
file.
To KMS38 activate it, you need to download
ClipUp.exe
file from this
link.
File: ClipUp.exe
SHA-256: 0d6e9f6bbd0321eda149658d96040cb4f79e0bd93ba60061f25b28fecbf4d4ef
This file has digital signatures which can be verified. You can also get
this file from official Windows
Server 2016 x64 RTM ISO.
Put the ClipUp.exe
beside the KMS38 Activation
script. That would be either MAS_AIO.cmd
or
KMS38_Activation.cmd
Activation script will check ClipUp.exe
in the
current folder (from where script is running) and will use it
accordingly.