massgrave/massgrave.dev
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update OEM folder page

Browse Source
This commit is contained in:
WindowsAddict
2024-04-14 02:39:49 +05:30
parent ef4aeb9bae
commit 52630e7e64
40 changed files with 51 additions and 60 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
docs/oem-folder.md
View File

@ -1,14 +1,20 @@
# $OEM$ Folders
(Windows Pre-Activation)
- To create a pre-activated Windows installation .iso, do the following:
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](intro.md) for activation method details and select the activation method as per your requirement.
:::warning
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 the default installed key is OEM. You can work around this issue by using Non-IoT Windows 10 Enterprise LTSC ISO, in which case the HWID method in preactivation will use IoT LTSC key to change the edition.
:::
------------------------------------------------------------------------
## Edit ISO File
@ -22,14 +28,6 @@
------------------------------------------------------------------------
## 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.