Ohook Activation for Office
Welcome to the definitive guide on the Ohook activation method, a cornerstone feature of the Microsoft Activation Scripts (MAS) suite. If you're looking for a persistent, offline-capable activation solution for modern versions of Microsoft Office, Ohook is the answer. This method provides a stable and reliable way to activate Volume-licensed Office products, including Microsoft 365, by cleverly intercepting the software's activation checks.
This pillar page will cover everything from the underlying technology of the DLL hook to step-by-step activation instructions and troubleshooting common issues. Whether you're a tech enthusiast curious about how it works or a user seeking a straightforward activation path, this guide has you covered.
What is Ohook and How Does It Work?
Ohook is an activation method that works by using a custom-built Dynamic-Link Library (DLL) file to intercept and handle Microsoft Office's licensing and activation verification calls. In essence, it tricks the Office application into believing it has been successfully activated without ever needing to contact Microsoft's activation servers.
The core of the method is a file named OAUDEV.DLL. When the Ohook activation process is run from the MAS script, this DLL is placed in the C:\Windows\System32 directory. The script then registers this DLL with the Office Software Protection Platform. When an Office application like Word or Excel starts, it loads its licensing components. Due to the registration, the system now loads our custom OAUDEV.DLL as part of this process. This technique is known as DLL hooking.
Once loaded, the hook intercepts function calls related to activation status. Instead of letting Office check with Microsoft servers, the custom DLL provides a spoofed "success" response, confirming that the product is licensed. This all happens locally on your machine, instantly, and without an internet connection, making it a highly reliable and persistent solution.
The Technical Details of the DLL Hook
For those interested in the specifics, the Ohook method targets the Office Software Protection Platform (OSPP) service. Modern Office versions use a component that periodically checks the license validity. Ohook's OAUDEV.DLL is specifically engineered to hook into the functions responsible for these checks.
When MAS installs Ohook, it performs two key actions:
- File Placement: It copies the correct version of
OAUDEV.DLL(either x64, x86, or ARM64) to the System32 folder. This location is part of the standard Windows search path for DLLs, ensuring it can be found by system processes. - COM Registration: The script registers the DLL as a Component Object Model (COM) server that implements the necessary interfaces for Office's licensing system. This registration is what tells Office to load and use this specific DLL for certain activation-related tasks.
Crucially, this method does not modify any core Office program files. It simply adds one file (OAUDEV.DLL) and creates a few registry keys for the COM registration. This makes the process completely reversible. If you choose to uninstall Ohook via the MAS script, it removes the DLL and cleans up the registry, returning your system to its original state without any lingering files or modifications to your Office installation.
Supported Office Products and Suites
Ohook is designed exclusively for Volume License (VL) versions of Microsoft Office. If you have a Retail version installed, you must first convert it to a Volume license, a process that the MAS script can perform automatically. For more details on this, see our guide on /guides/office-retail-to-volume.
Ohook supports the following Office products:
- Microsoft 365 Apps for Enterprise: The most common version used with this method.
- Office LTSC 2024 / 2021: All Long-Term Servicing Channel versions.
- Office 2019 / 2016: Volume editions of these perpetual license products.
- Individual Volume apps such as Visio and Project from the above suites.
It is important to note that Ohook is not intended for Retail, OEM, or Microsoft Store (UWP) versions of Office. Using the MAS script ensures you are targeting a compatible, converted-to-volume installation for a successful activation.
How to Activate Office with Ohook using MAS
Activating Office with Ohook is a simple process using the all-in-one MAS script. Follow these steps carefully.
-
Download and Run MAS: The easiest way to get started is by using the official PowerShell one-liner. Open a PowerShell window with administrator rights (right-click Start menu > PowerShell (Admin)) and run the following command:
irm https://get.activated.win | iexAlternatively, you can download the script files directly from the official project site at /.
-
Navigate to the Activation Menu: Once the script's main menu appears, press the corresponding key to enter the
Microsoft Officeactivation section. -
Select the Ohook Method: Inside the Office menu, you will see options for different activation methods. Choose the
Ohookactivation option. The script will also have options to check activation status or uninstall the method later. -
Let the Script Work: The script will now automatically perform all necessary tasks. This includes checking your Office version, converting it to Volume License if needed (with your confirmation), copying the
OAUDEV.DLLfile, and registering it. This process usually takes less than a minute. -
Verify Activation: Once the script reports
Activation Successful, you can verify it yourself. Open any Office application, such as Word or Excel. Go toFile > Account. Under Product Information, you should see the messageProduct Activated. The activation is now complete and will persist.
Ohook on ARM64 and macOS
Windows on ARM64: The Microsoft Activation Scripts and the Ohook method are fully compatible with Windows on ARM devices, such as the Surface Pro X. The MAS script is intelligent enough to detect your system's architecture. When you run the Ohook activation on an ARM64 device, the script automatically selects and installs the ARM64-native version of OAUDEV.DLL, ensuring optimal performance and compatibility. There are no extra steps required from the user; the process is seamless.
macOS: Microsoft Activation Scripts and Ohook are Windows-only tools. They are not compatible with macOS. Office for Mac uses a completely different architecture and licensing mechanism (typically a Volume License Serializer file, Microsoft_Office_20_VL_Serializer.pkg). Users on macOS will need to find activation solutions specifically designed for that platform, which are outside the scope of MAS.
Troubleshooting Common Ohook Issues
While Ohook is very reliable, you may encounter a few common issues, most of which are easily resolved.
-
Antivirus Flags: This is the most common problem. Antivirus software may detect
OAUDEV.DLLor the MAS script itself as a threat (e.g.,HackTool:Win32/AutoKMS,Generic.Trojan). This is a false positive. The tools are flagged because they are designed to bypass software licensing, which some AV vendors classify as malicious behavior. To resolve this, create an exclusion in your antivirus program for the MAS script folder and for the fileC:\Windows\System32\OAUDEV.DLL. -
Activation Not Sticking: If Office reverts to an unlicensed state, it's almost always because your antivirus has quarantined or deleted
OAUDEV.DLL. Check your AV's quarantine, restore the file, and create a permanent exclusion. Afterward, re-run the Ohook activation from the MAS script to ensure the COM registration is corrected. -
Unsupported Office Version Error: If the script reports that your Office version is not supported, it's likely because you have a Retail or Microsoft Store version installed. Use the built-in utility in MAS to convert your Office installation from Retail to Volume License, then try the Ohook activation again.
-
File Access Denied: If you see errors related to file access or registry permissions, it means the script was not run with sufficient privileges. Ensure you are running the PowerShell command or the
MAS_AIO.cmdscript as an administrator.
Is Ohook a Permanent Activation?
Yes, Ohook provides a persistent, or de facto permanent, activation. Unlike KMS activation, which requires renewal every 180 days, Ohook works continuously as long as the OAUDEV.DLL hook is in place. The activation check is handled locally every time an Office application starts, so it never "expires."
However, it's important to understand that major Microsoft Office updates could potentially overwrite or conflict with the COM registration used by the hook. In such rare cases, Office might report itself as unlicensed. The fix is simple: just re-run the Ohook activation task from the MAS menu. This will re-register the DLL and instantly restore the activated state. For this reason, it's a good idea to keep the MAS script handy.
Is It Safe to Use Ohook?
Safety comes down to the source. The Ohook method, as implemented in the official Microsoft Activation Scripts from the Massgrave repository, is safe. The project is open-source, meaning the code is publicly available for anyone to inspect. The scripts and the included OAUDEV.DLL are purpose-built for activation and do not contain any malware, spyware, or other malicious payloads.
The primary risk comes from downloading MAS from unofficial, third-party websites, YouTube videos, or torrents. These sources often bundle the legitimate script with malware. To ensure your safety, only use the official PowerShell one-liner (irm https://get.activated.win | iex) or download the script directly from the project's homepage at /. By sticking to the official source, you can be confident that the tool is clean.
How Does Ohook Differ from KMS Activation?
Ohook and KMS are two distinct activation methods available in MAS, each with its own advantages.
-
Mechanism: Ohook uses a local DLL hook to trick Office into thinking it's activated. KMS (Key Management Service) emulates a network activation server on your local machine that Office communicates with to validate its license.
-
Permanence: Ohook is a 'set-and-forget' persistent activation that doesn't expire. KMS activation lasts for 180 days, after which it must be renewed. The MAS KMS script installs a service that automatically handles this renewal in the background, making it effectively permanent as well, but the underlying mechanism is different.
-
Scope: Ohook is designed only for Microsoft Office. KMS activation, on the other hand, can be used for both Microsoft Office and Windows. For a complete activation solution, many users opt for KMS for Windows (as detailed in our /guides/kms-activation-windows guide) and Ohook for Office, as it's often seen as a cleaner, more direct method for the Office suite.
Ultimately, for activating Office, Ohook is often preferred for its simplicity and the fact that it requires no background services or scheduled tasks for renewal.