From 7d2157fb8d5989d3195083551dc8c5ce4c042714 Mon Sep 17 00:00:00 2001 From: WindowsAddict Date: Fri, 27 Oct 2023 02:06:23 +0530 Subject: Grammar fixes from Lyssa --- _site/kms38.html | 132 ++++++++++++++++++++++++++++--------------------------- 1 file changed, 68 insertions(+), 64 deletions(-) (limited to '_site/kms38.html') diff --git a/_site/kms38.html b/_site/kms38.html index a7a6e6a..e2de61b 100644 --- a/_site/kms38.html +++ b/_site/kms38.html @@ -414,11 +414,11 @@ div.tocify {
How to use it? Please find the instructions here.
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 does not store any files on the system.
This activation method works offline.
Unlike HWID and Online KMS activation option, KMS38 does not +
Unlike HWID and Online KMS activation options, KMS38 does not match with any official activation method.
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
+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.
Why it’s limited to the year 2038?
+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
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 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
+generate a valid ticket allowing activation up to January 19, 2038,
03:14:07 UTC.
2-
Q: Can Microsoft block this kind of @@ -742,10 +743,10 @@ support activation on non-azure systems.
In MAS, goto KMS38 Activation and apply Remove KM38 Protection -option.
After that, In MAS, goto Troubleshoot and apply Fix Licensing -option.
In MAS, go to KMS38 Activation and apply the Remove KM38 +Protection option.
After that, In MAS, go to Troubleshoot and apply the Fix +Licensing option.
Done.
Windows Server Cor/Acor (No GUI) editions don’t have +
Windows Server Cor/Acor (No GUI) editions don’t have the
clipup.exe file.
To KMS38 activate it, you need to download +
To KMS38 activate it, you need to download the
ClipUp.exe file from this
link.
@@ -763,15 +764,15 @@ link.
File: ClipUp.exe
SHA-256: 0d6e9f6bbd0321eda149658d96040cb4f79e0bd93ba60061f25b28fecbf4d4ef
-This file has digital signatures which can be verified. You can also get
-this file from official Windows
Server 2016 x64 RTM ISO.
Put the ClipUp.exe beside the KMS38 Activation
+
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
+
The activation script will check for ClipUp.exe in
+the current folder (from where the script is running) and will use it
accordingly.
KMS38 Activation is vulnerable to unintended replacement by a 180-Day KMS Activator.
From MAS 1.7, script will enable the KMS38 protection by +
From MAS 1.7, the script will enable KMS38 protection by default.
If you are going to use KMS_VL_ALL by @@ -791,13 +792,14 @@ 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 +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.
Script steps-
Set the Windows edition-specific KMS IP to Localhost @@ -818,31 +820,32 @@ that KMS activator can be used for Office activation.
This is for those who wants to perform manual activation. If you want -a tool to do this for you then check here.
-We can divide the manual activation process into two parts.
+This is for those who want to perform manual activation. If you want +a tool to do this for you, then check here.
+We can perform the manual activation process in 2 ways.
Open Windows Powershell as administrator, and enter the following -listed 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
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:
slmgr /ipk <key>
Download Universal ticket from Download the Universal ticket from here
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
slmgr /xpr
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
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.
Enter the Key, (Replace <key> with the key
-from the above list) with the following command
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:
slmgr /ipk <key>
gatherosstatemodified.exe
-and goto properties and set the compatibility to Windows XP SP3.gatherosstatemodified.exe,
+go to properties and set the compatibility mode to Windows XP SP3.C:\Files\gatherosstatemodified.exe /c GVLKExp=2038-01-19T03:14:07Z`;DownlevelGenuineState=1
C:\Files\ now let’s apply it.C:\Files\. Now, let’s apply it:
clipup -v -o -altto C:\Files\
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.
+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 clipup.exe file.
+To KMS38 activate it, you need to download the missing
+ClipUp.exe file from this
link.
File: ClipUp.exe
SHA-256: 0d6e9f6bbd0321eda149658d96040cb4f79e0bd93ba60061f25b28fecbf4d4ef
-This file has digital signatures which can be verified. You can also get
-this file from official Windows
Server 2016 x64 RTM 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.
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.