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/hwid.html | 56 ++++++++++++++++++++++++++++++++++++-------------------- 1 file changed, 36 insertions(+), 20 deletions(-) (limited to '_site/hwid.html') diff --git a/_site/hwid.html b/_site/hwid.html index e27154b..08b2492 100644 --- a/_site/hwid.html +++ b/_site/hwid.html @@ -11,7 +11,7 @@ -
In the background, the upgrade process runs a file named
-gatherosstate.exe and it checks the license of current
-Windows if found activated, it generates a valid GenuineTicket.xml 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). The script here does exactly that to get the
-activation for free without any upgrade process.
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).
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.
+
+2- Modify
+the gatherosstate.exe file itself so that it doesn’t check the system’s
+activation status and can directly create a valid ticket.
Note: If you want to understand more about how
+these above mentioned both methods then check this repo MAS-Legacy-Methods
+Latest MAS doesn’t use any of these methods, instead it uses ready to
+use Universal tickets (check below for info).
+
There are many methods for ticket generation, however we can classify +
There are many methods for ticket generation, majorly we can classify the ticket types in 3 categories.
Downlevel Ticket - This is the simplest ticket generation process. In this method, ticket is signed by downlevel key by -the system and the ticket’s OSVersion is 10. If it’s generated on +the system and the ticket’s OSVersion is =<10. If it’s generated on Windows 10/11 then MS ideally aren’t supposed to grant activation, however they do and method is continuously working from last 4-5 years. Almost every HWID activator (at the time of writing this) is based on @@ -491,7 +509,7 @@ href="https://github.com/massgravel/MAS-Legacy-Methods">MAS-Legacy-Methods
Now a question, can Microsoft block the new requests or revoke already established HWID license?
Windows Server does not support HWID activation.
ServerRdsh edition does not officially +href="https://learn.microsoft.com/en-us/azure/virtual-desktop/windows-10-multisession-faq">officially support activation on non-azure systems.