Office 2016 Activation From the Command Line — ospp.vbs Reference

Finding ospp.vbs

It lives in the Office program folder — typically `C:\Program Files\Microsoft Office\Office16` for MSI installs, or under `Program Files\Microsoft Office\root\Office16` for Click-to-Run. Open an elevated Command Prompt and change into that folder before running anything.

The four switches that matter

Nearly every scenario uses this set.

• `cscript ospp.vbs /dstatus` — show the installed licences and their remaining days
• `cscript ospp.vbs /inpkey:<key>` — install a product key
• `cscript ospp.vbs /sethst:<host>` — point Office at a KMS host name
• `cscript ospp.vbs /act` — trigger activation

Reading the output

`/dstatus` prints the licence name, the last five characters of the key and the remaining grace period. A volume licence shows a countdown in days because it is a 180-day lease; a retail or Microsoft 365 licence shows a different status entirely, tied to the signed-in account.

Removing a licence cleanly

`cscript ospp.vbs /unpkey:<last five characters>` removes an installed key — the correct first step before applying a different one, and the step most guides skip. Restart every Office application afterwards so the change is picked up.

Legal ways forward

Whatever the cause, the compliant options are the same.

• A valid Microsoft licence, digital licence or volume agreement is the only fully compliant route
• Windows runs without activation — you get a watermark and locked personalisation, security updates still install
• Office without a licence opens files read-only; the free web and mobile apps stay fully usable
• Business, school and production machines should use the organisation's own licensing agreement

Office 2016 Command-Line Activation System Requirements & Compatibility (2026)

Office 2016 Command-Line Activation 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 2016 Command-Line Activation Troubleshooting: Common Errors & Fast Fixes

Most Office 2016 Command-Line Activation 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