Compare commits
14 Commits
24b93c98f5
...
dd873e7826
| Author | SHA1 | Date | |
|---|---|---|---|
| dd873e7826 | |||
|
4c09f8e943 | ||
|
|
29c7033983 | ||
| ffe328cee1 | |||
|
|
32e1ff48e8 | ||
| b2a115a352 | |||
| 66226f02ab | |||
| 172b822547 | |||
|
|
dcfa95441a | ||
|
|
488f2f6b9f | ||
|
|
55cfef9f9a | ||
|
|
b1b11235ab | ||
| 1e1f9bd754 | |||
|
|
e651f3d9d7 |
@ -1 +1 @@
|
||||
This site https://massgrave.dev/ is built using [Docusaurus](https://docusaurus.io/).
|
||||
This site (https://massgrave.dev/) is built using [Docusaurus](https://docusaurus.io/).
|
||||
|
||||
@ -38,20 +38,20 @@ C02D8FE6-5242-4DA8-972F-82EE55E00671 - Microsoft2024 VL - Microsoft::LTS
|
||||
- Learn more about Office update channels here https://learn.microsoft.com/microsoft-365-apps/updates/overview-update-channels
|
||||
- You can fetch the latest Office build numbers here https://github.com/ItzLevvie/Office16/blob/master/defconfig
|
||||
- The official method to change the update channel is taken from these URLs
|
||||
https://techcommunity.microsoft.com/t5/office-365-blog/how-to-manage-office-365-proplus-channels-for-it-pros/ba-p/795813
|
||||
- The script has the above list in the database and offers to choose only the Officially supported change path.
|
||||
https://techcommunity.microsoft.com/t5/office-365-blog/how-to-manage-office-365-proplus-channels-for-it-pros/ba-p/795813
|
||||
- The script has the above list in the database and offers only officially supported upgrades.
|
||||
|
||||
### VL (LTSC) channel limitations
|
||||
(Applicable to 2019/21/24 VL)
|
||||
|
||||
Officially, the update channel can not be changed to/from the VL (LTSC) channel to/from any other channel.
|
||||
So if the Office installation file or installed channel is from the VL (LTSC) channel, then only that channel will appear in the script
|
||||
also if your update channel is not from the LTSC channel, then the script won't Offer you the option to change the channel to LTSC.
|
||||
also if your update channel is not from the LTSC channel, then the script won't offer you the option to change the channel to LTSC.
|
||||
|
||||
### Windows 7/8/8.1 limitations
|
||||
|
||||
Office C2R is officially not supported on Windows [7](https://learn.microsoft.com/microsoft-365-apps/end-of-support/windows-7-support) / [8](https://learn.microsoft.com/microsoft-365-apps/end-of-support/windows-8-support) / [8.1](https://learn.microsoft.com/microsoft-365-apps/end-of-support/windows-81-support) anymore.
|
||||
The last available build is fixed on certain builds and won't get any updates. VL (LTSC) channels are not supported on these Windows versions so they won't appear in the script.
|
||||
The last available build is fixed and won't get any updates. VL (LTSC) channels are not supported on these Windows versions so they won't appear in the script.
|
||||
|
||||
---
|
||||
|
||||
|
||||
@ -1,16 +1,16 @@
|
||||
# Change Windows Edition
|
||||
|
||||
- You can find this option in the MAS extras section.
|
||||
- It can change the Windows 7-8-8.1-10-11 and their Server equivalent editions.
|
||||
- The script incorporates 4 methods for edition changing:
|
||||
- It can change Windows versions 7 through 11 and the equivalent server editions.
|
||||
- The script incorporates four methods for edition changing:
|
||||
- May's DISM Api Method - Used in Windows 10/11 Core to Non-Core edition change
|
||||
- [slmgr /ipk Method](https://learn.microsoft.com/windows/deployment/upgrade/windows-edition-upgrades#upgrade-using-a-command-line-tool) - Used in Windows 10/11 where edition license files are already there
|
||||
- [slmgr /ipk Method](https://learn.microsoft.com/windows/deployment/upgrade/windows-edition-upgrades#upgrade-using-a-command-line-tool) - Used for Windows 10/11 virtual editions
|
||||
- [DISM Method](https://learn.microsoft.com/windows-server/get-started/upgrade-conversion-options) - Used in Server 2016 and later server versions
|
||||
- [CBS Upgrade Method](https://github.com/asdcorp/Set-WindowsCbsEdition) - Used in Windows versions before 10
|
||||
- Available editions that can be changed to are shown in the script based on all these 4 options.
|
||||
- The script is future-proof, which means that it won't need an update upon the release of new Windows / Server editions and can get the required product key from the system itself.
|
||||
- The script blocks changing to CountrySpecific, ServerRdsh, and to/from CloudEdition editions since it's officially not supported and the user may face issues.
|
||||
- The script cannot change,
|
||||
- The script will show editions available via any of the four methods.
|
||||
- The script is future-proof, which means that it won't need an update upon the release of new editions because it can get the required product key from the system itself.
|
||||
- The script blocks changing to CountrySpecific, ServerRdsh, and to/from CloudEdition editions since it's not officially supported and the user may face issues.
|
||||
- The script cannot change
|
||||
- Non-Core editions to Core editions (For example, Pro > Home isn't available)
|
||||
- GAC editions to LTSC editions (For example, Enterprise > Enterprise LTSC isn't available)
|
||||
|
||||
@ -24,11 +24,11 @@ If you want to manually change the edition instead of using the script, please f
|
||||
|
||||
- To view the list of available editions, open the command prompt as admin and enter
|
||||
`dism /online /english /Get-TargetEditions`
|
||||
- Get the keys for the desired edition from [here](hwid.md#supported-products)
|
||||
- Get a key for the desired edition from [here](hwid.md#supported-products)
|
||||
- If you are upgrading from Home to Pro, you will need to disable the Internet before performing the upgrade.
|
||||
- Now enter that product key with this command, replace `<product_key>` with the actual key.
|
||||
`changepk.exe /ProductKey <product_key>`
|
||||
- In the Home to Pro upgrade, it may show an error, restart the system anyway. (Use the script if it's still not working)
|
||||
- In a Home to Pro upgrade, it may show an error, restart the system anyway. (Use the script if it's still not working)
|
||||
- Activate the changed edition with MAS, that's all.
|
||||
|
||||
### Windows Server 2016 and Later
|
||||
|
||||
@ -6,9 +6,9 @@ Basics
|
||||
------
|
||||
| | HWID | Ohook | KMS38 | Online KMS | TSforge (ZeroCID) |
|
||||
| --- | :---: | :---: | :---: | :---: | :---: |
|
||||
| Does not require internet connection | ❌ | ✅ | ✅ | ❌ | ✅ |
|
||||
| Works offline | ❌ | ✅ | ✅ | ❌ | ✅ |
|
||||
| Activation is permanent | ✅ | ✅ | ✅[^1] | ✅[^2] | ✅ |
|
||||
| Does not leave any files in the system to keep the activation status | ✅ | ❌ | ✅ | ❌ | ✅ |
|
||||
| Does not leave any files in the system to maintain activation status | ✅ | ❌ | ✅ | ❌ | ✅ |
|
||||
|
||||
Persistence
|
||||
-----------
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
|
||||
Please feel free to share feedback regarding bug reports, documentation errors, troubleshooting, etc. using the links below.
|
||||
|
||||
- [Discord](https://discord.gg/j2yFsV5ZVC) ❤️ (signup not required) - Discussion
|
||||
- [Discord](https://discord.gg/j2yFsV5ZVC) ❤️ (no signup required) - Discussion
|
||||
- [Reddit](https://www.reddit.com/r/MAS_Activator/)
|
||||
- [Bluesky](https://bsky.app/profile/massgrave.dev)
|
||||
- [Twitter](https://twitter.com/massgravel)
|
||||
|
||||
12
docs/hwid.md
12
docs/hwid.md
@ -7,11 +7,11 @@
|
||||
- This activation method does not store or modify any files in your system.
|
||||
- This activation method gives you permanent Windows activation for your system hardware.
|
||||
- All activations can be linked to a Microsoft account without any issues.
|
||||
- Once the system is activated, this activation cannot be removed because the license is stored in the Microsoft servers and not in the user's system. MS checks the hardware ID (HWID) and if a license is found in their database, the system will automatically activate. This is how official digital license works.
|
||||
- Once the system is activated, this activation cannot be removed because the license is stored on Microsoft's servers, not on the user's system. Microsoft checks the hardware ID (HWID), and if a license is found in their database, the system will automatically activate. This is how all digital licenses work.
|
||||
- Any significant changes to the hardware (such as a motherboard) may deactivate the system. It is possible to reactivate a system that was deactivated because of significant hardware changes, IF your activation, was linked to an online Microsoft account.
|
||||
- For activation to succeed, internet connectivity must be enabled. If you are trying to activate without these conditions being met, then the system will auto-activate later when the conditions are met.
|
||||
- For activation to succeed, Internet connectivity must be enabled. If you are trying to activate without these conditions being met, then the system will auto-activate later when the conditions are met.
|
||||
- The following is required for Windows to reactivate itself after Windows reinstall:
|
||||
- The internet is required. (Only at the time of activation)
|
||||
- Internet connectivity is required. (Only at the time of activation)
|
||||
- The system will auto-activate only if Retail (Consumer) media was used for installing Windows.
|
||||
- The system will NOT auto-activate if VL (Business) media was used for the installation. In this case, the user will have to insert the generic Retail/OEM key corresponding to the Windows edition currently running to activate if the user doesn't want to use the script again. (Those keys can be found below on this page)
|
||||
|
||||
@ -83,7 +83,7 @@ Now a question, can Microsoft block the new requests or revoke already establish
|
||||
:::info
|
||||
|
||||
- Systems in all architectures (x86, x64 and arm64) are supported.
|
||||
- Any Evaluation version of Windows (i.e. 'EVAL' LTSB/C) [cannot be activated](evaluation_editions.md) beyond the evaluation period. You can use TSforge option in MAS to reset the activation any given time.
|
||||
- Any evaluation version of Windows (i.e. 'EVAL' LTSB/C) [cannot be activated](evaluation_editions.md) beyond the evaluation period. You can use TSforge option in MAS to reset the activation any given time.
|
||||
- IoTEnterpriseS (LTSC) 2021 key will be used to activate the unsupported EnterpriseS (LTSC) 2021 edition.
|
||||
- IoTEnterpriseS (LTSC) 2024 key will be used to activate the unsupported EnterpriseS (LTSC) 2024 edition.
|
||||
- Windows Server does not support HWID activation.
|
||||
@ -96,7 +96,7 @@ Now a question, can Microsoft block the new requests or revoke already establish
|
||||
## How to remove HWID?
|
||||
|
||||
- **HWID (Digital license) activation cannot be removed** because the license is stored in the Microsoft servers and not in the user's system.
|
||||
- Microsoft checks the hardware ID (HWID) and if a license is found in their database, the system will automatically activate. This is how Official digital license activation process works.
|
||||
- Microsoft checks the hardware ID (HWID) and if a license is found in their database, the system will automatically activate. This is how the official digital license activation process works.
|
||||
|
||||
**What if you still want to remove it?**
|
||||
|
||||
@ -132,7 +132,7 @@ This guide is for manually creating the same kind of tickets that are used in th
|
||||
https://download.microsoft.com/download/9/A/E/9AE69DD5-BA93-44E0-864E-180F5E700AB4/adk/Installers/14f4df8a2a7fc82a4f415cf6a341415d.cab
|
||||
- Find the file named `filf8377e82b29deadca67bc4858ed3fba9` (Size: 330 KB) and rename it to `gatherosstate.exe`.
|
||||
- Make a folder named `Files` in the root of the C: drive (`C:\Files`) and copy the `gatherosstate.exe` file to that folder.
|
||||
- Make sure you have a working internet connection.
|
||||
- Make sure you have a working Internet connection.
|
||||
- Open Windows PowerShell as Administrator and enter the following commands.
|
||||
- Copy the entire block of code below and enter it in PowerShell to patch the `gatherosstate.exe` file. The patches are based on [GamersOsState](https://github.com/asdcorp/GamersOsState).
|
||||
```
|
||||
|
||||
@ -23,7 +23,7 @@ Open-source Windows and Office activator featuring HWID, Ohook, TSforge, KMS38,
|
||||
```
|
||||
irm https://get.activated.win | iex
|
||||
```
|
||||
Alternatively, you can use the following (It will be deprecated in the future.)
|
||||
Alternatively, you can use the following (this will be deprecated in the future):
|
||||
```
|
||||
irm https://massgrave.dev/get | iex
|
||||
```
|
||||
@ -41,14 +41,14 @@ irm https://massgrave.dev/get | iex
|
||||
<details>
|
||||
<summary>Click here to view</summary>
|
||||
|
||||
1. Download the file using the links provided below.
|
||||
1. Download the file using one of the links below:
|
||||
`https://github.com/massgravel/Microsoft-Activation-Scripts/archive/refs/heads/master.zip`
|
||||
or
|
||||
`https://git.activated.win/massgrave/Microsoft-Activation-Scripts/archive/master.zip`
|
||||
2. Right-click on the downloaded zip file and extract
|
||||
3. In the extracted folder, find the folder named `All-In-One-Version`
|
||||
4. Run the file named `MAS_AIO.cmd`
|
||||
5. You will see the activation options, follow the on-screen instructions.
|
||||
2. Right-click on the downloaded zip file and extract it.
|
||||
3. In the extracted folder, find the folder named `All-In-One-Version`.
|
||||
4. Run the file named `MAS_AIO.cmd`.
|
||||
5. You will see the activation options. Follow the on-screen instructions.
|
||||
6. That's all.
|
||||
|
||||
</details>
|
||||
@ -57,17 +57,17 @@ or
|
||||
|
||||
### Not working ❓
|
||||
|
||||
- If you are **unable to launch MAS** using the PowerShell method, please refer to **Method 2** listed above.
|
||||
- If MAS is launched and the script shows any errors, check for any troubleshooting steps mentioned in blue color and try to follow those.
|
||||
- If you have any issues, please feel free to reach out to us [here](troubleshoot.md).
|
||||
- If you are **unable to launch MAS** using the PowerShell method, please refer to **Method 2** above.
|
||||
- If MAS launches but displays errors, check for troubleshooting steps highlighted in blue and follow them.
|
||||
- If issues persist, feel free to reach out to us [here](troubleshoot.md).
|
||||
|
||||
---
|
||||
|
||||
:::note
|
||||
|
||||
- The IRM command in PowerShell downloads a script from a specified URL, and the IEX command executes it.
|
||||
- Always double-check the URL before executing the command and verify the source if manually downloading files.
|
||||
- Be cautious, as some spread malware disguised as MAS by using different URLs in the IRM command.
|
||||
- Always double-check the URL before executing the command and verify the source is trustworthy when manually downloading files.
|
||||
- Be cautious, as some spread malware disguised as MAS by changing the URL in the IRM command.
|
||||
|
||||
:::
|
||||
|
||||
|
||||
@ -16,15 +16,15 @@
|
||||
- In the Windows major upgrade process, the system uses `gatherosstate.exe` to carry over the remaining KMS activation period. It does this by creating a ticket that can be used offline.
|
||||
- The trick is that we can fool the `gatherosstate.exe` about the remaining KMS activation period and manually put the desired period maximum up to January 19, 2038, 03:14:07 UTC.
|
||||
- Why is it limited to the year 2038?
|
||||
It's related to the [Y2K38 problem](https://en.wikipedia.org/wiki/Year_2038_problem) as this date (19 January 2038 03:14:07 UTC) is the maximum date we can give to `gatherosstate.exe` without it looping back to the year 1970.
|
||||
This is due to the [Y2K38 problem](https://en.wikipedia.org/wiki/Year_2038_problem). This date (19 January 2038, 03:14:07 UTC) is the maximum value that can fit into a signed 32 bit integer.
|
||||
- How can we convince the gatherosstate.exe?
|
||||
There are two methods for it.
|
||||
**1-** Place a [custom slc.dll](https://github.com/asdcorp/Integrated_Patcher_3) file beside gatherosstate.exe:
|
||||
gatherosstate.exe uses the system's `C:\Windows\System32\slc.dll` file to gather the system's info. If we place a custom slc.dll file beside gatherosstate.exe which can send the rubbish data to it, then it will simply accept it and generate a valid ticket allowing activation up to January 19, 2038, 03:14:07 UTC.
|
||||
**2-** [Modify](https://github.com/asdcorp/GamersOsState) the gatherosstate.exe file itself so that it doesn't check the system's activation status and we can put the activation period as we wish.
|
||||
- **Notes:**
|
||||
- To be clear, we are **not modifying/patching any on-board system file** to get the ticket. Gatherosstate.exe is a part of the ISO file and not available in C drive system files. The system's slc.dll file is not touched; Instead, we use custom slc.dll only for a brief moment of ticket generation.
|
||||
- Latest MAS doesn't use any of these methods; Instead, it uses ready-to-use Universal tickets (check below for manual activation info).
|
||||
- To be clear, we are **not modifying/patching any on-board system file** to get the ticket. Gatherosstate.exe is a part of the ISO file and not available in C drive system files. The system's slc.dll file is not touched; instead, we use custom slc.dll only for a brief moment of ticket generation.
|
||||
- Latest MAS doesn't use any of these methods; instead, it uses ready-to-use Universal Tickets (check below for manual activation info).
|
||||
|
||||
**Q:** Can Microsoft block this kind of activation?
|
||||
**A:** Not directly. They could only update Clipup to allow for a maximum activation period of 180 days. Not much besides that can be done on their part. The tickets are not sent to Microsoft at all, so they can't block them or take action directly.
|
||||
@ -129,7 +129,7 @@
|
||||
:::info
|
||||
|
||||
- Systems in all architectures (x86, x64 and arm64) are supported.
|
||||
- Any Evaluation version of Windows (i.e. 'EVAL' LTSB/C) [cannot be activated](evaluation_editions.md) beyond the evaluation period. You can use TSforge option in MAS to reset the activation any given time.
|
||||
- Any evaluation version of Windows (i.e. 'EVAL' LTSB/C) [cannot be activated](evaluation_editions.md) beyond the evaluation period. You can use the TSforge option in MAS to reset the activation at any time.
|
||||
- KMS38 only supports Windows/server version 14393 (1607) and newer versions.
|
||||
- Initial release (19044.1288) of Iot LTSC 2021 doesn't support KMS license and it was added later in update 19044.2788.
|
||||
- Server Azure Datacenter (ServerTurbine) edition does not support activation on non-azure systems.
|
||||
@ -193,7 +193,7 @@ This guide is for manually creating the same kind of tickets that are used in th
|
||||
https://download.microsoft.com/download/9/A/E/9AE69DD5-BA93-44E0-864E-180F5E700AB4/adk/Installers/14f4df8a2a7fc82a4f415cf6a341415d.cab
|
||||
- Find the file named `filf8377e82b29deadca67bc4858ed3fba9` (Size: 330 KB) and rename it to `gatherosstate.exe`.
|
||||
- Make a folder named `Files` in the root of the C: drive (`C:\Files`) and copy the `gatherosstate.exe` file to that folder.
|
||||
- Make sure you have a working internet connection.
|
||||
- Ensure you have a working Internet connection.
|
||||
- Open Windows PowerShell as Administrator and enter the following commands.
|
||||
- Copy the entire block of code below and enter it in PowerShell to patch the `gatherosstate.exe` file. The patches are based on [GamersOsState](https://github.com/asdcorp/GamersOsState).
|
||||
```
|
||||
|
||||
22
docs/news.md
22
docs/news.md
@ -1,12 +1,12 @@
|
||||
# News
|
||||
|
||||
### [14-Feb-25] MAS 3.0 update is released
|
||||
A new method "TSforge" is added, for details check [changelog](changelog.md)
|
||||
A new method "TSforge" is added, for details check the [changelog](changelog.md)
|
||||
|
||||
### [20-Dec-24] MAS 2.9 update is released
|
||||
[changelog](changelog.md)
|
||||
|
||||
### [19-Nov-24] Added November updated ISO's
|
||||
### [19-Nov-24] Added November updated ISOs
|
||||
Windows 10 22H2 / Windows 11 24H2 / Server 2025 / Server 2022 / Server 23H2
|
||||
https://massgrave.dev/genuine-installation-media
|
||||
|
||||
@ -16,14 +16,14 @@ https://massgrave.dev/genuine-installation-media
|
||||
### [1-Nov-24] Guide: Windows 10 Updates After End-Of-Life
|
||||
https://massgrave.dev/windows10_eol
|
||||
|
||||
### [16-Oct-24] Added October updated ISO's
|
||||
### [16-Oct-24] Added October updated ISOs
|
||||
Windows 10 22H2 / Windows 11 23H2 / Server 2022 / Server 23H2
|
||||
https://massgrave.dev/genuine-installation-media
|
||||
|
||||
### [2-Oct-24] Added MVS links for Win11 24H2 and LTSC 2024
|
||||
https://massgrave.dev/genuine-installation-media
|
||||
|
||||
### [18-Sep-24] Added: September updated ISO's for Windows 10/11/Server 2022
|
||||
### [18-Sep-24] Added: September updated ISOs for Windows 10/11/Server 2022
|
||||
https://massgrave.dev/genuine-installation-media
|
||||
|
||||
### [6-Sep-24] MAS 2.7 update is released
|
||||
@ -33,25 +33,25 @@ Also, the MASSGRAVE blog is now live
|
||||
### [30-Aug-24] Extend expiry date of massgrave.dev/get to 31/12/2024
|
||||
Because it looks like some ISPs are flagging new URLs for up to 5-6 months
|
||||
|
||||
### [21-Aug-24] Added: August updated ISO's for Windows 10/11/Server 2022
|
||||
### [21-Aug-24] Added: August updated ISOs for Windows 10/11/Server 2022
|
||||
https://massgrave.dev/genuine-installation-media
|
||||
|
||||
### [14-Aug-24] Added a page for evaluation editions
|
||||
https://massgrave.dev/evaluation_editions
|
||||
|
||||
### [7-Aug-24] Server ISOs update
|
||||
Added last updated ISO's for Server 2016/2019
|
||||
Added VL ISO's for Server 2008 R2/2012 R2
|
||||
Added last updated ISOs for Server 2016/2019
|
||||
Added VL ISOs for Server 2008 R2/2012 R2
|
||||
|
||||
### [19-July-24] Update: HWID activation is not working due to server issue
|
||||
https://azure.status.microsoft/status
|
||||
https://x.com/massgravel/status/1814087318577308157
|
||||
Update- It was fixed after a few hours.
|
||||
|
||||
### [17-July-24] Added: July updated ISO's for Windows 10/11/Server 2022
|
||||
### [17-July-24] Added: July updated ISOs for Windows 10/11/Server 2022
|
||||
https://massgrave.dev/genuine-installation-media
|
||||
|
||||
### [20-June-24] Added: June updated ISO's for Windows 10/11/Server 2022
|
||||
### [20-June-24] Added: June updated ISOs for Windows 10/11/Server 2022
|
||||
https://massgrave.dev/genuine-installation-media
|
||||
|
||||
### [16-June-24] Office 2024 online installers are added
|
||||
@ -68,7 +68,7 @@ https://massgrave.dev/genuine-installation-media
|
||||
### [23-May-24] Added: Windows Server 2025 (Preview)
|
||||
https://massgrave.dev/genuine-installation-media
|
||||
|
||||
### [22-May-24] Added: May updated ISO's for Windows 10/11/Server 2022
|
||||
### [22-May-24] Added: May updated ISOs for Windows 10/11/Server 2022
|
||||
https://massgrave.dev/genuine-installation-media
|
||||
|
||||
### [20-May-24] `irm https://massgrave.dev/get | iex` is retiring
|
||||
@ -85,7 +85,7 @@ https://massgrave.dev/changelog#26
|
||||
### [19-Apr-24] Added office 2024 preview serializer for macOS
|
||||
https://massgrave.dev/office_for_mac
|
||||
|
||||
### [17-Apr-24] Added Apr updated ISO's and IoT LTSB 15/16 ISO's
|
||||
### [17-Apr-24] Added April updated ISOs and IoT LTSB 15/16 ISOs
|
||||
https://massgrave.dev/genuine-installation-media
|
||||
|
||||
### [16-Apr-24] Added office links for older macOS versions
|
||||
|
||||
@ -1,15 +1,15 @@
|
||||
# $OEM$ Folders
|
||||
|
||||
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.
|
||||
- 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.
|
||||
|
||||
:::warning
|
||||
|
||||
- On Windows 8 and later, [**running setupcomplete.cmd is disabled**](https://learn.microsoft.com/windows-hardware/manufacture/desktop/add-a-custom-script-to-windows-setup?view=windows-11#windows-setup-scripts) if the default installed key for the edition is from the OEM channel, except for Enterprise editions and Windows Server operating systems.
|
||||
- On Windows 8 and later, [**running setupcomplete.cmd is disabled**](https://learn.microsoft.com/windows-hardware/manufacture/desktop/add-a-custom-script-to-windows-setup?view=windows-11#windows-setup-scripts) if the default installed key for the edition is from the OEM channel, except for Enterprise editions and Windows Server.
|
||||
- However, in Windows 10, IoT Enterprise editions were not included in the Enterprise category list during the installation process. As a result, Enterprise with an OEM key can handle setupcomplete.cmd, but IoT Enterprise (LTSC) cannot. This was fixed in later Windows 11 versions.
|
||||
- In Windows 10 IoT Enterprise (LTSC), you can resolve this issue by using the Non-IoT Windows 10 Enterprise LTSC ISO. In this case, the HWID method in preactivation will install the IoT LTSC key to change the edition and enable HWID activation.
|
||||
- In Windows 11 IoT Enterprise (LTSC), it works fine as expected by default.
|
||||
@ -21,10 +21,10 @@ To create a pre-activated Windows installation .iso, do the following:
|
||||
## 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](https://www.anyburn.com/download.php) 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$`
|
||||
- Download [AnyBurn Free Portable](https://www.anyburn.com/download.php) and extract the 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.
|
||||
|
||||
------------------------------------------------------------------------
|
||||
|
||||
@ -1,3 +1,3 @@
|
||||
# Our Non-Piracy Site
|
||||
|
||||
We also operate https://gravesoft.dev/ where you can find stuff exclusive to non-piracy.
|
||||
We also operate https://gravesoft.dev/, where you can find exclusively non-piracy projects.
|
||||
|
||||
@ -4,7 +4,7 @@ All download links lead to genuine files only.
|
||||
|
||||
- [FAQ](genuine-installation-media.md#faq)
|
||||
- **You can permanently activate Windows 7 with TSforge option in MAS.**
|
||||
- Pro and Ultimate ISO's also contains other editions such as, Starter, Home Basic, Home Premium, Pro, Ultimate but by default they don't appear while installing Windows. You can easily choose any of them while installing and for that you need to delete or edit `sources\ei.cfg` file in the ISO.
|
||||
- Pro and Ultimate ISOs also contain other editions such as, Starter, Home Basic, Home Premium, Pro, Ultimate but by default they don't appear while installing Windows. You can easily choose any of them while installing and for that you need to delete or edit `sources\ei.cfg` file in the ISO.
|
||||
- To get latest updates on Windows 7 install, you can use [Simplix Pack](https://blog-simplix-info.translate.goog/updatepack7r2/?_x_tr_sl=ru&_x_tr_tl=en&_x_tr_hl=nl&_x_tr_pto=sc) or activate ESU with TSforge option in MAS.
|
||||
- Windows Embedded POSReady 7 ISO is available in English language only. You need to use language pack for other languages.
|
||||
|
||||
|
||||
@ -26,7 +26,7 @@ import TabItem from '@theme/TabItem';
|
||||
**Windows 8.1 Core / Pro**
|
||||
(Build - 9600.17415)
|
||||
|
||||
MSDL https://msdl.gravesoft.dev/#52 provides Official links straight from Microsoft.
|
||||
MSDL https://msdl.gravesoft.dev/#52 provides official links directly from Microsoft.
|
||||
|
||||
------------------------------------------------------------------------
|
||||
|
||||
|
||||
@ -3,7 +3,7 @@
|
||||
All download links lead to genuine files only.
|
||||
|
||||
- [FAQ](genuine-installation-media.md#faq)
|
||||
- You need ARM64 processor (CPU) to install Windows ARM64 architecture OS.
|
||||
- You need an ARM64 processor (CPU) to install Windows ARM64 architecture OS.
|
||||
|
||||
------------------------------------------------------------------------
|
||||
|
||||
@ -82,7 +82,7 @@ Build - 26100.1742
|
||||
**Windows 11 IoT Enterprise 24H2**
|
||||
**(Not LTSC)**
|
||||
Build - 26100.1742
|
||||
These ISO's contain below editions,
|
||||
These ISOs contain below editions,
|
||||
|
||||
Windows 11 Enterprise
|
||||
Windows 11 IoT Enterprise
|
||||
@ -102,7 +102,7 @@ ARM64 version for IoT Enterprise ISO is available only in English language.
|
||||
**Windows 11 IoT Enterprise LTSC 2024**
|
||||
|
||||
Build - 26100.1742
|
||||
These ISO's contain below editions.
|
||||
These ISOs contain below editions.
|
||||
|
||||
Windows 11 Enterprise LTSC
|
||||
Windows 11 IoT Enterprise LTSC
|
||||
@ -122,10 +122,10 @@ ARM64 version for LTSC is available only in English language.
|
||||
|
||||
**Old Versions**
|
||||
|
||||
- Download the [Official Microsoft ESD file](https://worproject.com/esd) and [ESD>ISO Converter](https://github.com/abbodi1406/WHD/raw/master/scripts/esd-decrypter-wimlib-65.7z) by [abbodi1406](https://forums.mydigitallife.net/threads/abbodi1406s-batch-scripts-repo.74197/),
|
||||
- Download the [official Microsoft ESD file](https://worproject.com/esd) and [ESD>ISO Converter](https://github.com/abbodi1406/WHD/raw/master/scripts/esd-decrypter-wimlib-65.7z) by [abbodi1406](https://forums.mydigitallife.net/threads/abbodi1406s-batch-scripts-repo.74197/),
|
||||
- Put the ESD file beside `decrypt.cmd` and run that script.
|
||||
- It will create the ISO file.
|
||||
- This process is same as how Official MCT tool creates Windows 10 and 11 ISOs.
|
||||
- This process is the same as how the official MCT tool creates Windows 10 and 11 ISOs.
|
||||
|
||||
------------------------------------------------------------------------
|
||||
|
||||
@ -219,10 +219,10 @@ ARM64 version for LTSC is available only in English language.
|
||||
|
||||
**Old Versions**
|
||||
|
||||
- Download the [Official Microsoft ESD file](https://worproject.com/esd) and [ESD>ISO Converter](https://github.com/abbodi1406/WHD/raw/master/scripts/esd-decrypter-wimlib-65.7z) by [abbodi1406](https://forums.mydigitallife.net/threads/abbodi1406s-batch-scripts-repo.74197/),
|
||||
- Download an [official Microsoft ESD file](https://worproject.com/esd) and [ESD>ISO Converter](https://github.com/abbodi1406/WHD/raw/master/scripts/esd-decrypter-wimlib-65.7z) by [abbodi1406](https://forums.mydigitallife.net/threads/abbodi1406s-batch-scripts-repo.74197/),
|
||||
- Put the ESD file beside `decrypt.cmd` and run that script.
|
||||
- It will create the ISO file.
|
||||
- This process is same as how Official MCT tool creates Windows 10 and 11 ISOs.
|
||||
- This process is the same as how the official MCT tool creates Windows 10 and 11 ISOs.
|
||||
|
||||
------------------------------------------------------------------------
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
|
||||
All download links lead to genuine files only.
|
||||
- [FAQ](genuine-installation-media.md#faq)
|
||||
- Microsoft provides Evaluation ISO public [links](https://www.microsoft.com/evalcenter) for Windows LTSC releases, but as the name states, those ISO's are for evaluation purposes and can not be activated for more than 90 days. Below listed ISOs are full version that can be activated.
|
||||
- Microsoft provides Evaluation ISO public [links](https://www.microsoft.com/evalcenter) for Windows LTSC releases, but as the name states, those ISOs are for evaluation purposes and can not be activated for more than 90 days. Below listed ISOs are full version that can be activated.
|
||||
|
||||
<details>
|
||||
<summary>What is LTSC, and is it the right choice for you?</summary>
|
||||
@ -155,7 +155,7 @@ You might want to check [Windows 10 EOL guide](windows10_eol.md).
|
||||
<details>
|
||||
<summary>How to clean install Windows 11 IoT Enterprise LTSC **2024** in Non-English language?</summary>
|
||||
|
||||
IoT LTSC edition ISO's are available in English language only. However, you can follow the below steps to clean install it.
|
||||
IoT LTSC edition ISOs are available in English language only. However, you can follow the below steps to clean install it.
|
||||
|
||||
- Download the non-IoT LTSC 2024 ISO in the desired language from the section below.
|
||||
- Follow [PID.txt method](https://gravesoft.dev/clean_install_windows#windows-11-on-unsupported-hardware) to install IoT version from scratch.
|
||||
@ -167,7 +167,7 @@ Alternatively, You can install Non-IoT LTSC in another language and later instal
|
||||
<details>
|
||||
<summary>How to clean install Windows 10 IoT Enterprise LTSC **2021** in Non-English language?</summary>
|
||||
|
||||
IoT LTSC edition ISO's are available in English language only.
|
||||
IoT LTSC edition ISOs are available in English language only.
|
||||
|
||||
When installing Windows 11 IoT Enterprise LTSC 2024 from scratch, one advantage is its relaxed hardware requirements. However, there isn't much benefit to doing the same with the 2021 IoT version, since you can easily change the Windows edition later. Additionally, the PID.txt method for installing the virtual edition from scratch is only applicable to Windows 11 24H2 and later versions. While there are other methods to install from scratch, they are more complex, and the results do not justify the effort.
|
||||
|
||||
@ -193,14 +193,14 @@ Our recommendation is as follows:
|
||||
|
||||
Build - 26100.1742
|
||||
|
||||
These ISO's contain below editions.
|
||||
These ISOs contain below editions.
|
||||
Windows 11 Enterprise LTSC
|
||||
Windows 11 IoT Enterprise LTSC
|
||||
Windows 11 IoT Enterprise Subscription LTSC
|
||||
|
||||
| Language | Arch | Link |
|
||||
|:---------|:-----|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| English | x64 | [X23-81951_26100.1742.240906-0331.ge_release_svc_refresh_CLIENT_ENTERPRISES_OEM_x64FRE_en-us.iso](https://oemsoc.download.prss.microsoft.com/dbazure/X23-81951_26100.1742.240906-0331.ge_release_svc_refresh_CLIENT_ENTERPRISES_OEM_x64FRE_en-us.iso_640de540-87c4-427f-be87-e6d53a3a60b4?t=2c3b664b-b119-4088-9db1-ccff72c6d22e&P1=102816950270&P2=601&P3=2&P4=OC448onxqdmdUsBUApAiE8pj1FZ%2bEPTU3%2bC6Quq29MVwMyyDUtR%2fsbiy7RdVoZOHaZRndvzeOOnIwJZ2x3%2bmP6YK9cjJSP41Lvs0SulF4SVyL5C0DdDmiWqh2QW%2bcDPj2Xp%2bMrI9NOeElSBS5kkOWP8Eiyf2VkkQFM3g5vIk3HJVvu5sWo6pFKpFv4lML%2bHaIiTSuwbPMs5xwEQTfScuTKfigNlUZPdHRMp1B3uKLgIA3r0IbRpZgHYMXEwXQ%2fSLMdDNQthpqQvz1PThVkx7ObD55CXgt0GNSAWRfjdURWb8ywWk1gT7ozAgpP%2fKNm56U5nh33WZSuMZIuO1SBM2vw%3d%3d) <br /> = <br /> [en-us_windows_11_iot_enterprise_ltsc_2024_x64_dvd_f6b14814.iso](https://drive.massgrave.dev/en-us_windows_11_iot_enterprise_ltsc_2024_x64_dvd_f6b14814.iso) <br /> <br /> Both files are identical, only name is different. <br /> 1st link is Official from the OEM portal, and 2nd file is taken from MVS and hosted on massgrave. <br /> Note: With 1st link file you need to rename extension to .iso |
|
||||
| English | x64 | [X23-81951_26100.1742.240906-0331.ge_release_svc_refresh_CLIENT_ENTERPRISES_OEM_x64FRE_en-us.iso](https://oemsoc.download.prss.microsoft.com/dbazure/X23-81951_26100.1742.240906-0331.ge_release_svc_refresh_CLIENT_ENTERPRISES_OEM_x64FRE_en-us.iso_640de540-87c4-427f-be87-e6d53a3a60b4?t=2c3b664b-b119-4088-9db1-ccff72c6d22e&P1=102816950270&P2=601&P3=2&P4=OC448onxqdmdUsBUApAiE8pj1FZ%2bEPTU3%2bC6Quq29MVwMyyDUtR%2fsbiy7RdVoZOHaZRndvzeOOnIwJZ2x3%2bmP6YK9cjJSP41Lvs0SulF4SVyL5C0DdDmiWqh2QW%2bcDPj2Xp%2bMrI9NOeElSBS5kkOWP8Eiyf2VkkQFM3g5vIk3HJVvu5sWo6pFKpFv4lML%2bHaIiTSuwbPMs5xwEQTfScuTKfigNlUZPdHRMp1B3uKLgIA3r0IbRpZgHYMXEwXQ%2fSLMdDNQthpqQvz1PThVkx7ObD55CXgt0GNSAWRfjdURWb8ywWk1gT7ozAgpP%2fKNm56U5nh33WZSuMZIuO1SBM2vw%3d%3d) <br /> = <br /> [en-us_windows_11_iot_enterprise_ltsc_2024_x64_dvd_f6b14814.iso](https://drive.massgrave.dev/en-us_windows_11_iot_enterprise_ltsc_2024_x64_dvd_f6b14814.iso) <br /> <br /> Both files are identical, only name is different. <br /> 1st link is from the official OEM portal, and 2nd file is taken from MVS and hosted on massgrave. <br /> Note: With 1st link file you need to rename extension to .iso |
|
||||
|
||||
---
|
||||
|
||||
@ -258,7 +258,7 @@ Build - 26100.1742
|
||||
|
||||
(Build - 19044.1288)
|
||||
|
||||
These ISO's contain below editions.
|
||||
These ISOs contain below editions.
|
||||
Windows 10 Enterprise LTSC
|
||||
Windows 10 IoT Enterprise LTSC
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ All download links lead to genuine files only.
|
||||
## Windows Server 2025
|
||||
|
||||
Build - 26100.1742
|
||||
The below ISO's links are taken from the Official OEM portal.
|
||||
The below ISO links are taken from the Official OEM portal.
|
||||
Note: You need to rename extension to .iso after file is downloaded.
|
||||
|
||||
| Language | Arch | Link |
|
||||
|
||||
@ -11,7 +11,7 @@ All download links lead to genuine files only.
|
||||
Windows Vista HomeBasic N
|
||||
Windows Vista Business N
|
||||
Windows Vista Starter
|
||||
Where N editions are available only in English language ISO's and Starter edition is available only in x86 version ISO.
|
||||
Where N editions are available only in English language ISOs and Starter edition is available only in x86 version ISO.
|
||||
- Business and Enterprise Editions can be activated with KMS-VL-ALL by qewlpal [Official thread](https://forums.mydigitallife.net/threads/kms-vl-all-online-offline-kms-activator-for-microsoft-products.63471/) - [Mirror](https://app.box.com/s/q0nyib6bfylosvbbm5x8ztg87vy0kl8a) (Use 7.2RC2 version from the mirror link)
|
||||
Other editions can be activated with Windows Loader by Daz [Official thread](https://forums.mydigitallife.net/forums/windows-loader.39/) - [Mirror](https://app.box.com/s/bnchc6hten44adunlcpz9ya9j0uucfs2)
|
||||
|
||||
|
||||
@ -3,9 +3,9 @@
|
||||
All download links lead to genuine files only.
|
||||
|
||||
- [FAQ](genuine-installation-media.md#faq)
|
||||
- For x86, SP3 and for x64, SP2 are the last released ISO's available. x64 SP2 version was released in English language only.
|
||||
- x86 VL ISO's can be activated with the key `XCYBK-2B3KV-G8T8F-WXJM7-WCTYT`
|
||||
- x64 VL ISO's can be activated with the key `VCFQD-V9FX9-46WVH-K3CD4-4J3JM`
|
||||
- For x86, SP3 and for x64, SP2 are the last released ISOs available. x64 SP2 version was released in English language only.
|
||||
- x86 VL ISOs can be activated with the key `XCYBK-2B3KV-G8T8F-WXJM7-WCTYT`
|
||||
- x64 VL ISOs can be activated with the key `VCFQD-V9FX9-46WVH-K3CD4-4J3JM`
|
||||
|
||||
------------------------------------------------------------------------
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user