From 4845932d784c2b1e384b6d0f215ac874d5d70a94 Mon Sep 17 00:00:00 2001 From: DESKTOP-AJSJJMA\Admin Date: Thu, 16 Mar 2023 11:09:16 -0700 Subject: 1.8 --- _site/kms38.html | 82 ++++++++++++++++++++++++++++++++++++-------------------- 1 file changed, 53 insertions(+), 29 deletions(-) (limited to '_site/kms38.html') diff --git a/_site/kms38.html b/_site/kms38.html index e314b86..e784ef7 100644 --- a/_site/kms38.html +++ b/_site/kms38.html @@ -11,7 +11,7 @@ -kms38 +KMS38 Activation @@ -362,10 +362,6 @@ div.tocify { Install HWID Key
  • -
  • - Unreadable Codes In MAS AIO -
    • -
  • Office License Is Not Genuine
    • @@ -423,7 +419,7 @@ match with any official activation method.

    href="https://docs.microsoft.com/en-us/previous-versions/tn-archive/ee939272(v=technet.10)?redirectedfrom=MSDN#kms-overview">KMS activation environment, activation lasts a maximum of up to 180 days. This is done using a valid license and server setup.

    -

  • However, in the Windows major upgrade process, the system uses +

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

    • @@ -436,6 +432,27 @@ href="https://en.wikipedia.org/wiki/Year_2038_problem">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?
    +There are two methods for it.
    +
    +1- Place a custom +slc.dll 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.
    +
    +2- Modify +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.

    • +

  • Note: Latest MAS doesn’t use any of these +methods, instead it uses ready to use Universal ticket (check below for +manual activation).

    • Q: Can Microsoft block this kind of activation?
    @@ -696,8 +713,8 @@ they can’t block them or take action directly.

    activated.

  • KMS38 only supports Windows/server version 14393 (1607) and newer versions.

    • -

  • ServerRdsh edition does not officially +

  • ServerRdsh, Server Azure Datacenter editions do not officially support activation on non-azure systems.

    • @@ -708,13 +725,18 @@ support activation on non-azure systems.

  • Windows Server Cor/Acor (No GUI) editions don’t have clipup.exe file.

  • To KMS38 activate it, you need to download -ClipUp.exe file from the below official MS link.
    -https://msdl.microsoft.com/download/symbols/clipup.exe/5789984414b000/clipup.exe

    • -

  • Rename the downloaded file as ClipUp.exe and put it -beside the KMS38 Activation script. That would be either -MAS_AIO.cmd or KMS38_Activation.cmd

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

    • @@ -885,17 +907,21 @@ with below Powershell command and then initiate the ticket generation process as per above mentioned steps.
    $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. So to activate it, you -need to download ClipUp.exe file from the below official MS -link.
    -https://msdl.microsoft.com/download/symbols/clipup.exe/5789984414b000/clipup.exe
    -    Rename the downloaded file as ClipUp.exe and put it in -C:\Windows\System32 folder and then initiate the above -mentioned activation process. Once the activation is done, you can -remove the file.

    • +system doesn’t have clipup.exe file.
    +To KMS38 activate it, you need to download 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.

    @@ -911,9 +937,7 @@ section if you want pre-activated Windows installation.

    Troubleshooting

    -- cgit v1.2.3