<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 can activate all kinds of Office versions on Windows 8 and higher and their Server equivalent except Office 2010 and Office UWP apps.</li>
<li>This activation method works offline and activates Office permanently.</li>
<li>This activation method can survive Office repairs, Office updates, and even Windows major feature upgrades. You do not need to reactivate in these cases.</li>
<li>For the O365 subscription version, you can't get server side O365 specific features such as 1TB storage in Onedrive. However, almost all other features and 5GB storage in free onedrive account would work fine.</li>
<li>This activation method does not modify/patch any onboard system files, instead it installs a custom SPPC.dll (open source) file for the activation to work. Check further details in below "How does it work?" section.</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>
<li>As illustrated in the above 1st image, in the Official activation process of SPP based Office, Office asks <code>C:\Windows\System32\sppc.dll</code> about the activation status and that file asks the same thing to SPP (Software Protection Platform) <code>C:\Windows\System32\sppsvc.exe</code> and returns the message back to Office.</li>
<li>As illustrated in the above 2nd image, we modify this behavior by placing a custom <code>sppc.dll</code> file in Office folder without touching system's <code>C:\Windows\System32\sppc.dll</code> file and that custom file always returns the message that Office is activated. This is how ohook activation works.</li>
<li>You can find the source code of ohook custom sppc.dll file <ahref="https://github.com/asdcorp/ohook"target="_blank"rel="noopener noreferrer">here</a>.</li>
</ul>
<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>
<p>TL;DR all kinds of Office products are supported on Windows 8 and higher and their Server equivalent except Office 2010 and Office UWP apps.</p>
<li>For the O365 subscription version, you can't get server side O365 specific features such as 1TB storage in Onedrive. However, almost all other features and 5GB storage in free onedrive account would work fine.</li>
<li>Script doesn't convert any product to Volume or vice-versa. All products are activated with their own licence.</li>
<li>Key preference is given in this order, Retail:TB<!---->:Sub<!---->> Retail > OEM<!---->:NONSLP<!---->> Volume<!---->:MAK<!---->> Volume<!---->:GVLK</li>
<h2class="anchor anchorWithStickyNavbar_LWe7"id="unsupported-products">Unsupported Products<ahref="#unsupported-products"class="hash-link"aria-label="Direct link to Unsupported Products"title="Direct link to Unsupported Products"></a></h2>
<ul>
<li>Office on Windows 7 and their Server equivalent</li>
<li>Office 2010</li>
<li>Office UWP (Store apps)</li>
</ul>
<p><strong>Note:</strong></p>
<ul>
<li>Theoretically Office on Windows 7 and Office 2010 can be activated with Ohook but these versions require changing Office registry keys and renaming Office file names, that is why we have not added support for it. We recommend to use KMS activation for them.</li>
</ul>
<hr>
<h2class="anchor anchorWithStickyNavbar_LWe7"id="how-to-remove-ohook">How to remove Ohook?<ahref="#how-to-remove-ohook"class="hash-link"aria-label="Direct link to How to remove Ohook?"title="Direct link to How to remove Ohook?"></a></h2>
<ul>
<li>In MAS, goto Ohook Activation and apply Uninstall option.</li>
<li>After that, In MAS, goto Troubleshoot and apply Fix Licensing option. (Optional)</li>
<li>Done.</li>
</ul>
<hr>
<h2class="anchor anchorWithStickyNavbar_LWe7"id="custom-sppcdll-info">Custom sppc.dll Info<ahref="#custom-sppcdll-info"class="hash-link"aria-label="Direct link to Custom sppc.dll Info"title="Direct link to Custom sppc.dll Info"></a></h2>
<ul>
<li>Custom sppc.dll source code (Ohook 0.3) is available <ahref="https://github.com/asdcorp/ohook/archive/refs/tags/0.3.zip"target="_blank"rel="noopener noreferrer">here</a>.</li>
<li>In MAS AIO version, these 2 files are encoded in base64 to make MAS AIO version. In AIO script, <ahref="https://stackoverflow.com/a/35335273"target="_blank"rel="noopener noreferrer">instructions</a> are mentioned on how to decode files from Base64 format.<br>
<strong>How to create identical sppc.dll files from scratch?</strong></li>
<li>Download ohook 0.3 source code file from <ahref="https://github.com/asdcorp/ohook/archive/refs/tags/0.3.zip"target="_blank"rel="noopener noreferrer">here</a></li>
<li>Extract this zip file to a folder named <code>C:\ohook</code></li>
<li>Now download these two compiler archives, <ahref="https://github.com/brechtsanders/winlibs_mingw/releases/download/11.4.0-11.0.0-ucrt-r1/winlibs-i686-posix-dwarf-gcc-11.4.0-mingw-w64ucrt-11.0.0-r1.7z"target="_blank"rel="noopener noreferrer">mingw32</a> and <ahref="https://github.com/brechtsanders/winlibs_mingw/releases/download/11.4.0-11.0.0-ucrt-r1/winlibs-x86_64-posix-seh-gcc-11.4.0-mingw-w64ucrt-11.0.0-r1.7z"target="_blank"rel="noopener noreferrer">mingw64</a></li>
<li>Extract both archives with 7-zip in C drive, so that path would look like this,<br>
<code>C:\mingw32</code>
<code>C:\mingw64</code></li>
<li>Open Powershell as admin and enter below command to set the time and date,<br>
<li>Now open another Windows for Powershell and enter below command to create sppc.dll files,<br>
<code>Set-Location -Path C:\ohook</code><br>
<code>C:\mingw64\bin\mingw32-make.exe</code></li>
<li>Calculate the SHA-256 of the created sppc64.dll and sppc32.dll files using 7-zip or Powershell, it would be same as mentioned above.</li>
<li>Done, you can now close that powershell window and correct the date now.</li>
</ul>
<hr>
<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 wants to perform manual activation. If you want a tool to do this for you then check <ahref="/">here</a>.</p>
<ul>
<li>These steps are listed for Office 16.0 (2016, 2019, 2021, O365) C2R x64 bit on Windows x64 bit version.</li>
<li>Download ohook sppc.dll files from <ahref="https://github.com/asdcorp/ohook/releases/download/0.3/ohook_0.3.zip"target="_blank"rel="noopener noreferrer">here</a> or create sppc.dll files from scratch as per the above instructions.</li>
<li>Extract this zip file to a folder named <code>C:\ohook</code></li>
<li>Open command prompt as admin and enter below command to create a symlink of the system sppc.dll in the Office C2R System directory as sppcs.dll,<br>
<li>Some O365 editions check the license status and show the banner "There was a problem checking this device's license status". To stop this, enter below command,<br>
<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>Done.</li>
</ul>
<hr>
<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="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>
