<h2class="anchor anchorWithStickyNavbar_LWe7"id="overview">Overview<ahref="#overview"class="hash-link"aria-label="Direct link to Overview"title="Direct link to Overview"></a></h2>
<ul>
<li>How to use it? Please find the instructions <ahref="/#download--how-to-use-it">here</a>.</li>
<li>This activation method activates Windows 10/11 and Windows Server (14393 and later builds), until January 19, 2038, 03:14:07 UTC.</li>
<li>This activation method does not store any files on the system.</li>
<li>This activation method works offline.</li>
<li>Unlike HWID and Online KMS activation options, KMS38 does not match with any official activation method.</li>
</ul>
<hr>
<h2class="anchor anchorWithStickyNavbar_LWe7"id="how-does-it-work">How does it work?<ahref="#how-does-it-work"class="hash-link"aria-label="Direct link to How does it work?"title="Direct link to How does it work?"></a></h2>
<ul>
<li>In a genuine <ahref="https://docs.microsoft.com/en-us/previous-versions/tn-archive/ee939272(v=technet.10)?redirectedfrom=MSDN#kms-overview"target="_blank"rel="noopener noreferrer">KMS</a> activation environment, activation lasts a maximum of up to 180 days. This is done using a valid license and server setup.</li>
<li>In the Windows major upgrade process, the system uses <code>gatherosstate.exe</code> to carry over the remaining KMS activation period. It does this by creating a ticket that can be used offline.</li>
<li>The trick is that we can fool the <code>gatherosstate.exe</code> about the remaining KMS activation period and manually put the desired period maximum up to January 19, 2038, 03:14:07 UTC.</li>
<li>Why is it limited to the year 2038?<br>
<!---->It's related to the <ahref="https://en.wikipedia.org/wiki/Year_2038_problem"target="_blank"rel="noopener noreferrer">Y2K38 problem</a> as this date (19 January 2038 03:14:07 UTC) is the maximum date we can give to <code>gatherosstate.exe</code> without it looping back to the year 1970.</li>
<li>How can we convince the gatherosstate.exe?<br>
<!---->There are two methods for it.<br>
<strong>1-</strong> Place a <ahref="https://github.com/asdcorp/Integrated_Patcher_3"target="_blank"rel="noopener noreferrer">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 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 up to January 19, 2038, 03:14:07 UTC.<br>
<strong>2-</strong><ahref="https://github.com/asdcorp/GamersOsState"target="_blank"rel="noopener noreferrer">Modify</a> 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.</li>
<li><strong>Notes:</strong>
<ul>
<li>To be clear, we are <strong>not modifying/patching any on-board system file</strong> to get the ticket. Gatherosstate.exe is a part of the ISO file and not available in C drive system files. The system's slc.dll file is not touched; Instead, we use custom slc.dll only for a brief moment of ticket generation.</li>
<li>Latest MAS doesn't use any of these methods; Instead, it uses ready-to-use Universal tickets (check below for manual activation info).</li>
</ul>
</li>
</ul>
<p><strong>Q:</strong> Can Microsoft block this kind of activation?<br>
<strong>A:</strong> Not directly. They could only update Clipup to allow for a maximum activation period of 180 days. Not much besides that can be done on their part. The tickets are not sent to Microsoft at all, so they can't block them or take action directly.</p>
<hr>
<h2class="anchor anchorWithStickyNavbar_LWe7"id="supported-products">Supported Products<ahref="#supported-products"class="hash-link"aria-label="Direct link to Supported Products"title="Direct link to Supported Products"></a></h2>
<h3class="anchor anchorWithStickyNavbar_LWe7"id="windows-10--11">Windows 10 / 11<ahref="#windows-10--11"class="hash-link"aria-label="Direct link to Windows 10 / 11"title="Direct link to Windows 10 / 11"></a></h3>
<h3class="anchor anchorWithStickyNavbar_LWe7"id="windows-server-ltsc">Windows Server (LTSC)<ahref="#windows-server-ltsc"class="hash-link"aria-label="Direct link to Windows Server (LTSC)"title="Direct link to Windows Server (LTSC)"></a></h3>
<table><thead><tr><th>Windows Server (LTSC)</th><th>EditionID</th><th>Generic Volume License Key</th></tr></thead><tbody><tr><td>Windows Server 2025 Standard</td><td>ServerStandard</td><td>DPNXD-67YY9-WWFJJ-RYH99-RM832</td></tr><tr><td>Windows Server 2025 Datacenter</td><td>ServerDatacenter</td><td>CNFDQ-2BW8H-9V4WM-TKCPD-MD2QF</td></tr><tr><td>Windows Server 2025 Azure Core</td><td>ServerAzureCor</td><td>QN7G3-4RM92-MT6QR-PR966-FVYV7</td></tr><tr><td>Windows Server 2025 Azure Datacenter</td><td>ServerTurbine</td><td>NQ8HH-FTDTM-6VGY7-TQ3DV-XFBV2</td></tr><tr><td>Windows Server 2022 Datacenter</td><td>ServerDatacenter</td><td>WX4NM-KYWYW-QJJR4-XV3QB-6VM33</td></tr><tr><td>Windows Server 2022 Standard</td><td>ServerStandard</td><td>VDYBN-27WPP-V4HQT-9VMD4-VMK7H</td></tr><tr><td>Windows Server 2022 Azure Core</td><td>ServerAzureCor</td><td>6N379-GGTMK-23C6M-XVVTC-CKFRQ</td></tr><tr><td>Windows Server 2022 Azure Datacenter</td><td>ServerTurbine</td><td>NTBV8-9K7Q8-V27C6-M2BTV-KHMXV</td></tr><tr><td>Windows Server 2019 Datacenter</td><td>ServerDatacenter</td><td>WMDGN-G9PQG-XVVXX-R3X43-63DFG</td></tr><tr><td>Windows Server 2019 Standard</td><td>ServerStandard</td><td>N69G4-B89J2-4G8F4-WWYCC-J464C</td></tr><tr><td>Windows Server 2019 Essentials</td><td>ServerSolution</td><td>WVDHN-86M7X-466P6-VHXV7-YY726</td></tr><tr><td>Windows Server 2019 Azure Core</td><td>ServerAzureCor</td><td>FDNH6-VW9RW-BXPJ7-4XTYG-239TB</td></tr><tr><td>Windows Server 2019 ARM64</td><td>ServerARM64</td><td>GRFBW-QNDC4-6QBHG-CCK3B-2PR88</td></tr><tr><td>Windows Server 2016 ARM64</td><td>ServerARM64</td><td>K9FYF-G6NCK-73M32-XMVPY-F9DRR</td></tr><tr><td>Windows Server 2016 Datacenter</td><td>ServerDatacenter</td><td>CB7KF-BWN84-R7R2Y-793K2-8XDDG</td></tr><tr><td>Windows Server 2016 Standard</td><td>ServerStandard</td><td>WC2BQ-8NRM3-FDDYY-2BFGV-KHKQY</td></tr><tr><td>Windows Server 2016 Essentials</td><td>ServerSolution</td><td>JCKRF-N37P4-C2D82-9YXRT-4M63B</td></tr><tr><td>Windows Server 2016 Cloud Storage</td><td>ServerCloudStorage</td><td>QN4C6-GBJD2-FB422-GHWJK-GJG2R</td></tr><tr><td>Windows Server 2016 Azure Core</td><td>ServerAzureCor</td><td>VP34G-4NPPG-79JTQ-864T4-R3MQX</td></tr></tbody></table>
<h3class="anchor anchorWithStickyNavbar_LWe7"id="windows-server-annual-channel">Windows Server (Annual Channel)<ahref="#windows-server-annual-channel"class="hash-link"aria-label="Direct link to Windows Server (Annual Channel)"title="Direct link to Windows Server (Annual Channel)"></a></h3>
<table><thead><tr><th>Windows Server (Annual Channel)</th><th>EditionID</th><th>Generic Volume License Key</th></tr></thead><tbody><tr><td>Windows Server Datacenter (23H2)</td><td>ServerDatacenter</td><td>WX4NM-KYWYW-QJJR4-XV3QB-6VM33</td></tr></tbody></table>
<h3class="anchor anchorWithStickyNavbar_LWe7"id="windows-server-semi-annual-channel">Windows Server (Semi-Annual Channel)<ahref="#windows-server-semi-annual-channel"class="hash-link"aria-label="Direct link to Windows Server (Semi-Annual Channel)"title="Direct link to Windows Server (Semi-Annual Channel)"></a></h3>
<table><thead><tr><th>Windows Server (Semi-Annual Channel)</th><th>EditionID</th><th>Generic Volume License Key</th></tr></thead><tbody><tr><td><strong>20H2, 2004, 1909, 1903, and 1809</strong></td><td></td><td></td></tr><tr><td>Windows Server Datacenter</td><td>ServerDatacenterACor</td><td>6NMRW-2C8FM-D24W7-TQWMY-CWH2D</td></tr><tr><td>Windows Server Standard</td><td>ServerStandardACor</td><td>N2KJX-J94YW-TQVFB-DG9YT-724CC</td></tr><tr><td><strong>1803</strong></td><td></td><td></td></tr><tr><td>Windows Server Datacenter</td><td>ServerDatacenterACor</td><td>2HXDN-KRXHB-GPYC7-YCKFJ-7FVDG</td></tr><tr><td>Windows Server Standard</td><td>ServerStandardACor</td><td>PTXN8-JFHJM-4WC78-MPCBR-9W4KR</td></tr><tr><td><strong>1709</strong></td><td></td><td></td></tr><tr><td>Windows Server Datacenter</td><td>ServerDatacenterACor</td><td>6Y6KB-N82V8-D8CQV-23MJW-BWTG6</td></tr><tr><td>Windows Server Standard</td><td>ServerStandardACor</td><td>DPCNP-XQFKJ-BJF7R-FRC8D-GF6G4</td></tr></tbody></table>
<li>ServerRdsh, Server Azure Datacenter editions <ahref="https://learn.microsoft.com/en-us/azure/virtual-desktop/windows-10-multisession-faq"target="_blank"rel="noopener noreferrer">officially</a> do not support activation on non-azure systems.</li>
<h2class="anchor anchorWithStickyNavbar_LWe7"id="how-to-remove-kms38">How to remove KMS38?<ahref="#how-to-remove-kms38"class="hash-link"aria-label="Direct link to How to remove KMS38?"title="Direct link to How to remove KMS38?"></a></h2>
<ul>
<li>In MAS, go to KMS38 Activation and apply the Remove KM38 Protection option.</li>
<li>After that, In MAS, go to Troubleshoot and apply the Fix Licensing option.</li>
<li>Done.</li>
</ul>
<hr>
<h2class="anchor anchorWithStickyNavbar_LWe7"id="kms38---server-coracor">KMS38 - Server Cor/Acor<ahref="#kms38---server-coracor"class="hash-link"aria-label="Direct link to KMS38 - Server Cor/Acor"title="Direct link to KMS38 - Server Cor/Acor"></a></h2>
<ul>
<li>Windows Server Cor/Acor (No GUI) editions don't have the <code>clipup.exe</code> file.</li>
<li>To KMS38 activate it, you need to download the <code>ClipUp.exe</code> file from <ahref="/assets/files/ClipUp-35a116e9ec8a086319a5a83e176f6156.zip"target="_blank">this link</a>.<br>
<!---->This file has digital signatures that can be verified. You can also get this file from the official <ahref="https://download.microsoft.com/download/1/6/F/16FA20E6-4662-482A-920B-1A45CF5AAE3C/14393.0.160715-1616.RS1_RELEASE_SERVER_EVAL_X64FRE_EN-US.ISO"target="_blank"rel="noopener noreferrer">Windows Server 2016 x64 RTM ISO</a>.</li>
<li>Put the <code>ClipUp.exe</code> file beside the KMS38 Activation script. That would be either <code>MAS_AIO.cmd</code> or <code>KMS38_Activation.cmd</code></li>
<li>The activation script will check for <code>ClipUp.exe</code> in the current folder (from where the script is running) and will use it accordingly.</li>
</ul>
<hr>
<h2class="anchor anchorWithStickyNavbar_LWe7"id="kms38-protection">KMS38 Protection<ahref="#kms38-protection"class="hash-link"aria-label="Direct link to KMS38 Protection"title="Direct link to KMS38 Protection"></a></h2>
<ul>
<li>KMS38 Activation is vulnerable to unintended replacement by a 180-Day KMS Activator.</li>
<li>From MAS 1.7, the script will enable KMS38 protection by default.</li>
<li>If you are going to use <ahref="https://github.com/abbodi1406/KMS_VL_ALL_AIO"target="_blank"rel="noopener noreferrer">KMS_VL_ALL</a> by abbodi1406 or <ahref="/">MAS</a> (Online KMS option) for <strong>Office activation</strong>, then you can choose to remove this protection.</li>
<li>Below is the explanation for how the script protect KMS38.</li>
<li>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 the Global KMS IP. Another fact is that if Localhost (IP range 127.0.0.0/8) is defined as the 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.</li>
<li>Script steps-<!---->
<ul>
<li>Set the Windows edition-specific KMS IP to Localhost (127.0.0.2)</li>
<li>Protect the below Registry from edit and delete<br>
<h2class="anchor anchorWithStickyNavbar_LWe7"id="command-line-switches">Command line Switches<ahref="#command-line-switches"class="hash-link"aria-label="Direct link to Command line Switches"title="Direct link to Command line Switches"></a></h2>
<h2class="anchor anchorWithStickyNavbar_LWe7"id="manual-activation">Manual Activation<ahref="#manual-activation"class="hash-link"aria-label="Direct link to Manual Activation"title="Direct link to Manual Activation"></a></h2>
<p>This is for those who want to perform manual activation. If you want a tool to do this for you, then check <ahref="/#download--how-to-use-it">here</a>.<br>
<!---->We can perform the manual activation process in 2 ways.</p>
<h3class="anchor anchorWithStickyNavbar_LWe7"id="1--from-ready-made-ticket">1- From Ready-Made Ticket<ahref="#1--from-ready-made-ticket"class="hash-link"aria-label="Direct link to 1- From Ready-Made Ticket"title="Direct link to 1- From Ready-Made Ticket"></a></h3>
<ul>
<li>Open Windows PowerShell as administrator, and enter the following commands in the sequence in which they are given.</li>
<li>Enter the key (Replace <code><key></code> with the key from the above list) with the following command:<br>
<code>slmgr /ipk <key></code></li>
<li>Download the Universal ticket from <ahref="/assets/files/Tickets-a2c5b276276c43ce40d84e13ed1d85b7.zip"target="_blank">here</a> and extract the downloaded file.</li>
<li>Find a file named <code>KMS.xml</code> in the extracted folder.</li>
<li>Copy that ticket file and paste it in the following folder:<br>
<li>Now run the below command in PowerShell to apply the ticket:<br>
<code>clipup -v -o</code></li>
<li>Check the Activation Status with the following command:<br>
<code>slmgr /xpr</code></li>
<li>Done.</li>
</ul>
<hr>
<h3class="anchor anchorWithStickyNavbar_LWe7"id="2--from-scratch">2- From Scratch<ahref="#2--from-scratch"class="hash-link"aria-label="Direct link to 2- From Scratch"title="Direct link to 2- From Scratch"></a></h3>
<p>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.</p>
<ul>
<li>Download the file from the official MS link and extract the .cab file.<br>
<li>Find the file named <code>filf8377e82b29deadca67bc4858ed3fba9</code> (Size: 330 KB) and rename it as <code>gatherosstate.exe</code></li>
<li>Make a folder named <code>Files</code> in C drive, <code>C:\Files</code> and copy the <code>gatherosstate.exe</code> file in that folder.</li>
<li>Open Windows PowerShell as administrator and enter the following commands in the sequence in which they are given.</li>
<li>Enter the key (Replace <code><key></code> with the key from the above list) with the following command:<br>
<code>slmgr /ipk <key></code></li>
<li>Copy the below code all at once and enter in PowerShell to modify the <code>gatherosstate.exe</code> file.<br>
<!---->This code to modify the file is based on <ahref="https://github.com/asdcorp/GamersOsState"target="_blank"rel="noopener noreferrer">GamersOsState</a>.</li>
<li>A GenuineTicket.xml file should be created in the folder <code>C:\Files\</code>. Now, let's apply it:<br>
<code>clipup -v -o -altto C:\Files\</code></li>
<li>Check Activation Status with the following command:<br>
<code>slmgr /xpr</code></li>
<li>Done.</li>
</ul>
<p><strong>Notes:</strong></p>
<ul>
<li>To make the exact ticket used in MAS KMS38 script, fix the time with the below PowerShell command and then initiate the ticket generation process as per the steps mentioned above.<br>
<li>In the case of Windows Server Cor/Acor (No GUI) editions, the system doesn't have the <code>clipup.exe</code> file.<br>
<!---->To KMS38 activate it, you need to download the missing <code>ClipUp.exe</code> file from <ahref="/assets/files/ClipUp-35a116e9ec8a086319a5a83e176f6156.zip"target="_blank">this link</a>.<br>
<!---->This file has digital signatures that can be verified. You can also get this file from the official <ahref="https://download.microsoft.com/download/1/6/F/16FA20E6-4662-482A-920B-1A45CF5AAE3C/14393.0.160715-1616.RS1_RELEASE_SERVER_EVAL_X64FRE_EN-US.ISO"target="_blank"rel="noopener noreferrer">Windows Server 2016 x64 RTM ISO</a>.<br>
<!---->Put the <code>ClipUp.exe</code> in the <code>C:\Windows\System32</code> folder and then initiate the above-mentioned activation process. Once the activation is complete, you can remove the file.</li>
</ul>
<hr>
<h2class="anchor anchorWithStickyNavbar_LWe7"id="setup-preactivate">Setup Preactivate<ahref="#setup-preactivate"class="hash-link"aria-label="Direct link to Setup Preactivate"title="Direct link to Setup Preactivate"></a></h2>
<ul>
<li>Check the Extract OEM option in the MAS <code>Extras</code> section if you want pre-activated Windows installation.</li>
<h2class="anchor anchorWithStickyNavbar_LWe7"id="troubleshooting">Troubleshooting<ahref="#troubleshooting"class="hash-link"aria-label="Direct link to Troubleshooting"title="Direct link to Troubleshooting"></a></h2>
