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.

  • +(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 +

  • Unlike HWID and Online KMS activation options, KMS38 does not match with any official activation method.


  • @@ -432,18 +432,18 @@ 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 +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.

    How to remove KMS38?


    @@ -753,9 +754,9 @@ option.

    KMS38 - Server Cor/Acor


    @@ -781,7 +782,7 @@ accordingly.

    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.

    -

    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.

    1- From Ready-Made Ticket

      -
    • 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

      -
    • Check Activation Status with the following command
    • +
    • Check the Activation Status with the following command:

    slmgr /xpr

      @@ -852,12 +855,13 @@ folder.

    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

    • @@ -867,10 +871,10 @@ class="uri">https://download.microsoft.com/download/9/A/E/9AE69DD5-BA93-44E0-864
    • 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>

      @@ -949,17 +953,17 @@ $bytes[34376] = 0xeb $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 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.
      • +command:
      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.
      • +C:\Files\. Now, let’s apply it:

      clipup -v -o -altto C:\Files\

        @@ -972,27 +976,27 @@ command.

        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.

        • +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.


    -- cgit v1.2.3