Visio 0xC004F04F: the licence store is missing its management data

Fix it now

Microsoft’s published description is exact: the Software Licensing Service reported that license management information was not found in the licenses. Read what the store actually holds before you change anything, because on a machine running both Office and Visio the arrangement you are about to break may well be a supported one.

cd "C:\Program Files\Microsoft Office\root\Office16"
cscript ospp.vbs /dstatusall
cscript ospp.vbs /dstatus

1. Write down every product name and the last five characters of every key the output reports. Expect to find more entries than you were told about.
2. Do not remove anything yet. A perpetual or volume-licensed Visio next to a subscription Office is supported, so an extra entry is not by itself evidence of a problem.
3. Run Microsoft’s Microsoft 365 activation troubleshooter, or the OLicenseCleanup script it publishes, which clears the licence and identity state in the documented order.
4. Sign in again for a subscription, or reapply a key with cscript ospp.vbs /inpkey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX then cscript ospp.vbs /act.

Before running /unpkey on anything, confirm you hold the full 25-character key or the licence record for it. The last five characters shown by /dstatus cannot be used to reinstall a key.

If activation succeeds you can stop here. If it does not, the next section explains what the store holds and which of its entries genuinely do not belong.

Why it happens

Office, Visio and Project on a Click-to-Run install share one licence store. Each entitlement writes its own entries into it – a volume key, a retail key, a subscription token – and the platform reads all of them when an application starts. 0xC004F04F is that platform reporting that the management information it expected to find alongside a licence is not there.

The related codes in this family are duplication errors rather than lookup failures, and the difference decides what you do next. 0xC004F054 is published as license management information having duplicated data. 0xC004F052 is published as the licences containing duplicated properties. Neither is another way of saying “a lookup failed”, and treating them as such sends you hunting for a missing entry when the store actually holds two of something.

Now the part that gets machines broken by well-meaning troubleshooting. Mixing licensing models is not the fault. Microsoft documents Microsoft 365 Apps alongside a volume-licensed Visio LTSC Professional 2024 as supported, and the same for retail Project. What has to match is the installation technology, the architecture and the update channel – and the perpetual releases need a recent enough Microsoft 365 Apps: 2408 or later for the 2024 products, 2108 for 2021, 1808 for 2019. Signing a user out of their subscription to “clean up” a machine like that deactivates working software for no reason.

The other two codes people bring to this error, 30050-1039 and 30020-15, are Click-to-Run setup failures with no published meaning. They come from the installer, not the licensing platform. If those are what you are actually looking at, the deployment log, the previous-version removal and the security software are the places to look, and ospp.vbs will tell you nothing useful.

Full reference

What Microsoft actually publishes for each code

Two of those five are duplication errors and two are not licensing codes at all. That is worth internalising before you start, because the remedy for a missing entry and the remedy for a duplicated one are not the same, and neither of them is anywhere near an installer log.

What a mixed machine is allowed to be

Do not remove a key or sign a user out because the store contains more than one licensing model. That is a supported arrangement. Remove an entry only when you can say which product it belongs to and confirm that product is not installed on this machine – and only when you hold the full key.

Microsoft’s documented reset, in order

1. Close every Office application, including Outlook and Teams.
2. Remove the licence files: %localappdata%\Microsoft\Office\Licenses for a current build, and %localappdata%\Microsoft\Office\16.0\Licensing where shared computer activation is in use.
3. On a volume-licensed machine, remove keys with cscript ospp.vbs /unpkey:<last5> from C:\Program Files\Microsoft Office\root\Office16, having confirmed you hold the full keys.
4. Delete the per-user licensing and identity state: HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Licensing and HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity.
5. Remove the Office entries from Control Panel, then Credential Manager, then Windows Credentials.
6. Restart, open one application, and sign in or reapply the key before opening anything else.

Microsoft publishes automated equivalents of that sequence – the Microsoft 365 activation troubleshooter, and the OLicenseCleanup script for scripted estates – and on any machine you did not build yourself they are the safer route. They clear the same state in the same order without depending on someone reading a registry path correctly at half past five.

When the store looks clean and activation still fails

• Confirm the Software Protection service is running: sc query sppsvc.
• Read what the service actually said with cscript ospp.vbs /ddescr:<code> and cscript ospp.vbs /dhistoryacterr.
• Check whether Visio and Office are genuinely on the same channel and architecture. A mismatch there produces licensing symptoms that look like store damage.
• Run an Office Online Repair last, not first. It rewrites files and takes a while, and it does not clear licence state, which is what this code is about.
• If the codes you are seeing are 30050-1039 or 30020-15, stop reading the store. Those are installer failures and the deployment log is where the answer is.

Every code this article covers

Confirm the fix worked

1. cscript ospp.vbs /dstatusall lists exactly the products installed, each once, with a licensed status.
2. Visio opens and File, then Account shows the expected product with no activation banner.
3. Word on the same machine reports the same version, channel and architecture under About.
4. sc query sppsvc shows the Software Protection service running.
5. Restart and reopen Visio to confirm the state survives rather than reverting.

Questions people ask about this