From 76691a591ad4c67c4159cb48b55e80b6b9c71a7f Mon Sep 17 00:00:00 2001
From: WindowsAddict
Date: Tue, 3 Oct 2023 16:00:57 +0530
Subject: 2.2

---
 _site/hwid.html | 100 +++++++++++++++++++++-----------------------------------
 1 file changed, 38 insertions(+), 62 deletions(-)

(limited to '_site/hwid.html')

diff --git a/_site/hwid.html b/_site/hwid.html
index f598c79..b734473 100644
--- a/_site/hwid.html
+++ b/_site/hwid.html
@@ -410,14 +410,8 @@ div.tocify {
 <hr />
 <div id="overview" class="section level2">
 <h2>Overview</h2>
-<ul>
-<li><strong>Note: HWID Activation is not working<br />
-</strong>HWID activation is not working because of server-side changes
-at Microsoft. Use the KMS38 option for now. Your previously established
-HWID is safe. This happened because of <a
-href="https://devicepartner.microsoft.com/en-us/communications/comm-windows-ends-installation-path-for-free-windows-7-8-upgrade">recent
-change</a> to not allow Windows 7/8 free upgrades.</li>
-</ul>
+<p><strong>Note: HWID Activation is working again with a new
+method.</strong></p>
 <hr />
 <ul>
 <li><p>How to use it? Please find the instructions <a
@@ -458,11 +452,17 @@ script.</p></li>
 </ul>
 <hr />
 </div>
+<div id="hwid-history" class="section level2">
+<h2>HWID History</h2>
+</div>
 <div id="how-does-it-work" class="section level2">
 <h2>How does it work?</h2>
+<div id="hwid-1-now-defunct-summer-of-2018---sep-26-2023"
+class="section level4">
+<h4>HWID 1 (Now defunct) (Summer of 2018 - Sep 26 2023)</h4>
 <ul>
 <li><p>In the official upgrade process from Windows 7 to Windows 10,
-Microsoft provides an HWID (digital license) activation for Windows 10
+Microsoft provided an HWID (digital license) activation for Windows 10
 without any cost.</p></li>
 <li><p>In the background, the upgrade process runs a file named
 gatherosstate.exe (available in Windows 10/11 ISO) and it checks the
@@ -479,73 +479,49 @@ There are two methods for it.<br />
 <strong>1-</strong> Place a <a
 href="https://github.com/asdcorp/Integrated_Patcher_3">custom
 slc.dll</a> file beside gatherosstate.exe:<br />
-gatherosstate.exe uses the system’s
-<code>C:\Windows\System32\slc.dll</code> file to gather the system’s
+gatherosstate.exe uses the system's
+<code>C:\Windows\System32\slc.dll</code> 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.<br />
 <br />
 <strong>2-</strong> <a
 href="https://github.com/asdcorp/GamersOsState">Modify</a> the
-gatherosstate.exe file itself so that it doesn’t check the system’s
+gatherosstate.exe file itself so that it doesn't check the system's
 activation status and can directly create a valid ticket.</p></li>
-<li><p><strong>Notes:</strong></p>
+<li><p>You can find working of this old method here <a
+href="https://github.com/massgravel/MAS-Legacy-Methods">MAS-Legacy-Methods</a>.</p></li>
+<li><p>Microsoft <a
+href="https://devicepartner.microsoft.com/en-us/communications/comm-windows-ends-installation-path-for-free-windows-7-8-upgrade">made</a>
+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.</p></li>
+</ul>
+</div>
+<div id="hwid-2-currently-working-03-oct-2023---current"
+class="section level4">
+<h4>HWID 2 (Currently working) (03 Oct 2023 - Current)</h4>
 <ul>
-<li>To be clear, we are <strong>not modifying/patching any on-board
-system file</strong> to get digital license. 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.</li>
-<li>If you want to understand more about how these above mentioned both
-methods then check this repo <a
-href="https://github.com/massgravel/MAS-Legacy-Methods">MAS-Legacy-Methods</a></li>
-<li>Latest MAS doesn’t use any of these methods, instead it uses ready
-to use Universal tickets (check below for info).</li>
-</ul></li>
+<li>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.</li>
 </ul>
 <hr />
-</div>
-<div id="types-of-tickets" class="section level2">
-<h2>Types of Tickets</h2>
-<p>There are many methods for ticket generation, majorly we can classify
-the ticket types in 3 categories.</p>
-<ol style="list-style-type: decimal">
-<li><p><strong>Downlevel Ticket</strong> - 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 =&lt;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
-this method.</p></li>
-<li><p><strong>Lockbox Ticket</strong> - This is slightly a trickier
-method. The ticket is signed by Lockbox key by the system and the
-ticket’s OSVersion is 10. This ticket generation process involves
-cleaning Clipsvc licenses and IdentityCRL registry key in the system.
-Due to some hiccups in the process, this method is not primarily used in
-MAS, however these are the types of tickets that are identical to the
-genuine ticket generated by system on activated Windows 10/11.</p></li>
-<li><p><strong>Universal Ticket</strong> - In this method, we set the
-OSVersion =&lt;5 in the ticket and when we apply the ticket, system
-ignores the HWID in the ticket due to lower OSVersion and grant the
-activation anyway. This ticket can be applied on any system. These
-tickets can either be Downlevel or Lockbox type. MS ideally aren’t
-supposed to grant activation, however they do.</p></li>
-</ol>
-<p>Latest version of MAS is using Universal ticket method. Other ticket
-method scripts can be found in this repo <a
-href="https://github.com/massgravel/MAS-Legacy-Methods">MAS-Legacy-Methods</a></p>
 <p>Now a question, can Microsoft block the new requests or revoke
 already established HWID license?</p>
 <ul>
 <li>Revoking the license would be too extreme and will face many
-complications and risk of voiding valid licenses. However maybe they can
-block the new activation requests coming from Downlevel and Universal
-tickets. But the tools are working from 4-5 years and they don’t seem to
-care much for consumer piracy; That’s not where they get the most money
-from.</li>
+complications and risk of voiding valid licenses. However they can block
+the new activation requests for new hardware coming from the methods
+mentioned here.</li>
 </ul>
 <hr />
 </div>
+</div>
 <div id="supported-products" class="section level2">
 <h2>Supported Products</h2>
 <table>
@@ -724,8 +700,8 @@ from the above list) with the following command</p></li>
 <p><code>slmgr /ipk &lt;key&gt;</code></p>
 <ul>
 <li><p>Download Universal tickets from <a
-href="https://www.box.com/index.php?rm=box_download_shared_file&amp;shared_name=p9zvmu4tnogv4nkn01kpyvkndfzhhiv4&amp;file_id=f_1171245497490">here</a>
-and extract the downloaded file.</p></li>
+href="https://pixeldrain.com/u/GbVLtMn6">here</a> and extract the
+downloaded file.</p></li>
 <li><p>Now enter below code in Powershell</p></li>
 </ul>
 <p><code>(Get-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Control\ProductOptions).OSProductPfn</code></p>
@@ -861,7 +837,7 @@ command.</li>
 <!-- -->
 <pre><code>$value = (Get-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Control\ProductOptions).OSProductPfn
 
-C:\Files\gatherosstatemodified.exe /c Pfn=$value`;DownlevelGenuineState=1</code></pre>
+C:\Files\gatherosstatemodified.exe /c Pfn=$value`;PKeyIID=465145217131314304264339481117862266242033457260311819664735280</code></pre>
 <ul>
 <li>A GenuineTicket.xml file should be created in the folder
 <code>C:\Files\</code> now let’s apply it.</li>
-- 
cgit v1.2.3