massgravel/massgrave.dev
1
0
Fork 0
mirror of https://github.com/massgravel/massgrave.dev.git synced 2024-11-23 23:10:55 +07:00
Code Issues Actions Packages Projects Releases Wiki Activity
4f1b1643ea
massgrave.dev/oem-folder.md

5.2 KiB
Raw Blame History

pagetitle
OEM Folders

$OEM$ Folders

(Windows Pre-Activation)

Overview

  • To create a pre-activated Windows installation .iso, do the following:

  • Extract the $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, 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 for activation method details and select the activation method as per your requirement.

Edit ISO File

  • 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 the steps below.

  • Download AnyBurn Free Portable and extract this zip file

  • Run the file named AnyBurn(64-bit)\AnyBurn.exe

  • Select the option named Edit image file

  • Follow the on-screen instructions and add the $OEM$ folder to the sources folder so that the directory will appear like this: \sources\$OEM$

  • Save the ISO, that's it.

Limitations

  • 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 the OEM channel.

  • The solution for this issue is to use (Non-Iot) Windows 10 Enterprise LTSC ISO, and the HWID method in preactivation will use Iot LTSC key to change the edition.

KMS38 - Server Cor/Acor

  • Windows Server Cor/Acor (No GUI) editions don't have the clipup.exe file.

  • To KMS38 activate it, you need to download the missing ClipUp.exe file from this link.

    File: ClipUp.exe
    SHA-256: 0d6e9f6bbd0321eda149658d96040cb4f79e0bd93ba60061f25b28fecbf4d4ef

    This file has digital signatures that can be verified. You can also get this file from the 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

  • The activation script will check ClipUp.exe in the current folder (from where script is running) and will use it accordingly.

HWID

  • When using HWID activation, no files are stored on the system, and Windows 10-11 will be activated when connected to the internet for the first time.

Ohook

  • If Office is preinstalled then Ohook method will activate the Office immediately without Internet. This activation uses custom sppc.dll file for the activation.

KMS38

  • When using KMS38 activation, no files are stored on the system, and Windows 10-11-Server becomes activated immediately without Internet.

Online KMS

  • When using Online KMS activation, Windows-Server and Office (Preinstalled) both will be activated when connected to the internet for the first time. This option uses a renewal task for lifetime activation.

HWID + Ohook

  • In this method, Windows 10-11 will be activated with HWID, and Office (Preinstalled) will be activated using Ohook.

HWID + Online KMS

  • In this method, Windows 10-11 will be activated with HWID, and Office (Preinstalled) will be activated using Online KMS.

KMS38 + Ohook

  • In this method, Windows 10-11-Server will be activated with KMS38, and Office (Preinstalled) will be activated using Ohook.

KMS38 + Online KMS

  • In this method, Windows 10-11-Server will be activated with KMS38, and Office (Preinstalled) will be activated using Online KMS.

Online KMS + Ohook

  • In this method, Windows-Server will be activated with Online KMS, and Office (Preinstalled) will be activated using Ohook.