Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

License Error 0xC004F07A

Office 0xC004F07A: the licensing service could not verify the licence

12 min read Updated October 5, 2026 Office & Microsoft 365 Licensing

Fix it now

Microsoft publishes one line for 0xC004F07A: the Software Licensing Service reported that the verification could not be done. It is a general licence-verification failure rather than a shared computer renewal code, so check that the account still holds a live seat, then re-issue the local licence state.

  1. Confirm the user still holds a licence: Microsoft 365 admin centre, Users, Active users, select the user, Licenses and Apps. Then check under Billing, Licenses, that the desktop applications are selected inside it.
  2. Confirm the subscription itself is not in the Disabled stage. Users lose the applications there, and it looks like a client fault from the desk.
  3. Have the user close every Office application, sign out of Windows and back in so a clean session starts, then open Word and sign in under File, then Account. An interactive sign-in re-issues what a silent refresh could not.
  4. If it still fails, clear the local licence state with Microsoft’s published tools rather than by hand: run OLicenseCleanup.vbs elevated, then signoutofwamaccounts.ps1 on Windows 10 1803 or later, then restart and sign in again.
  5. On a session host, confirm shared mode is still set: reg query HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration /v SharedComputerLicensing should return 1.

The Microsoft 365 activation troubleshooter in the Get Help app does most of the above without hunting for paths, and there is an enterprise command-line build of the same tool for estates.

If Office reports itself licensed after signing back in, you are done. If it does not, the next section covers what verification involves and which half of it has failed.

Why it happens

Take the published meaning first, because a good deal of writing about this code assigns it a much more specific job than Microsoft does. Microsoft’s Office activation tables give 0xC004F07A as: the Software Licensing Service reported that the verification could not be done. That is a general statement about verifying a licence. It is not published as a shared computer activation renewal failure, and reading it that way sends people to look at session hosts when the machine in front of them may be an ordinary desktop.

The shared computer renewal failure is real, but it is documented by its message rather than by a code: “Your shared computer license expires on (date) and we’re having trouble renewing it”. Microsoft’s stated cause is that automatic renewal was attempted and failed, most often because the machine was offline at the time, and the remedy is to select Renew or restore connectivity before the token expires. If that is the notice on screen, work that one.

Two of the companion codes have published meanings that have nothing to do with tokens at all. 0xC004F071 is the Software Licensing Service reporting that the plug-in manifest file is incorrect, and 0xC004F076 is the Software Licensing Service reporting that the requested plug-in cannot be found. Those describe the licensing service’s own component files being wrong or missing, which is a local repair problem. 0xC004F079 is not published at all.

So verification fails for two broad reasons, and they need different work. Either there is nothing valid to verify – the seat has gone, the subscription has moved into Disabled, the local licence files have been removed – or the service cannot carry the verification out, because its own components are damaged or it cannot reach what it needs to check against. Tenant question, or repair-and-connectivity question.

The seat behind the user has gone

You have this one if The admin centre shows the user unlicensed, or the subscription is past its renewal date.

  1. Read the subscription’s status in the admin centre, not just the seat count. Expired lasts 30 days for most offers with no user impact; Disabled follows and users lose the applications.
  2. If the subscription has lapsed, reactivate it. If the seat was reassigned, assign one back.
  3. Have the user sign out of Office and back in so the client re-asks rather than waiting for its own retry.

Group-based licensing does this quietly. A user who drops out of the group that grants the licence loses the seat with nobody touching their account.

The local licence state is stale or damaged

You have this one if One user on one machine, still fully licensed in the admin centre, and signing out and in has not helped.

  1. Close every Office application and confirm none survive in Task Manager.
  2. Run Microsoft’s OLicenseCleanup.vbs elevated to remove Office licence state, then signoutofwamaccounts.ps1 to clear cached Web Account Manager accounts.
  3. Restart, open Word, and sign in when prompted so a fresh licence is issued.
  4. For many machines, the enterprise command-line build of the Microsoft Support and Recovery Assistant does the same job and can be scripted.

The licensing service’s own components are wrong

You have this one if 0xC004F071 or 0xC004F076 appears alongside, pointing at an incorrect plug-in manifest or a plug-in that cannot be found.

  1. Run an Online Repair: right-click Start, select Apps and Features, select the Office product, select Modify, then Online Repair and Repair.
  2. Run sfc /scannow from an elevated prompt, then DISM /Online /Cleanup-Image /RestoreHealth, and restart.
  3. Retry activation before removing anything. A repair restores the licensing components without touching documents or profiles.

The client cannot reach what it needs to verify against

You have this one if Every user on one host is affected at once, and the timing lines up with a network change rather than a licensing one.

  1. Check the machine-level proxy that services actually use: netsh winhttp show proxy.
  2. Confirm the sign-in, licensing and configuration endpoints are permitted from this subnet, built from Microsoft’s endpoints web service rather than a static list.
  3. If a gateway inspects TLS, bypass the Microsoft 365 domains. Microsoft’s connectivity guidance asks for that and names interception of those domains as a known cause of connectivity problems.

The clock is wrong

You have this one if Verification fails across a whole machine or host and the system time is visibly out.

  1. Read the current state with w32tm /query /status, then run w32tm /resync.
  2. On a domain-joined machine, confirm it is syncing from a domain controller rather than an unreachable source.

w32tm /resync takes /computer, /nowait, /rediscover and /soft. It does not take /force – given an unrecognised switch, w32tm prints its usage block and never resynchronises at all.

Full reference

The four codes, and what Microsoft publishes for each

Code Published text
0xC004F07A The Software Licensing Service reported that the verification could not be done
0xC004F071 The Software Licensing Service reported that the plug-in manifest file is incorrect
0xC004F076 The Software Licensing Service reported that the requested plug-in cannot be found
0xC004F079 Not published

Read the middle two as a hint to repair rather than to re-license. A manifest that is wrong and a plug-in that cannot be found are both local component problems, and no amount of work in the tenant fixes either.

Shared computer activation, if that is what you are on

Item Value
Registry value SharedComputerLicensing, String (REG_SZ) set to 1
Registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration
Token location %localappdata%\Microsoft\Office\16.0\Licensing
Token lifetime 30 days, renewed automatically as expiry nears while the user is signed in and using the applications
Subscription licence location %localappdata%\Microsoft\Office\Licenses, licence ID begins EWW

The 30-day figure is Microsoft’s, and it explains the shape of the incidents. A host that lost its route to the licensing service does not fail that afternoon. It fails up to a month later, for everyone at once, at whatever moment each user’s token happens to run out – which is why the first person to report it usually has the oldest token rather than the newest problem.

Clearing licence state signs the user out of Office and forces a fresh interactive sign-in, including any multi-factor step. Do it with their agreement and their documents closed, not as a background sweep across every profile on a live session host.

Microsoft’s published reset, in order

  1. Run the Microsoft 365 activation troubleshooter from the Get Help app, or the enterprise command-line build for estates.
  2. Run OLicenseCleanup.vbs elevated to remove Office licence state.
  3. Run signoutofwamaccounts.ps1 elevated to clear cached Web Account Manager accounts. It needs Windows 10 version 1803 or later.
  4. If the device is Workplace Joined, run WPJCleanUp.cmd, or disconnect the account under Settings, Accounts, Access work or school.
  5. Restart, then sign in once from inside an Office application.

Telling which half broke

What you observe Where the fault is
One user affected, everyone else fine That user’s seat, credential or local licence state
Every user on one machine affected at once The machine: its network path, its clock, or its Office installation
Everyone on every machine, starting on one date The subscription, or a licensing group change
Only users who recently changed password Silent refresh failing on the credential, not on the licence
A plug-in manifest or missing plug-in code alongside Local components. Repair Office before anything else

Approaches that make this worse

  • Do not delete the whole of %localappdata%\Microsoft\Office. The documented licence locations are two specific subfolders, and the rest of that tree holds settings and caches you will be asked about later.
  • Do not assume a renewal problem because the phrase ‘renew’ appears somewhere. The published meaning of this code is verification, not renewal.
  • Do not use w32tm /resync /force. It is not a documented parameter and the command exits without resynchronising anything.
  • Do not reinstall Office as a first move. An Online Repair restores the licensing components without removing the product or its activation state.
  • Do not sweep licence state across a live session host. Users lose their sign-in mid-document and you will spend the afternoon on that instead.

When a licence is the actual fix

Where verification fails because the entitlement behind it has gone, restoring the licence is the whole fix and nothing local substitutes for it. Check first whether the seat was simply reassigned or dropped out of a licensing group, because putting back a seat you already own costs nothing. If the subscription itself has lapsed, reactivating it before it reaches the deleted stage is the cheapest route by a distance. Where you genuinely need more seats – most often on session hosts, where every user signing in needs a plan that carries shared computer activation – Arco supplies Microsoft 365 Apps for enterprise, and will help you count the people who actually sign in rather than the machines they sign in to.

Every code this article covers

Code What it points at Source
0xC004F07A The Software Licensing Service reported that the verification could not be done Microsoft Learn
0xC004F071 The Software Licensing Service reported that the plug-in manifest file is incorrect Microsoft Learn
0xC004F076 The Software Licensing Service reported that the requested plug-in cannot be found Microsoft Learn
0xC004F079 Raised by the licensing service in the same exchange. Not in Microsoft’s published Office activation tables not published by the vendor

Confirm the fix worked

  1. Open Word as the affected user and confirm File, then Account shows the product as licensed with no warning.
  2. Confirm a licence file exists under %localappdata%\Microsoft\Office\Licenses, or a token under 16.0\Licensing on a shared host.
  3. Sign out of Windows, sign back in, and open Excel to prove the state survives a new session.
  4. In the admin centre, confirm the seat is assigned and the desktop applications are selected within it.
  5. Come back to one machine after a few days and confirm no warning has reappeared.

Questions people ask about this

Does 0xC004F07A mean the shared computer licence failed to renew?

Not according to Microsoft. It publishes the code as the licensing service reporting that the verification could not be done, which is general. The shared computer renewal failure is documented by its on-screen message – your shared computer license expires on a date and we’re having trouble renewing it – with connectivity as the usual cause.

How long does the shared computer token last?

Microsoft states 30 days, and that Microsoft 365 Apps attempts renewal automatically as the expiry approaches while the user is signed in and using the applications. The period is set by Microsoft and is not configurable on the host.

Can users work offline?

Within the life of the current licence or token, yes. Shared computer activation in particular assumes the user is online often enough to renew – reasonable on a session host, poor on a laptop that spends weeks off the network.

Will clearing the licence state lose the user’s settings?

No. It removes licensing state only. Documents, mail profiles and application settings live elsewhere and are untouched. The user will have to sign in again, including any multi-factor step.

Do I have to buy anything to clear this?

Not if the subscription is live and the seat is still assigned – that case is a repair or a network fix and costs nothing. If the subscription has actually lapsed, no configuration change substitutes for reactivating it.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix Office 1058-13: the Click-to-Run service refuses to start on this PC License Error Office 0xC004F038: your KMS count is below the minimum of five clients License Error Office 0x4004F00C: Office is unlicensed and running on a grace period Free Fix Office for Mac 0xD000000C: the keychain cannot store the sign-in
โ† Back to Knowledge Base