0x4004F00C Office Activation Error: What It Means and How to Fix It

Word opens, a yellow bar about activation sits under the ribbon, and a dialog or a command window has just shown you the code 0x4004F00C. Nothing has failed yet. The 0x4004F00C Office activation error reports a state, not a crash: Office is installed, has not activated, and is running inside its grace period. Your job is to finish activation before that period ends: sign in or enter your key under File > Account, or on volume editions run cscript ospp.vbs /act (after /inpkey if no valid key is installed).

Why hurry if everything still works? Because of the counter. When the grace days run out, Office drops to reduced functionality and the title bar reads “Unlicensed Product”. Documents stay where they are. Editing stops.

People usually meet the code in one of two places. Administrators find it in the output of cscript ospp.vbs /dstatus, next to “LICENSE STATUS: —OOB_GRACE—” and a line called REMAINING GRACE. Home and small-office users get it after an activation attempt that did not go through. Same code. Different fixes, and that is the catch: 0x4004F00C looks identical on a retail copy and on a volume install, yet the two activate in different ways. So the steps below begin by reading which kind of license sits on the machine. One command.

How to fix the 0x4004F00C Office activation error

Read the license channel with ospp.vbs /dstatus, then activate the way that channel expects. Retail Office activates under File > Account, by signing in or entering the key. Volume Office activates against a KMS host with /sethst and /act, or with a MAK through /inpkey and /act.

1. Close every Office app. Then check the clock: Settings > Time & language > Date & time, with Set time automatically and Set time zone automatically both switched on.
2. Open Command Prompt as administrator and change to the Office folder: cd "C:\Program Files\Microsoft Office\Office16". Microsoft also lists C:\Program Files\Microsoft Office\root\Office16, and 32-bit Office on 64-bit Windows sits under Program Files (x86).
3. Run cscript ospp.vbs /dstatus. Write down four lines: LICENSE NAME, LICENSE DESCRIPTION (it names the channel: Retail, MAK or VOLUME_KMSCLIENT), ERROR CODE and REMAINING GRACE.
4. Retail channel: open Word, go to File > Account and choose Activate Product or Sign in. Use the Microsoft account the key was redeemed with. A new key has to be redeemed at the Office setup page first; sign in after that.
5. Volume channel with a company KMS host: connect to the company network or VPN and run cscript ospp.vbs /act. Host not found automatically? Point Office at it with cscript ospp.vbs /sethst:kms.contoso.com, your own host name in place of the example, and run /act again.
6. Volume channel with a MAK, or the wrong key installed: put the right one in with cscript ospp.vbs /inpkey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX, then run cscript ospp.vbs /act.
7. Clear out leftover keys that hold Office in grace. Take the last five characters of each key you do not use from the /dstatus output and run cscript ospp.vbs /unpkey:XXXXX once per key.
8. Run cscript ospp.vbs /dstatus again. “LICENSE STATUS: —LICENSED—” means 0x4004F00C is gone. Still OOB_GRACE? cscript ospp.vbs /dhistoryacterr or /dhistorykms shows why the attempt failed.

Steps 4, 5 and 6 are alternatives. You do the one that matches the channel from step 3 and skip the other two. Guessing the channel is the mistake I see most often: someone with a retail key spends an evening on /sethst, which can never work for that key.

Tip: cscript ospp.vbs /ddescr:0xC004F074 prints the plain-language description of whatever code an activation attempt returns. Swap in your own code and you save a search each time it changes. The one in the example means no KMS host answered, and our 0xC004F074 activation error guide has a section for Office.

How do I check my Office license status and the days left?

Open Command Prompt as administrator, change to the Office16 folder and run cscript ospp.vbs /dstatus. The output names the installed license, its channel, the current status code and the grace days that remain. On a volume install that has not activated yet, it looks roughly like this, with the edition lines shortened:

LICENSE NAME: (edition name)
LICENSE DESCRIPTION: (version), VOLUME_KMSCLIENT channel
LICENSE STATUS:  ---OOB_GRACE---
ERROR CODE: 0x4004F00C
ERROR DESCRIPTION: The Software Licensing Service reported that the application is running within the valid grace period.
REMAINING GRACE: 30 days
Last 5 characters of installed product key: XXXXX

Four of those lines matter. LICENSE DESCRIPTION is the one I read first, since the channel written there decides everything that follows. LICENSE STATUS tells you if Office is still in grace or already licensed. REMAINING GRACE is your deadline. And the last five characters identify which key Office is trying to activate, which is not always the key you typed yesterday.

More than one block in the output? Then more than one key is installed, and each has its own status. Worth knowing before you touch anything else.

If the command cannot find the script, you are in the wrong folder, so try the root\Office16 path or the Program Files (x86) one from step 2. (The folder is called Office16 for every current perpetual version, Office 2024 included, so the number in the path is not a mistake.)

What does 0x4004F00C mean: an error or a warning?

Neither, strictly. 0x4004F00C means “The Software Licensing Service reported that the application is running within the valid grace period.” Office has not been activated and is running in its out-of-box (OOB) grace period, so nothing is broken yet, but activation has to succeed before the grace expires.

Look at the prefix. Codes that begin with 0xC are errors. Codes that begin with 0x4 are informational statuses from the Software Protection Platform. Internally this one carries the name SL_I_OOB_GRACE_PERIOD, and the description that ospp.vbs prints for it reads word for word as quoted above.

So why does Office stay in that state instead of activating by itself? In most cases for one of three reasons: the product key is missing or wrong, the KMS host cannot be reached, or the account you signed in with does not hold the license. A reinstall fixes none of those. Activation does.

Which fix matches which cause?

Pick the fix by the channel that /dstatus shows, not by the code alone. The table pairs each common cause with the sign that gives it away and the fix that usually ends the grace period. Microsoft 365 Apps stand outside it, because ospp.vbs does not cover them.

A word on the top row, since it tends to confuse people the most. Microsoft Office LTSC Professional Plus 2024 and the 2021 release, when deployed with a KMS client key, go looking for a KMS host. Inside a company network they find one. At home, or anywhere no host is configured, they sit in OOB_GRACE until the days are gone.

Retail editions fail differently. Office Home 2024 and Office Home & Business 2024 bind the key to a Microsoft account; sign in with another account and Office finds no license at all. Check which account holds it before you blame the key.

Scripted installs produce the third row. A deployment built with the Office Deployment Tool can install the key and stop there if the activation step was left out. One /act closes it.

Microsoft itself names the last three rows among the causes of Office activation errors: firewalls, antivirus and proxy settings; a wrong date, which it puts first in its list for Office 2016 to 2024; and two installations in conflict, for example a preinstalled Microsoft 365 trial next to Office 2024.

How long is the Office grace period?

For volume-licensed Office on a KMS client key, the out-of-box grace typically lasts 30 days from installation, and /dstatus shows what is left as REMAINING GRACE. Retail Click-to-Run installs do not show a fixed counter: Office asks you to sign in or enter a key, keeps showing activation prompts, and falls into reduced functionality if nothing changes.

Is the code dangerous in the meantime? No. It only reports that the grace period is still running. Trouble starts at zero, when Office enters reduced functionality and shows “Unlicensed Product” until it activates. In that state you can open and print documents. You cannot create or edit them. No data is lost, and once activation succeeds every feature comes back at once. No reinstall.

Waiting does not help, though. The counter runs down no matter how rarely you open Office, so closing Word for two weeks buys nothing. My advice: sort activation out in the first week, while there is still time to read an error message calmly. Title bar already says Unlicensed Product? Our guide to the Unlicensed Product message in Office picks up from that point.

Note: /rearm resets the grace period on volume editions. Microsoft documents it for KMS and Active Directory activation scenarios and limits the number of rearms. It does not activate Office, so I would not treat it as a fix.

Why does Office say it is in a grace period after I entered a key?

Usually for one of three reasons: the key was installed but activation never ran or failed, an older key is still installed and takes priority, or the key is a volume key that needs a KMS host. Run cscript ospp.vbs /dstatus and compare the last five characters with your key. Not yours? Remove the old one with /unpkey, then run /act again.

Duplicate installs are the other usual suspect. Many new laptops ship with a Microsoft 365 trial. Put Office Home & Business 2024 on top of it and Office can end up checking the wrong license. Microsoft’s own fix is plain: uninstall the versions you do not use under Control Panel > Programs > Programs and Features, then restart. When an old version refuses to leave, our page on the Microsoft Office uninstall tool covers the leftovers.

Not sure the key went in the right way in the first place? The step-by-step Office 2019 activation guide shows the full sign-in and key flow. Same flow in Office 2021 and 2024.

Then there is the key itself. A cheap volume key sold as “lifetime” may install without complaint and then sit in grace forever, or activate briefly and fail at renewal. No command repairs that. The only fix is a different key. If that is where you are, HypestKey sells the Office LTSC Professional Plus 2024 key, and it arrives instantly by email.

Does ospp.vbs work for Microsoft 365 and Office 2024?

For Office LTSC 2024, Office LTSC 2021, Office 2019 and Office 2016, yes: Microsoft documents ospp.vbs for the volume editions, and /dstatus also reads retail installs of the same versions. For Microsoft 365 Apps and subscription Project and Visio, no. Microsoft points to a PowerShell script named vnextdiag.ps1 for those, because subscription licensing works through your account.

On Microsoft 365 Apps you will rarely meet 0x4004F00C by number. Its equivalent tends to be a sign-in prompt or a “Product Activation Failed” bar, and the way out is sign-in under File > Account, a subscription check and the Microsoft 365 activation troubleshooter. Microsoft’s page Unlicensed Product and activation errors in Office walks through that path.

What about the rest of this page? It applies to Office LTSC Professional Plus 2024, Office LTSC 2021, Office Home 2024, Office Home & Business 2024, Office 2021, Office 2019 and Office 2016 on Windows 11 and Windows 10. How much of it you need depends on the edition:

• Volume editions (LTSC 2024, LTSC 2021, 2019 Volume): every ospp.vbs step, KMS and MAK alike.
• Retail editions (Home 2024, Home & Business 2024, 2021 retail): date and time, sign-in under File > Account, /dstatus, /unpkey and the hunt for duplicate installs.
• Microsoft 365 Apps: sign-in, subscription check, the activation troubleshooter, and vnextdiag.ps1 for license details.

One remark on age. Office 2019 and Office 2016 have been out of support since October 14, 2025, and support for Office 2021 ended on October 13, 2026. The steps above still apply to all three.

What to do when /act still fails

Read the reason before you change anything else. Both cscript ospp.vbs /dhistoryacterr and cscript ospp.vbs /dhistorykms show why activation failed. Whatever code comes back, feed it to /ddescr and you get one sentence that says what went wrong.

Network errors in that history point to something between the PC and the activation service. Disable the firewall or antivirus temporarily, check the proxy settings, and try again.

Nothing network-related? Then walk through Microsoft’s short checklist for Office activation: the right account, only one Office version installed, correct date and time, firewall and proxy, and the activation troubleshooter. Dull list. In my experience it tends to catch what the commands missed, the account most of all.

And if the output shows a KMS client key on a home PC with no host to talk to, stop troubleshooting. That key stays in grace until it expires. I think the honest answer here is short: the fix is a retail or MAK key, installed with /inpkey and activated with /act.

Whichever branch you took, finish the same way. Close Office, open the elevated Command Prompt once more and run cscript ospp.vbs /dstatus. The line you want reads “LICENSE STATUS: —LICENSED—“.