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

commit 1

Browse Source
This commit is contained in:
Lyssa 2023-10-24 17:46:54 +04:00 committed by GitHub
parent b5e55c4788
commit e8bf99c151
12 changed files with 155 additions and 155 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
bypass-russian-geoblock.md
View File

@ -24,13 +24,13 @@ We are unable to complete your request at this time. Some users, entities and lo
[MSDL](/msdl/)
It uses shared sessions/proxy to generate official download links in Russia and in all other blocked places.
It uses shared sessions/proxy to generate official download links in Russia and all other blocked places.
------------------------------------------------------------------------
## Office Download
Russian users face an error when they try to [download](genuine-installation-media.html) Office C2R with online installer or ODT.
Russian users face an error when they try to [download](genuine-installation-media.html) Office C2R with the online installer or ODT.
### Error
@ -41,9 +41,9 @@ We're sorry, we can't continue because we weren't able to download a required fi
![](https://lookimg.com/images/2023/03/24/QTAO3s.png)
#### How Microsoft is blocking it?
#### How is Microsoft blocking it?
It's primarily checking Russian IP address and basis on that above error is shown to users. However that's not the end of it. Once it find out that Russian IP is used then installer creates a below registry key to remember it. After that if you even use a VPN then installer will still keep showing the error.
Primarily, it checks for Russian IP addresses, and based on that, the above error is shown to users. However that's not the end of it. Once it find out that Russian IP is used, the installer creates the registry key below to remember it. After that, even if you use a VPN, the installer will still keep showing the error.
```
[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\ExperimentConfigs\Ecs]
@ -58,9 +58,9 @@ It's primarily checking Russian IP address and basis on that above error is show
reg add "HKCU\Software\Microsoft\Office\16.0\Common\ExperimentConfigs\Ecs" /v "CountryCode" /t REG_SZ /d "std::wstring|US" /f
```
After that office installer won't show any such errors. You can apply this before or after running the Office installer and you can download Office without any VPN and with your Russian IP address.
After that, the office installer won't show any related errors. You can apply this before or after running the Office installer and you can download Office without any VPN with your Russian IP address.
**2-** Use [Offline installer file](office_c2r_links.html) to install Office.
**2-** Use the [Offline installer file](office_c2r_links.html) to install Office.
------------------------------------------------------------------------

10
change_edition.md
View File

@ -10,19 +10,19 @@ pagetitle: Change Windows Edition
- It can change the Windows 7-8-8.1-10-11 and equivalent Server Editions.
- Script incorporates 4 methods for edition change:
- The script incorporates 4 methods for edition change:
- Alex (aka may, ave9858) DISM Api Method (Based on changepk.exe method but better)\
- slmgr /ipk Method\
- DISM Method\
- [CBS Upgrade method](https://github.com/asdcorp/Set-WindowsCbsEdition)
- Available editions for change are shown in the script basis on all these 4 options.
- Available editions for change are shown in the script based on all these 4 options.
- The script is future proof, which means on the release of new Windows / Server editions, the script doesn't need an update and can get the required key from the system itself.
- The script is future-proof, which means that upon the release of new Windows / Server editions, the script won't need an update and can get the required key from the system itself.
- Script blocks the change to CountrySpecific, ServerRdsh and to/from CloudEdition editions since it's officially not supported and the user may face issues.
- The script blocks the change to CountrySpecific, ServerRdsh and to/from CloudEdition editions since it's officially not supported and the user may face issues.
- The script can not change the Non-Core (Pro, Enterprise, etc) to Core (Home) edition.
- The script cannot change the Non-Core (Pro, Enterprise, etc) to Core (Home) edition.
------------------------------------------------------------------------

24
check_activation_status.md
View File

@ -9,32 +9,32 @@ pagetitle: Check Activation Status
MAS includes checking activation options (WMI/VBS) which are taken from abbodi1406's [KMS_VL_ALL](https://github.com/abbodi1406/KMS_VL_ALL_AIO/).\
It checks the status of Windows and Office products.
Please find below the difference between vbs and wmi options.
Please find below the difference between VBS and WMI options.
------------------------------------------------------------------------
## Check Activation Status [vbs]
## Check Activation Status [VBS]
- Query and execute official licensing VBScripts: slmgr.vbs for Windows, ospp.vbs for Office
- Queries and executes official licensing VBScripts: slmgr.vbs for Windows, ospp.vbs for Office.
- Shows the activation expiration date for Windows
- Shows the activation expiration date for Windows.
- Office 2010 ospp.vbs shows a very little info
- Office 2010 ospp.vbs shows very little information.
------------------------------------------------------------------------
## Check Activation Status [wmi]
## Check Activation Status [WMI]
- Query and execute WMI functions using wmic.exe or VBScripts
- Queries and executes WMI functions using wmic.exe or VBScripts.
- Shows extra info (SKU ID, key channel)
- Shows extra information (SKU ID, key channel).
- Shows the activation expiration date for all products
- Shows the activation expiration date for all products.
- Shows more detailed info for Office 2010
- Shows more detailed information for Office 2010.
- Can show the status of Office UWP apps
- Can show the status of Office UWP apps.
- Implement vNextDiag.ps1 functions to **detect new Office 365 vNext licenses and subscriptions**
- Implement vNextDiag.ps1 functions to **detect new Office 365 vNext licenses and subscriptions**.
------------------------------------------------------------------------

2
credits.md
View File

@ -4,7 +4,7 @@ pagetitle: Credits
# Credits
MAS project wouldn't be possible without kind help and uses of other honorable developer's tools and scripts. I would like to say thanks to all those wonderful people and projects.
The MAS project wouldn't be possible without the kind help and use of other honorable developers' tools and scripts. I would like to say thanks to all those wonderful people and projects.
| | |
|----------------------|:-------------------------------------------------|

16
faq.md
View File

@ -14,13 +14,13 @@ pagetitle: FAQ
**Check the info [here](index.html#Download__How_to_use_it).
- **How to activate Windows permanently?**\
Use HWID option in MAS.
Use the HWID option in MAS.
- **How to download and install Office?**\
Check the info [here](genuine-installation-media.html).
- **How to activate Office permanently?**\
Use Ohook option in MAS.
Use the Ohook option in MAS.
- **It says activation failed, what to do now?**\
Check [here](troubleshoot.html).
@ -32,13 +32,13 @@ pagetitle: FAQ
Run HWID activation to activate Pro. Each edition requires separate activation.
- **How to remove HWID activation?**\
You can not remove it, same as you can not remove official Windows digital (HWID) license. Once a 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.
You cannot remove it, just like you cannot remove an official Windows digital (HWID) license. Once a 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.
- **How to remove Ohook, KMS38, Online KMS activation?**\
[Ohook](ohook.html#How_to_remove_Ohook), [KMS38](kms38.html#How_to_remove_KMS38), [Online KMS](online_kms.html#How_to_remove_Online_KMS).
- **Is MAS safe? How to know if there is any malware?**\
MAS is fully [open source](index.html#MAS_Latest_Release). You can open the batch files with notepad and verify it. It has many users/stars on Github. You can even perform the activation manually, check Doc section for instructions.
- **Is MAS safe? How can I know if there is any malware?**\
MAS is fully [open source](index.html#MAS_Latest_Release). You can open the batch files with notepad and verify it. It has many users/stars on Github. You can even perform the activation manually, check the Docs section for instructions.
- **Can I link my Microsoft account safely with MAS activation methods?**\
Yes.
@ -53,15 +53,15 @@ pagetitle: FAQ
Use the change edition option in the Extras section in MAS.
- **Can I activate Office 365?**\
Yes, use Ohook activation option. However, you can't get server-side O365 specific features such as 1TB storage in Onedrive, though almost all other features and 5GB storage in free onedrive account would work fine.
Yes, use the Ohook activation option. However, you can't get server-side O365 specific features such as 1TB storage in OneDrive, though almost all other features and 5GB storage in free OneDrive account would work fine.
- **I'm getting 'Office is not genuine banner'.**\
- **I'm getting an 'Office is not genuine' banner.**\
Run Ohook activation from the latest MAS version.
- **Can I delete the MAS folder after activation?**\
Yes.
- **How MAS is able to activate?**\
- **How is MAS able to activate?**\
Read activation details in the Docs section.
- **Does MAS work for Windows 7/8.1?**\

24
fix-wpa-registry.md
View File

@ -6,11 +6,11 @@ pagetitle: Fix WPA Registry
------------------------------------------------------------------------
- In some cases, system may have corrupt WPA registry keys `HKEY_LOCAL_MACHINE\SYSTEM\WPA` which can cause `sppsvc` to not work and activation will fail.
- In some cases, the system may have corrupt WPA registry keys at `HKEY_LOCAL_MACHINE\SYSTEM\WPA` which can cause `sppsvc` to not work and activation to fail.
- The activation scripts in MAS can detect this issue and will inform you accordingly when to run this option. We suggest to run this only when script asks you to do it. If you are not sure if you need to do it, you can take the help from [here](troubleshoot.html).
- The activation scripts in MAS can detect this issue and will inform you accordingly when to run this option. We suggest running this only when the script asks you to do so. If you are not sure whether you need to do it, you can get help from [here](troubleshoot.html).
- This registry key is protected by the Kernal and can not be deleted normally. That is why we need to follow some more below steps to clear it.
- This registry key is protected by the Kernel and cannot be deleted normally. That is why we need to follow some more steps below to clear it.
------------------------------------------------------------------------
@ -18,27 +18,27 @@ pagetitle: Fix WPA Registry
- Download <https://github.com/asdcorp/rearm/archive/refs/heads/principalis.zip>
- Extract this zip file
- Extract this zip file.
- Copy `rearm.cmd` file to the root of the C drive like `C:\rearm.cmd`
- Copy `rearm.cmd` file to the root of the C drive, like `C:\rearm.cmd`.
- Open command prompt as admin and enter the below command\
- Open the command prompt as administrator and enter the below command\
`Shutdown /f /r /o /t 0`
- After system restart, you will find Troubleshoot \> Advanced Option, select Command Prompt option
- After the system restarts, select Troubleshoot \> Advanced Options \> Command Prompt.
- Now enter the below command\
- Enter the following command\
`C:\rearm.cmd`
- If it says the command is not recognized then enter\
- If it says the command is not recognized, enter\
`bcdedit | find "osdevice"`
- It will show you the OS drive letter, use that drive letter in the command, for example -\
- It will show you the OS drive letter. Use that drive letter in the command, for example -\
`E:\rearm.cmd`
- Wait for it to finish. When it's finished, you will be able to type in the command prompt, if not then wait.
- Wait for it to finish. When it's finished, you will be able to type in the command prompt, If not then wait.
- Once done, exit and then normally boot into windows.
- Once done, exit and then normally boot into Windows.
- Let [us know](contactus.html) if it doesn't help.

10
genuine-installation-media.md
View File

@ -4,7 +4,7 @@ pagetitle: Genuine Installation Media
## Genuine Installation Media
All download links leads to genuine files only.
All download links lead to genuine files only.
| **Windows** | |
|:-----------------------------|:---------------------------------|
@ -24,17 +24,17 @@ All download links leads to genuine files only.
| Office C2R Custom Install (Retail / VL) | [Link](office_c2r_custom.html) (More steps, allows customization) |
| Office MSI VL (Old versions) | [Link](office_msi_links.html) |
You can contact [here](https://discord.gg/gjJEfq7ux8) if you need any other Windows / Office files.
You can contact us [here](https://discord.gg/gjJEfq7ux8) if you need any other Windows / Office files.
------------------------------------------------------------------------
## Verify Authenticity Of Files
- We can use [file hashing method](https://en.wikipedia.org/wiki/File_verification) to verify if a file is genuine or not but we must first know the actual checksum of the file.
- We can use the [file hashing method](https://en.wikipedia.org/wiki/File_verification) to verify if a file is genuine or not, but we must first know the actual checksum of the file.
- Microsoft publish a checksum list for [Windows 11](https://www.microsoft.com/software-download/windows11) consumer edition. Checksum list for other products is not public and it's available to paid subscribers of [MVS](https://visualstudio.microsoft.com/subscriptions/).
- Microsoft publishes a checksum list for [Windows 11](https://www.microsoft.com/software-download/windows11) consumer edition. The checksum list for other products is not public and is available to paid subscribers of [MVS](https://visualstudio.microsoft.com/subscriptions/).
- There are many places where we can find the checksums for Microsoft files and compare them with our files with tools like [7-Zip](https://7-zip.org/) (After installing 7-Zip, right click on ISO file and goto 7-Zip \> CRC SHA). Below is a list of sites containing checksums.
- There are many places where we can find the checksums for Microsoft files and compare them with our files using tools like [7-Zip](https://7-zip.org/) (After installing 7-Zip, right click on the ISO file and go to 7-Zip \> CRC SHA). Below is a list of sites containing checksums.
1. [files.rg-adguard](https://files.rg-adguard.net/) (most complete collection)
2. [MVS dump](https://awuctl.github.io/mvs/)

64
hwid.md
View File

@ -20,11 +20,11 @@ pagetitle: HWID Activation
- This activation is a permanent activation for your system Hardware.
- On a system, this activation can be created for all the supported editions, and all can be linked to Microsoft account without any issues.
- On a system, this activation can be created for all the supported editions, and all can be linked to a Microsoft account without any issues.
- Once a 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.
- Any significant changes in 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.
- Any significant changes in 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.
@ -46,9 +46,9 @@ pagetitle: HWID Activation
- In the official upgrade process from Windows 7 to Windows 10, Microsoft provided an HWID (digital license) activation for Windows 10 without any cost.
- In the background, the upgrade process runs a file named gatherosstate.exe (available in Windows 10/11 ISO) and it checks the license of current Windows if found activated, it generates a valid GenuineTicket.xml **ticket** which is sent to Microsoft and in return, MS authorizes a license.
- In the background, the upgrade process runs a file named gatherosstate.exe (available in Windows 10/11 ISO) and it checks the license of current Windows. If found activated, it generates a valid GenuineTicket.xml **ticket** which is sent to Microsoft and in return, MS authorizes a license.
- So if we just convince the gatherosstate.exe file that the conditions are met for ticket generation by fooling it, it will generate a valid ticket, which can be used to get the valid HWID (Digital license).
- So, if we can convince the gatherosstate.exe file that the conditions are met for ticket generation by fooling it, it will generate a valid ticket, which can be used to get the valid HWID (Digital license).
- How to convince the gatherosstate.exe?\
There are two methods for it.\
@ -58,13 +58,13 @@ pagetitle: HWID Activation
\
**2-** [Modify](https://github.com/asdcorp/GamersOsState) the gatherosstate.exe file itself so that it doesn\'t check the system\'s activation status and can directly create a valid ticket.
- You can find working of this old method here [MAS-Legacy-Methods](https://github.com/massgravel/MAS-Legacy-Methods).
- You can find the workings of this old method here: [MAS-Legacy-Methods](https://github.com/massgravel/MAS-Legacy-Methods).
- Microsoft [made](https://devicepartner.microsoft.com/en-us/communications/comm-windows-ends-installation-path-for-free-windows-7-8-upgrade) server side changes to to block the free upgrade and with that server side change, this method stopped working. To be clear, only new activation requests coming from new hardware was blocked, already established HWID are fine.
- Microsoft [made](https://devicepartner.microsoft.com/en-us/communications/comm-windows-ends-installation-path-for-free-windows-7-8-upgrade) server-side changes to to block the free upgrade, and with that server-side change, this method stopped working. To be clear, only new activation requests coming from new hardware were blocked, already established HWIDs are fine.
#### HWID 2 (Currently working) (03 Oct 2023 - Current)
- When Microsoft stopped the free upgrade, it started requiring Genuine valid key in ticket to authorize a digital license. In the new method we used only the Installation ID of a genuine, valid key. This gets accepted by the server and allows us to get a digital license for free. Check manual activation process in below section to know how to make working universal tickets.
- When Microsoft stopped the free upgrade, it started requiring a genuine valid key in the ticket to authorize a digital license. In the new method, we use only the Installation ID of a genuine, valid key. This gets accepted by the server and allows us to get a digital license for free. Check the manual activation process in below section to know how to make working universal tickets.
------------------------------------------------------------------------
@ -123,7 +123,7 @@ Now a question, can Microsoft block the new requests or revoke already establish
## How to remove HWID?
- You can not remove it, same as you can not remove official Windows digital (HWID) license. Once a 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.
- You cannot remove it, just like you cannot remove an official Windows digital (HWID) license. Once a 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.
------------------------------------------------------------------------
@ -135,23 +135,23 @@ Now a question, can Microsoft block the new requests or revoke already establish
## Manual Activation
This is for those who wants to perform manual activation. If you want a tool to do this for you then check [here](index.html).
This is for those who wants to perform manual activation. If you want a tool to do this for you, then check [here](index.html).
We can divide the manual activation process into two parts.
We can perform the manual activation process in 2 ways.
### 1- From Ready-Made Ticket
- Make sure the Internet is enabled.
- Make sure the internet is enabled.
- Open Windows Powershell as administrator, and enter the following listed commands in the sequence in which they are given.
- Open Windows PowerShell as administrator, and enter the following commands in the sequence in which they are given.
- Enter the Key, (Replace `<key>` with the key from the above list) with the following command
- Enter the Key (Replace `<key>` with the key from the above list) with the following command:
`slmgr /ipk <key>`
- Download Universal tickets from [here](https://pixeldrain.com/u/GbVLtMn6) and extract the downloaded file.
- Now enter below code in Powershell
- Now enter below code in PowerShell:
`(Get-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Control\ProductOptions).OSProductPfn`
@ -159,19 +159,19 @@ We can divide the manual activation process into two parts.
- You need to find the exact same name ticket file in the folder which you have extracted earlier.
- Copy that ticket file and paste it in the below folder
- Copy that ticket file and paste it in the following folder:
`C:\ProgramData\Microsoft\Windows\ClipSVC\GenuineTicket`
- Now run below command in Powershell to apply the ticket
- Now run below command in PowerShell to apply the ticket:
`clipup -v -o`
- Activate Windows with the following command
- Activate Windows with the following command:
`slmgr /ato`
- Check Activation Status with the following command
- Check Activation Status with the following command:
`slmgr /xpr`
@ -181,20 +181,20 @@ We can divide the manual activation process into two parts.
### 2- From Scratch
In this process we will perform activation from scratch. This is based on Universal ticket method. Here we will create identical tickets which are used in MAS HWID script and activate the system with it.
In this process, we will perform activation from scratch. This is based on the Universal ticket method. Here, we will create identical tickets that are used in the MAS HWID script and activate the system with them.
- Download file from the below official MS link and extract this .cab file.\
- Download the file from the official MS link and extract the .cab file.\
<https://download.microsoft.com/download/9/A/E/9AE69DD5-BA93-44E0-864E-180F5E700AB4/adk/Installers/14f4df8a2a7fc82a4f415cf6a341415d.cab>
- Find the file named `filf8377e82b29deadca67bc4858ed3fba9` and rename it as `gatherosstate.exe`
- Find the file named `filf8377e82b29deadca67bc4858ed3fba9` and rename it to `gatherosstate.exe`
- Make a folder named `Files` in C drive, `C:\Files` and copy the `gatherosstate.exe` file in that folder.
- Make a folder named `Files` in the C drive, `C:\Files` and copy the `gatherosstate.exe` file into that folder.
- Make sure the Internet is enabled.
- Make sure that the internet is enabled.
- Open Windows Powershell as administrator, and enter the following listed commands in the sequence in which they are given.
- Open Windows PowerShell as administrator and enter the following commands in the sequence in which they are given.
- Enter the Key, (Replace `<key>` with the key from the above list) with the following command
- Enter the key (Replace `<key>` with the key from the above list) with the following command:
`slmgr /ipk <key>`
@ -273,8 +273,8 @@ $bytes[34377] = 0x63
[System.IO.File]::WriteAllBytes("C:\Files\gatherosstatemodified.exe", $bytes)
```
- Now right click on the file `gatherosstatemodified.exe` and goto properties and set the compatibility to Windows XP SP3.\
- Now we need to generate the ticket, to do that, enter the below command.
- Now right click on the file `gatherosstatemodified.exe`, go to properties and set the compatibility mode to Windows XP SP3.\
- Now we need to generate the ticket, to do that, enter the below command:
<!-- -->
@ -284,15 +284,15 @@ $value = (Get-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Control\ProductOptions
C:\Files\gatherosstatemodified.exe /c Pfn=$value`;PKeyIID=465145217131314304264339481117862266242033457260311819664735280
```
- A GenuineTicket.xml file should be created in the folder `C:\Files\` now let's apply it.
- A GenuineTicket.xml file should be created in the folder `C:\Files\`. Now, let's apply it.
`clipup -v -o -altto C:\Files\`
- Activate Windows with the following command
- Activate Windows with the following command:
`slmgr /ato`
- Check Activation Status with the following command
- Check Activation Status with the following command:
`slmgr /xpr`
@ -300,9 +300,9 @@ C:\Files\gatherosstatemodified.exe /c Pfn=$value`;PKeyIID=4651452171313143042643
**Notes:**
- If the system is already activated then created ticket will be a Lockbox ticket and if not then it will be a Downlevel ticket.
- If the system is already activated then, then the created ticket will be a Lockbox ticket. If not, it will be a Downlevel ticket.
- To make the exact ticket used in MAS HWID script, make sure system is already activated and fix the time with below Powershell command and then initiate the ticket generation process as per above mentioned steps.\
- To make the exact ticket used in MAS HWID script, make sure system is already activated and fix the time with the below PowerShell command and then initiate the ticket generation process as per the steps mentioned above.\
`Set-TimeZone -Id "UTC"; $date=[datetime]"2022/10/11 12:00";while($true){set-date $date; start-sleep -milliseconds 10}`
------------------------------------------------------------------------

14
index.md
View File

@ -15,13 +15,13 @@ A Windows and Office activator using HWID / Ohook / KMS38 / Online KMS activatio
- **HWID (Digital License)** Method to Permanently Activate Windows
- **Ohook** Method to Permanently Activate Office
- **KMS38** Method to Activate Windows/Server Till the Year 2038
- **Online KMS** Method to Activate Windows/Server/Office Till 180 Days (Lifetime With Renewal Task)
- Advanced Activation Troubleshoot
- **Online KMS** Method to Activate Windows/Server/Office For 180 Days (Lifetime With Renewal Task)
- Advanced Activation Troubleshooting
- \$OEM\$ Folders For Preactivation
- Change Windows Edition
- Check Windows/Office Activation Status
- Available in All In One and Separate Files Version
- Fully Open Source and Based on Batch Script
- Available in All In One and Separate Files Versions
- Fully Open Source and Based on Batch Scripts
- Fewer Antivirus Detections
------------------------------------------------------------------------
@ -42,9 +42,9 @@ Last Release - v2.4 (21-Oct-2023)\
(Recommended)
- On Windows 8.1/10/11, right-click on the Windows start menu and select PowerShell or Terminal (Not CMD).
- Copy-paste the below code and press enter\
- Copy and paste the code below and press enter\
`irm https://massgrave.dev/get | iex`
- You will see the activation options, and follow onscreen instructions.
- You will see the activation options. Follow the on-screen instructions.
- That's all.
### Method 2 - Traditional
@ -53,7 +53,7 @@ Last Release - v2.4 (21-Oct-2023)\
- Right click on the downloaded zip file and extract
- In the extracted folder, find the folder named `All-In-One-Version`
- Run the file named `MAS_AIO.cmd`
- You will see the activation options, and follow onscreen instructions.
- You will see the activation options. Follow the on-screen instructions.
- That's all.
To run the scripts in unattended mode, check [here](command_line_switches.html)

76
kms38.md
View File

@ -10,13 +10,13 @@ pagetitle: KMS38 Activation
- How to use it? Please find the instructions [here](index.html#Download__How_to_use_it).
- This activation method activates Windows 10/11 and Windows Server (14393 and later builds), until 19 January 2038 03:14:07 UTC.
- This activation method activates Windows 10/11 and Windows Server (14393 and later builds), until January 19, 2038, 03:14:07 UTC.
- This activation method does not store any files on the system.
- This activation method works offline.
- Unlike HWID and Online KMS activation option, KMS38 does not match with any official activation method.
- Unlike HWID and Online KMS activation options, KMS38 does not match with any official activation method.
------------------------------------------------------------------------
@ -24,25 +24,25 @@ pagetitle: KMS38 Activation
- In a genuine [KMS](https://docs.microsoft.com/en-us/previous-versions/tn-archive/ee939272(v=technet.10)?redirectedfrom=MSDN#kms-overview) activation environment, activation lasts a maximum of up to 180 days. This is done using a valid license and server setup.
- In the Windows major upgrade process, the system uses `gatherosstate.exe` to carry over the remaining KMS activation period. It does it by creating a ticket that can be used offline.
- 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 19 January 2038 03:14:07 UTC.
- 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 it's limited to the year 2038?\
- 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.
- How to convince the gatherosstate.exe?\
- 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 upto 19 January 2038 03:14:07 UTC.\
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 ISO file and not available in C drive system files. 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.
@ -127,9 +127,9 @@ pagetitle: KMS38 Activation
## How to remove KMS38?
- In MAS, goto KMS38 Activation and apply Remove KM38 Protection option.
- In MAS, go to KMS38 Activation and apply the Remove KM38 Protection option.
- After that, In MAS, goto Troubleshoot and apply Fix Licensing option.
- After that, In MAS, go to Troubleshoot and apply the Fix Licensing option.
- Done.
@ -137,18 +137,18 @@ pagetitle: KMS38 Activation
## KMS38 - Server Cor/Acor
- Windows Server Cor/Acor (No GUI) editions don't have `clipup.exe` file.
- Windows Server Cor/Acor (No GUI) editions don't have the `clipup.exe` file.
- To KMS38 activate it, you need to download `ClipUp.exe` file from [this link](https://www.box.com/index.php?rm=box_download_shared_file&shared_name=qrmkewit9ty6ah0qzk0vncyyrwo8hei9&file_id=f_747809716860).\
- To KMS38 activate it, you need to download the `ClipUp.exe` file from [this link](https://www.box.com/index.php?rm=box_download_shared_file&shared_name=qrmkewit9ty6ah0qzk0vncyyrwo8hei9&file_id=f_747809716860).\
\
`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](https://download.microsoft.com/download/1/6/F/16FA20E6-4662-482A-920B-1A45CF5AAE3C/14393.0.160715-1616.RS1_RELEASE_SERVER_EVAL_X64FRE_EN-US.ISO).
This file has digital signatures that can be verified. You can also get this file from the official [Windows Server 2016 x64 RTM ISO](https://download.microsoft.com/download/1/6/F/16FA20E6-4662-482A-920B-1A45CF5AAE3C/14393.0.160715-1616.RS1_RELEASE_SERVER_EVAL_X64FRE_EN-US.ISO).
- Put the `ClipUp.exe` beside the KMS38 Activation script. That would be either `MAS_AIO.cmd` or `KMS38_Activation.cmd`
- Put the `ClipUp.exe` file 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.
- The activation script will check for `ClipUp.exe` in the current folder (from where the script is running) and will use it accordingly.
------------------------------------------------------------------------
@ -156,13 +156,13 @@ pagetitle: KMS38 Activation
- KMS38 Activation is vulnerable to unintended replacement by a 180-Day KMS Activator.
- From MAS 1.7, script will enable the KMS38 protection by default.
- From MAS 1.7, the script will enable KMS38 protection by default.
- If you are going to use [KMS_VL_ALL]((https://github.com/abbodi1406/KMS_VL_ALL_AIO)) by abbodi1406 or [MAS](index.html) (Online KMS option) for **Office activation**, then you can choose to remove this protection.
- Below is the explanation for how the script protect KMS38.
- In the KMS activation method, Windows first checks the KMS IP registered as a specific KMS, and if that is not defined then it checks the Global KMS IP. Another fact is that if Localhost (IP range 127.0.0.0/8) is defined as KMS IP in Windows 8 and later OS then Windows will not accept it as a valid KMS IP. This script simply utilizes the above facts to protect the KMS38 activation from being overwritten by any alternative 'normal' 180-Day KMS Activation and at the same time that KMS activator can be used for Office activation.
- In the KMS activation method, Windows first checks the KMS IP registered as a specific KMS, and if that is not defined, then it checks the Global KMS IP. Another fact is that if Localhost (IP range 127.0.0.0/8) is defined as the KMS IP in Windows 8 and later OS, then Windows will not accept it as a valid KMS IP. This script simply utilizes the above facts to protect the KMS38 activation from being overwritten by any alternative 'normal' 180-Day KMS Activation, and at the same time, that KMS activator can be used for Office activation.
- Script steps-
@ -184,31 +184,31 @@ pagetitle: KMS38 Activation
## Manual Activation
This is for those who wants to perform manual activation. If you want a tool to do this for you then check [here](index.html).
This is for those who want to perform manual activation. If you want a tool to do this for you, then check [here](index.html).
We can divide the manual activation process into two parts.
We can perform the manual activation process in 2 ways.
### 1- From Ready-Made Ticket
- Open Windows Powershell as administrator, and enter the following listed commands in the sequence in which they are given.
- Open Windows PowerShell as administrator, and enter the following commands in the sequence in which they are given.
- Enter the Key, (Replace `<key>` with the key from the above list) with the following command
- Enter the key (Replace `<key>` with the key from the above list) with the following command:
`slmgr /ipk <key>`
- Download Universal ticket from [here](https://www.box.com/index.php?rm=box_download_shared_file&shared_name=p9zvmu4tnogv4nkn01kpyvkndfzhhiv4&file_id=f_1171245497490) and extract the downloaded file.
- Download the Universal ticket from [here](https://www.box.com/index.php?rm=box_download_shared_file&shared_name=p9zvmu4tnogv4nkn01kpyvkndfzhhiv4&file_id=f_1171245497490) and extract the downloaded file.
- Find a file named `KMS.xml` in the extracted folder.
- Copy that ticket file and paste it in the below folder
- Copy that ticket file and paste it in the following folder:
`C:\ProgramData\Microsoft\Windows\ClipSVC\GenuineTicket`
- Now run below command in Powershell to apply the ticket
- Now run the below command in PowerShell to apply the ticket:
`clipup -v -o`
- Check Activation Status with the following command
- Check the Activation Status with the following command:
`slmgr /xpr`
@ -218,18 +218,18 @@ We can divide the manual activation process into two parts.
### 2- From Scratch
In this process we will perform activation from scratch. This is based on Universal ticket method. Here we will create identical ticket which is used in MAS KMS38 script and activate the system with it.
In this process, we will perform activation from scratch. This is based on the Universal ticket method. Here, we will create identical tickets that are used in the MAS HWID script and activate the system with them.
- Download file from the below official MS link and extract this .cab file.\
- Download the file from the official MS link and extract this .cab file.\
<https://download.microsoft.com/download/9/A/E/9AE69DD5-BA93-44E0-864E-180F5E700AB4/adk/Installers/14f4df8a2a7fc82a4f415cf6a341415d.cab>
- Find the file named `filf8377e82b29deadca67bc4858ed3fba9` and rename it as `gatherosstate.exe`
- Make a folder named `Files` in C drive, `C:\Files` and copy the `gatherosstate.exe` file in that folder.
- Open Windows Powershell as administrator, and enter the following listed commands in the sequence in which they are given.
- Open Windows PowerShell as administrator and enter the following commands in the sequence in which they are given.
- Enter the Key, (Replace `<key>` with the key from the above list) with the following command
- Enter the key (Replace `<key>` with the key from the above list) with the following command:
`slmgr /ipk <key>`
@ -309,8 +309,8 @@ $bytes[34377] = 0x63
[System.IO.File]::WriteAllBytes("C:\Files\gatherosstatemodified.exe", $bytes)
```
- Now right click on the file `gatherosstatemodified.exe` and goto properties and set the compatibility to Windows XP SP3.\
- Now we need to generate the ticket, to do that, enter the below command.
- Now right click on the file `gatherosstatemodified.exe`, go to properties and set the compatibility mode to Windows XP SP3.\
- Now we need to generate the ticket, to do that, enter the below command:
<!-- -->
@ -318,7 +318,7 @@ $bytes[34377] = 0x63
C:\Files\gatherosstatemodified.exe /c GVLKExp=2038-01-19T03:14:07Z`;DownlevelGenuineState=1
```
- A GenuineTicket.xml file should be created in the folder `C:\Files\` now let's apply it.
- A GenuineTicket.xml file should be created in the folder `C:\Files\`. Now, let's apply it:
`clipup -v -o -altto C:\Files\`
@ -330,18 +330,18 @@ C:\Files\gatherosstatemodified.exe /c GVLKExp=2038-01-19T03:14:07Z`;DownlevelGen
**Notes:**
- To make the exact ticket used in MAS KMS38 script, fix the time with below Powershell command and then initiate the ticket generation process as per above mentioned steps.\
- To make the exact ticket used in MAS KMS38 script, fix the time with the below PowerShell command and then initiate the ticket generation process as per the steps mentioned above.\
`Set-TimeZone -Id "UTC"; $date=[datetime]"2022/10/11 12:00";while($true){set-date $date; start-sleep -milliseconds 10}`
- In the case of Windows Server Cor/Acor (No GUI) editions, the system doesn't have `clipup.exe` file.\
To KMS38 activate it, you need to download `ClipUp.exe` file from [this link](https://www.box.com/index.php?rm=box_download_shared_file&shared_name=qrmkewit9ty6ah0qzk0vncyyrwo8hei9&file_id=f_747809716860).\
- In the case of Windows Server Cor/Acor (No GUI) editions, the system doesn't have the `clipup.exe` file.\
To KMS38 activate it, you need to download the missing `ClipUp.exe` file from [this link](https://www.box.com/index.php?rm=box_download_shared_file&shared_name=qrmkewit9ty6ah0qzk0vncyyrwo8hei9&file_id=f_747809716860).\
\
`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](https://download.microsoft.com/download/1/6/F/16FA20E6-4662-482A-920B-1A45CF5AAE3C/14393.0.160715-1616.RS1_RELEASE_SERVER_EVAL_X64FRE_EN-US.ISO).\
This file has digital signatures that can be verified. You can also get this file from the official [Windows Server 2016 x64 RTM ISO](https://download.microsoft.com/download/1/6/F/16FA20E6-4662-482A-920B-1A45CF5AAE3C/14393.0.160715-1616.RS1_RELEASE_SERVER_EVAL_X64FRE_EN-US.ISO).\
\
Put the `ClipUp.exe` in `C:\Windows\System32` folder and then initiate the above mentioned activation process. Once the activation is done, you can remove the file.
Put the `ClipUp.exe` in the `C:\Windows\System32` folder and then initiate the above-mentioned activation process. Once the activation is complete, you can remove the file.
------------------------------------------------------------------------

36
licensing-servers-issue.md
View File

@ -6,28 +6,28 @@ pagetitle: Licensing Servers Issue
------------------------------------------------------------------------
- In some cases, **HWID activation** may fail because system couldn't connect to HWID licensing servers.
- In some cases, **HWID activation** may fail because the system couldn't connect to HWID licensing servers.
- Activation script will inform you about this if that is the case. We suggest to follow the below guide only when the script tells you to do it. If you are unsure, you can take the help from [here](troubleshoot.html).
- The activation script will inform you about this if that is the case. We suggest to following the below guide only when the script tells you to do so. If you are unsure, you can get help from [here](troubleshoot.html).
- This may happen mostly either due to DNS or Issues in MS licensing servers itself or Firewall rules in the system. Below you can find fixes for it.
- This may happen mostly due to DNS issues, issues in MS licensing servers themselves or firewall rules in the system. Below you can find fixes for it.
- **Which method to choose for the fix?\
- **Which method should you choose for the fix?\
\
**If you are located in China then choose **Modify Host File** option.\
If you are not in China then first try **Network Reset** option and if that doesn't work then **Fix DNS** option, and if that doesn't work then try **VPN** method or try another Internet connection.
**If you are located in China, then choose the **Modify Host File** option.\
If you are not in China, then first try the **Network Reset** option. If that doesn't work, try the **Fix DNS** option. If that doesn't work, then try the **VPN** method or try another internet connection.
- If you are still facing issues then check [here](troubleshoot.html).
- If you are still facing issues, check [here](troubleshoot.html).
------------------------------------------------------------------------
## Network Reset
- In Windows 10/11, goto settings and search for Network Reset and apply this option.
- In Windows 10/11, go to settings and search for Network Reset, then apply this option.
- Restart your system and try HWID Activation.
- If it's showing same Internet error then apply the Fix DNS option.
- If it's showing the same Internet error then apply the Fix DNS option.
------------------------------------------------------------------------
@ -35,13 +35,13 @@ pagetitle: Licensing Servers Issue
- Download the `Fix_DNS.zip` file from [here](https://www.box.com/index.php?rm=box_download_shared_file&shared_name=4c66hw8ezuijy5j0trwczy860sf825i7&file_id=f_1146300205040).
- Extract the zip file and right click on `Fix_DNS.cmd` file and run it as admin.
- Extract the zip file and right-click on `Fix_DNS.cmd` file and run it as administrator.
- Follow onscreen instructions.
- Follow the on-screen instructions.
- Once done, try HWID Activation.
- If it's showing same Internet error then try VPN option.
- If it shows the same internet error, try the VPN option.
------------------------------------------------------------------------
@ -50,19 +50,19 @@ pagetitle: Licensing Servers Issue
- Install Freedome VPN\
<https://download.sp.f-secure.com/freedome/installer/2/Freedome.exe>
- Once done connect to USA servers and then try HWID Activation.
- Once done, connect to USA servers and then try HWID Activation.
- If it's showing same Internet error then check [here](troubleshoot.html).
- If it's showing the same internet error, check [here](troubleshoot.html).
------------------------------------------------------------------------
## Modify Host File
Around 8 Feb 2023 in China, MS licensing servers failed to properly connect and it disrupted many Windows services including activation. Solution to this issue is to simply hardcode another country's MS licensing servers IP in hosts file and Windows will use that for activation. This method can also be used if for any reason DNS is failing to resolve MS licensing servers.
Around February 8, 2023, in China, MS licensing servers failed to properly connect, disrupting many Windows services, including activation. The solution to this issue is to simply hardcode another country's MS licensing servers IP in hosts file, and Windows will use that for activation. This method can also be used if, for any reason, DNS is failing to resolve MS licensing servers.
- Open Powershell or Terminal as admin (don't open CMD).
- Open PowerShell or Terminal as admin (don't open CMD).
- Copy paste below lines and press enter,
- Copy and paste the lines below and press enter:
<!-- -->
@ -76,7 +76,7 @@ Add-Content -Path $filePath -Value "124.108.22.138 licensing.mp.microsoft.com"
- Done. Now try HWID Activation.
To restore it, run below commands.
To restore it, run the commands below.
```
$filePath = "C:\Windows\System32\drivers\etc\hosts"

22
oem-folder.md
View File

@ -10,23 +10,23 @@ pagetitle: OEM Folders
## Overview
- To create a pre-activated Windows installation .iso, do the following things:
- To create a pre-activated Windows installation .iso, do the following:
- Extract `$OEM$` folder to the desktop using the MAS script.
- 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 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.
- 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](index.html) about activation method details and select the activation method as per your requirement.
- You can check [here](index.html) 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 below steps.
- 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.
- Extract the ISO file with an archive software like 7-zip or Winrar.
@ -34,7 +34,7 @@ pagetitle: OEM Folders
- Run [MakeISO.reg](https://forums.mydigitallife.net/posts/1733596) by Aveyo. [Mirror](https://pixeldrain.com/u/sKEdjFJA).
- Right click on extracted ISO folder and select `MakeISO` option.
- Right-click on the extracted ISO folder and select `MakeISO` option.
- That's it.
@ -43,22 +43,22 @@ pagetitle: OEM Folders
## 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 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 HWID method in preactivation will use Iot LTSC key to change the edition.
- 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 `clipup.exe` file.
- Windows Server Cor/Acor (No GUI) editions don't have the `clipup.exe` file.
- To KMS38 activate it, you need to download `ClipUp.exe` file from [this link](https://www.box.com/index.php?rm=box_download_shared_file&shared_name=qrmkewit9ty6ah0qzk0vncyyrwo8hei9&file_id=f_747809716860).\
- To KMS38 activate it, you need to download the missing `ClipUp.exe` file from [this link](https://www.box.com/index.php?rm=box_download_shared_file&shared_name=qrmkewit9ty6ah0qzk0vncyyrwo8hei9&file_id=f_747809716860).\
\
`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](https://download.microsoft.com/download/1/6/F/16FA20E6-4662-482A-920B-1A45CF5AAE3C/14393.0.160715-1616.RS1_RELEASE_SERVER_EVAL_X64FRE_EN-US.ISO).
This file has digital signatures that can be verified. You can also get this file from the official [Windows Server 2016 x64 RTM ISO](https://download.microsoft.com/download/1/6/F/16FA20E6-4662-482A-920B-1A45CF5AAE3C/14393.0.160715-1616.RS1_RELEASE_SERVER_EVAL_X64FRE_EN-US.ISO).
- Put the `ClipUp.exe` beside the KMS38 Activation script. That would be either `MAS_AIO.cmd` or `KMS38_Activation.cmd`