Fix it now
Microsoft’s published description of 0xC004F001 is short: the Software Licensing Service reported an internal error. It did not reject your key and it did not fail to reach a server, so the usual answer is to clear the licence state and let Office rebuild it. Microsoft publishes both an automated route and a manual one, and the automated one is safer.
cd "C:\Program Files\Microsoft Office\root\Office16"
cscript ospp.vbs /dstatus
cscript ospp.vbs /ddescr:0xC004F001
- Close every Office application, including Outlook and anything loading an Office add-in.
- Run Microsoft’s Microsoft 365 activation troubleshooter, or the OLicenseCleanup script it publishes for scripted estates. Both clear the licence and identity state in the documented order.
- If you are doing it by hand, move the contents of
%localappdata%\Microsoft\Office\Licensesaside, and%localappdata%\Microsoft\Office\16.0\Licensingtoo if shared computer activation is in use on that machine. - Remove the Office entries from Control Panel, then Credential Manager, then Windows Credentials, and delete the HKCU Office 16.0 Common Licensing and Common Identity keys.
- Restart, open Word, and sign in or reapply the key with
cscript ospp.vbs /inpkey:followed bycscript ospp.vbs /act.
Move the licensing folders rather than deleting them the first time. On a volume-licensed machine, have the product key to hand before you clear anything, because you will be retyping it.
If Office activates you can stop here. If it does not, the next section covers what the store actually holds and why the codes people group with this one mean something else.
Why it happens
A Click-to-Run Office installation does not keep its licence in one place. There is a token under the user’s local application data, per-user licensing and identity keys in the registry, cached credentials in Credential Manager, and on volume-licensed machines a set of entries in the machine’s software protection store. All of them have to be readable and consistent with each other, and 0xC004F001 is the service reporting that something went wrong inside itself while working with them.
The word to notice in the published description is internal. This is not a refusal. The service has not looked at your entitlement and decided against it; it has failed part-way through an operation. That is why the remedy is to clear state rather than to change a key, and why the same fix works on a subscription machine and a volume-licensed one for different reasons.
Two codes get grouped with this one in the wild and neither belongs. 0xC004F019 is published as the service determining that the requested event ID is invalid. 0xC004F01A is published as the requested event not being registered with the service. Those are event-registration codes, not store-lookup failures, and reading them as “another way of saying the same thing” is how people end up clearing licence state to fix something else entirely.
One more detail worth getting right, because it changes what deleting a folder does. %localappdata%\Microsoft\Office\Licenses is the current per-user licence location. %localappdata%\Microsoft\Office\16.0\Licensing is the shared computer activation location, not an old folder left behind by an upgrade. On a session host, clearing the second one signs everybody out.
The per-user licence state is damaged
You have this one if The code appears the moment an Office application starts, on a machine that was activated before and has had no licensing change since.
- Close all Office applications.
- Run the Microsoft 365 activation troubleshooter, or move the contents of
%localappdata%\Microsoft\Office\Licensesto a backup folder. - Delete
HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Licensing. - Restart, open Word, and sign in or reapply the key.
Cached credentials point at an identity that no longer works
You have this one if Sign-in loops, or Office insists on an account that has been disabled or renamed.
- Open Control Panel, then Credential Manager, then Windows Credentials, and remove the Office entries.
- Delete
HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity. - Sign the user out of Office under File, then Account, if that option is still available.
- Restart and sign back in with the correct account.
The machine-level software protection store is inconsistent
You have this one if On a volume-licensed machine, cscript ospp.vbs /dstatus errors out or returns nothing sensible.
- Confirm the Software Protection service is running:
sc query sppsvcfrom an elevated prompt. - Run
sfc /scannowand let it complete. - Run
dism /online /cleanup-image /restorehealthto repair the component store underneath it. - Restart, then reapply the Office key and activate.
Those two commands repair Windows itself. They are safe to run and frequently clear a licensing fault whose real cause was a damaged system file.
Security software is quarantining files in the licensing folder
You have this one if The fault returns within hours or days of every repair, and only on machines running one particular product.
- Check that product’s quarantine and restore anything it has taken from the Office user data folders.
- Add the Office licensing folders to its exclusion list if the vendor supports exclusions.
- Clear the licensing state again and let Office rebuild it once the exclusion is in place.
This is a diagnosis for repeat failures rather than a cause Microsoft publishes for this code. It is worth checking precisely because nothing in the error points at it.
The user profile cannot be written
You have this one if The code affects roaming, redirected or mandatory profiles and nothing else.
- Confirm the user can create a file under
%localappdata%\Microsoft\Office. - Check disk quota and free space on the volume holding the profile.
- Where local application data is redirected to a read-only path, exclude the Office licensing folders from redirection so they can be written locally.
Full reference
Where Office keeps its licence state
| Location | What it holds |
|---|---|
%localappdata%\Microsoft\Office\Licenses |
The current per-user licence location, for builds from version 1909 onwards |
%localappdata%\Microsoft\Office\16.0\Licensing |
The shared computer activation licence location, not a legacy folder |
HKCU\Software\Microsoft\Office\16.0\Common\Licensing |
Per-user licensing state, removed as part of Microsoft’s documented reset |
HKCU\Software\Microsoft\Office\16.0\Common\Identity |
Cached Office account identity, including the Identities subkey |
| Credential Manager, Windows Credentials | Cached Office sign-in credentials |
| The software protection store | Machine-level licence data on volume-licensed installs, read through ospp.vbs |
Microsoft’s supported reset routes
- The Microsoft 365 activation troubleshooter, for a single machine with someone sitting at it.
- The enterprise Support and Recovery Assistant, for machines you are working on remotely or at scale.
- OLicenseCleanup, a script Microsoft publishes for the same job in a scripted deployment.
- signoutofwamaccounts, a companion script for clearing cached account state on managed devices running Windows 10 version 1803 or later.
- The manual sequence, which is the same steps in the same order and is worth knowing so you can tell what the tools did.
Reading what the service actually said
| Command | What it gives you |
|---|---|
cscript ospp.vbs /dstatus |
Licence information for installed product keys |
cscript ospp.vbs /dstatusall |
Licence information for all installed licences, including those without keys |
cscript ospp.vbs /ddescr:<code> |
The description the licensing service holds for an error code |
cscript ospp.vbs /dhistoryacterr |
The failure history for MAK and retail activation |
sc query sppsvc |
Whether the Software Protection service is running |
sfc /scannow |
Repairs damaged Windows system files underneath the licensing service |
Run these from C:\Program Files\Microsoft Office\root\Office16 on a 64-bit Office installation, or C:\Program Files (x86)\Microsoft Office\root\Office16 for 32-bit Office on 64-bit Windows. The path without the root folder is the older MSI-era location and does not exist on a Click-to-Run install, which is what produces the “Can not find script file” message people mistake for a broken Office.
The neighbouring codes, precisely
| Code | Published description | What that means for this fix |
|---|---|---|
0xC004F001 |
The Software Licensing Service reported an internal error | Clear the licence state and let it rebuild |
0xC004F019 |
The requested event ID is invalid | An event registration problem, not a licence store one |
0xC004F01A |
The requested event is not registered with the service | As above; clearing licence state is not aimed at this |
Stopping it coming back
A single occurrence on one machine is usually just damage, and the reset is the whole story. A machine that produces it repeatedly is telling you something else: security software taking files out of the licensing folder, a profile that cannot be written reliably, a disk that keeps filling, or a roaming configuration that half-copies the state at logoff. Fix the reset first so the person can work, then go and find which of those it is, because otherwise you will be back.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0xC004F001 |
The Software Licensing Service reported an internal error | Microsoft Learn |
0xC004F019 |
The Software Licensing Service determined that the requested event ID is invalid | Microsoft Learn |
0xC004F01A |
The Software Licensing Service determined that the requested event is not registered with the service | Microsoft Learn |
Confirm the fix worked
- Word shows the product as activated under File, then Account, with no banner.
- On a volume install,
cscript ospp.vbs /dstatusreports a licensed status for the expected product. - The licensing folder under the user’s local application data has been recreated with fresh content.
sc query sppsvcshows the Software Protection service running.- Restart and open Outlook to confirm activation survives a reboot rather than reappearing.
Questions people ask about this
Do I need to buy a new licence?
No. Nothing here consumes or invalidates an entitlement. A subscription lives on the account and a volume key lives on your agreement; clearing damaged local state touches neither.
Will I have to re-enter my product key?
On a volume-licensed machine, yes, so have it ready before you clear anything. On a subscription install you only sign in again.
Is it safe to delete the licensing folder?
Office rebuilds it, so yes in that sense. Move it rather than delete it the first time so you can reverse the change if the fault turns out to be somewhere else.
I also see 0xC004F019. Same fix?
Probably not. Microsoft publishes that one as the requested event ID being invalid, which is an event registration problem rather than a licence store one. Clearing licence state is not aimed at it, and if that is the only code you have, this is the wrong article.
ospp.vbs says it cannot find the script file.
You are in the wrong folder. On a Click-to-Run install the script lives under C:\Program Files\Microsoft Office\root\Office16. The path without root is the MSI-era location.
