Cara Mengaktifkan Office 2024 Activation with Ohook Gratis 2026 — Panduan Langkah

Why Office needs a different engine than Windows

Windows licensing lives in the Software Licensing Service and answers to slmgr. Office Click-to-Run licensing lives in its own service and answers to ospp.vbs. They share terminology and nothing else, which is the root of most confusion on this topic.

• Office Click-to-Run validates against a local licence store refreshed by the Office Licensing Service
• Windows activation state has no effect on Office activation state, and vice versa
• Retail Office is account-bound; volume Office is KMS or MAK bound; Microsoft 365 Apps is subscription-bound
• Ohook targets the Click-to-Run licence check specifically, which is why it needs no host and no renewal

What Ohook actually does

Ohook installs a small shim that intercepts the licence validation call inside the Office licensing component and returns a licensed verdict locally. Nothing is patched inside Word, Excel or Outlook, and no Office binary is modified — which is why Office updates do not usually break it.

• Permanent by design: there is no lease and nothing to renew
• Fully offline: no KMS host, no port 1688, no scheduled task
• Survives Office monthly channel updates in the vast majority of cases
• Applies per-installation rather than per-application
• Removable — uninstalling the shim returns Office to its unlicensed state cleanly

Supported Office products in 2026

Ohook covers the Click-to-Run family. Older MSI-based Office installs use the classic KMS path instead, and the tool selects it automatically when it detects one.

• Office LTSC 2024 — Professional Plus, Standard
• Office LTSC 2021 and Office 2019 (Click-to-Run)
• Office 2016 Click-to-Run installs
• Microsoft 365 Apps for Enterprise and for Business
• Project 2024 / 2021 / 2019 and Visio 2024 / 2021 / 2019

Step-by-step: activating Office 2024

The order matters. Applying the shim before Office finishes its first-run licence provisioning is the single most common cause of a failed run.

• Install Office and launch Word once, then close it — this provisions the licence store
• Sign out of any Microsoft account inside Office (File → Account → Sign out) to avoid a competing subscription state
• Add your tool folder to Windows Security exclusions before running anything
• Run the tool as administrator and select the Office / Ohook engine
• Close every Office application, then apply — a locked process is the second most common failure
• Reopen Word and check File → Account: it should read 'Product Activated' with no banner

Verify with ospp.vbs

Office ships its own licensing script. Run it from an elevated Command Prompt inside the Office install folder (typically C:\Program Files\Microsoft Office\Office16) for the authoritative answer.

• cscript ospp.vbs /dstatus — licence status, SKU and remaining grace for each installed product
• cscript ospp.vbs /dstatusall — the same report including expired and superseded licences
• cscript ospp.vbs /unpkey:XXXXX — removes a specific product key by its last five characters
• cscript ospp.vbs /act — forces an activation attempt on the current licence
• In the GUI: File → Account should show 'Product Activated' and no subscription warning bar

Errors you will actually hit

Office activation errors are more specific than Windows ones, which makes them easier to diagnose once you know the mapping.

• 0x4004F00C or a yellow subscription bar — the shim applied but Office cached the old state: close all Office apps and reopen
• 'Product Deactivated' after a monthly update — reapply the engine; the update replaced the licensing component
• 0xC004F017 — a mismatched product key for the installed SKU: remove the key with /unpkey, then reapply
• A signed-in Microsoft account overriding local licence state — sign out inside Office and reapply
• Outlook prompting for credentials — an account issue, not a licence issue; the two are unrelated

Ohook versus KMS for Office

If your Office install is volume-licensed and you have a real KMS host, use it — that is the supported path and it is auditable. Ohook is the better fit when there is no host, when the machine is offline, or when you need a state that does not expire. Ohook is permanent and offline but unsupported; KMS is renewable, requires a reachable host every 180 days, and is the documented enterprise mechanism.

The honest legal note

Office licensing tools are appropriate for products you already own, for evaluation, and for lab environments. Commercial use needs a purchased licence — that is the only route with support and audit compliance. This page explains the mechanism; the decision is yours.

Get the current build

The current 2026 build is distributed from officialkmsauto.com as a plain ZIP — no password, no installer, no bundled software, no signup. Verify the published SHA-256 before you extract, add the folder to Windows Security exclusions, then run the executable as administrator. Everything on this page works the same whether you use the tool or type the commands yourself.

Office 2024 Activation with Ohook System Requirements & Compatibility (2026)

Office 2024 Activation with Ohook is engineered for the modern Microsoft activation stack. The tool runs on Windows 7 SP1, Windows 8.1, Windows 10 (all builds from 1507 to 22H2) and every Windows 11 release including 23H2 and 24H2. Both x64 and ARM64 hardware are supported, and the activator also recognises Server SKUs such as Server 2016, 2019 and 2022. On the Office side, Click-to-Run installations of Office 2013, 2016, 2019, 2021, 2024 and Microsoft 365 are detected automatically — including LTSC channels. You do not need to uninstall a previous KMS client or remove an existing product key: the script reads the current edition through slmgr and routes it to the correct activation method (HWID for Windows, Ohook for Office).

• Windows 7 SP1 / 8.1 / 10 / 11 — all editions (Home, Pro, Education, Enterprise, IoT, LTSC)
• Windows Server 2008 R2 through Server 2025
• Office 2010, 2013, 2016, 2019, 2021, 2024 and Microsoft 365 Apps
• Architectures: x86, x64, ARM64
• .NET Framework 4.6+ (preinstalled on Windows 8.1 and later)

Office 2024 Activation with Ohook Troubleshooting: Common Errors & Fast Fixes

Most Office 2024 Activation with Ohook failures fall into three buckets: antivirus interference, missing administrator rights, or a corrupted Software Protection Service. If you see error 0xC004F074 the KMS host could not be contacted — disable Defender real-time scanning for two minutes, then re-run the activator. Error 0xC004C003 means the product key is blocked by Microsoft; switch to the HWID method, which bypasses key validation entirely by binding the licence to your motherboard's hardware ID. Error 0x80070005 (Access Denied) is always a UAC issue — right-click the executable and select "Run as administrator". If activation succeeds but reverts after reboot, open services.msc, set "Software Protection" to Automatic, and restart sppsvc.exe. For Office, run the Office Click-to-Run repair from Settings → Apps → Microsoft 365 → Modify → Quick Repair before retrying Ohook.

• 0xC004F074 — pause antivirus, re-run as administrator
• 0xC004C003 — switch to HWID (no key required)
• 0x80070005 — UAC denied, use "Run as administrator"
• Activation reverts on reboot — set "Software Protection" service to Automatic
• Office not detected — run Quick Repair, then re-run Ohook