Fix it now
Microsoft documents 0x8004FC12 as an Office activation failure seen after upgrading Windows, showing “something went wrong and we can’t do this for you right now”. The published fix is to bring Windows fully up to date; where that is not possible immediately, three specific commands are the documented workaround.
net localgroup Administrators localservice /add
fsutil resource setautoreset true C:\
netsh int ip reset resetlog.txt
- Try the supported fix first: install all available Windows updates and restart, then attempt activation again. Microsoft gives that as the primary solution.
- If updating is not possible today, run the three commands above in order from an elevated Command Prompt.
- Reboot the device, then open an Office application and let it activate.
- Once activation succeeds and Windows has been updated, remove the temporary group membership:
net localgroup Administrators localservice /delete. - If the machine is a Remote Desktop or virtual desktop host, read the shared computer activation section below before applying any of this – the documented failures there carry different messages and different fixes.
Adding LOCAL SERVICE to the local Administrators group raises the privilege of a low-privilege service account. It is Microsoft’s published workaround for this specific error, not a configuration to leave in place; reverse it once Windows is current.
If Office activates after the reboot you can stop here. If it does not, the next section explains what is documented for this code and what is not.
Why it happens
Start with what Microsoft actually publishes, because this code has attracted a great deal of confident writing that the vendor does not support. There is one Microsoft page for 0x8004FC12. It describes the error as appearing when activating Office after upgrading to Windows 10, quotes the message as “We’re sorry, something went wrong and we can’t do this for you right now. Please try again later. (0x8004FC12)”, and gives two solutions: update Windows to the latest version, or, if that is not immediately possible, run three commands and reboot.
Those three commands are worth reading rather than pasting blindly, because each one touches something different and only one is about Office at all. net localgroup Administrators localservice /add puts the LOCAL SERVICE account into the local Administrators group. fsutil resource setautoreset true C:\ tells the transactional resource manager on the system volume to reset its log at the next mount. netsh int ip reset resetlog.txt rebuilds the TCP/IP stack configuration. That is a set of workarounds for a machine left in an odd state by an upgrade, not a licensing repair.
What is not documented matters just as much here. Neither of Microsoft’s shared computer activation troubleshooting pages lists 0x8004FC12, and the shared computer failures that are documented carry their own messages: “The products we found in your account cannot be used to activate Office in shared computer scenarios”, “Sorry, we cannot verify the license currently installed for this product”, “Sorry, this Microsoft 365 account has recently been used to activate too many computers”, and the UNLICENSED PRODUCT notice. If you are on a session host and seeing one of those, this code is not your lead.
Of the codes seen alongside, only one has a published meaning. 0x80070520 is ERROR_NO_SUCH_LOGON_SESSION – a specified logon session does not exist, it may already have been terminated – which is exactly what you would expect when a credential context is torn down under a running session. 0xC004F025, 0x8004E102 and 0x8004E104 are not in Microsoft’s published tables at all.
Windows is behind after an upgrade
You have this one if The failure began after a Windows feature update or an in-place upgrade, and the machine has updates outstanding.
- Open Settings, then Windows Update, and install everything offered, including optional quality updates if they are relevant.
- Restart and try activating again before changing anything else.
- This is Microsoft’s primary published solution; the command workaround exists for machines that cannot be updated straight away.
The machine is in the state the workaround addresses
You have this one if Windows cannot be updated today, and activation still fails after a restart.
- Run the three documented commands from an elevated prompt, in the order Microsoft gives them.
- Reboot, then activate.
- Remove LOCAL SERVICE from the Administrators group once the machine is current and activation holds.
Treat this as a bridge to a patched machine rather than a destination. A service account sitting in Administrators is exactly the sort of thing that gets found in an audit two years later with nobody able to say why.
The logon session behind the request has gone
You have this one if 0x80070520 appears with it, typically on a session host or a machine where the profile or credential context was reset under a live session.
- Have the user sign out of Windows completely – not just close Office – and sign back in so a fresh session is created.
- Open Word and let it activate before opening anything else.
- If it recurs at every logon, look at what is resetting the profile: a non-persistent pool, a mandatory profile, or a container that attaches late.
It is actually a shared computer activation problem
You have this one if The machine is an RDS or VDI host and the on-screen message is one of the documented shared computer ones rather than the generic “something went wrong”.
- Confirm the host is in shared mode:
reg query HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration /v SharedComputerLicensingshould return 1. - Read the on-screen message rather than the code, and match it to the documented list in the reference section below.
- Confirm the user holds a plan that carries shared computer activation before assuming anything about the host.
Full reference
What each command in the workaround does
| Command | What it changes |
|---|---|
net localgroup Administrators localservice /add |
Adds the LOCAL SERVICE account to the local Administrators group |
fsutil resource setautoreset true C:\ |
Sets the transactional resource manager on the system volume to reset its log at the next mount |
netsh int ip reset resetlog.txt |
Resets the TCP/IP stack configuration, logging what it did to resetlog.txt |
net localgroup Administrators localservice /delete |
Reverses the first command once the machine is patched |
The first command grants administrative rights to a service account. Microsoft publishes it as a workaround for this error on a machine that cannot yet be updated. Do not deploy it across an estate, do not leave it in place, and record it wherever you record temporary privilege changes.
Shared computer activation, and the messages that really belong to it
| On-screen message | What Microsoft documents |
|---|---|
| The products we found in your account cannot be used to activate Office in shared computer scenarios | The user’s plan does not include shared computer activation. Ask an administrator for a Microsoft 365 Apps for enterprise licence |
| Sorry, we cannot verify the license currently installed for this product | A problem with the user’s licensing token. Sign in to Office again to obtain a new one |
| Sorry, this Microsoft 365 account has recently been used to activate too many computers | The account has passed Microsoft’s limit for a time period. Wait 24 hours or use a different licensed account |
| UNLICENSED PRODUCT: most features are turned off because a shared computer license isn’t available | No token was obtained. Check the licence assignment, the sign-in and the internet connection |
| Your shared computer license expires on (date) and we’re having trouble renewing it | Automatic renewal failed, most often because the machine was offline. Select Renew, or restore connectivity |
Where the shared computer pieces live
| Item | Value |
|---|---|
| Registry key | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration |
| Value | SharedComputerLicensing, a String (REG_SZ) set to 1 |
| Token location | %localappdata%\Microsoft\Office\16.0\Licensing |
| Subscription licence location | %localappdata%\Microsoft\Office\Licenses |
| Token lifetime | 30 days, renewed automatically as expiry approaches while the user is signed in and online |
Those two folders are not the same thing and the distinction saves time. The 16.0\Licensing folder holds the shared computer activation token. The Office\Licenses folder holds the ordinary subscription licence file, whose ID begins EWW. A host in shared mode uses the first; a normal desktop uses the second.
If you are on a session host and want to be thorough
- Confirm the registry value is present and set to 1, and that Office was restarted afterwards – it reads the setting at start-up.
- Confirm the user’s plan carries shared computer activation. Microsoft documents it for any plan including Microsoft 365 Apps for enterprise, for the desktop Project and Visio plans, for the education plans that include Apps for enterprise, and for Microsoft 365 Business Premium – which is the one business-tier plan that has it.
- Confirm the host can reach the sign-in and licensing services. A token that cannot be fetched fails identically to one that cannot be written.
- Check whether a profile container is excluding or including the Office activation folders in a way that loses the token between sessions.
- Only then look at the profile itself.
The undocumented companions
0xC004F025, 0x8004E102 and 0x8004E104 all appear in reports of this error and none of them is published. There is no vendor text to quote and no meaning to give you. Treat them as additional failures raised in the same exchange, diagnose from the documented codes and the on-screen message, and be wary of any page that hands you a definition for them – it will have been written to make somebody’s explanation work.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0x8004FC12 |
Microsoft documents this as an Office activation failure after upgrading Windows, with the message “something went wrong and we can’t do this for you right now”. Fixed by updating Windows, or by the three published commands | Microsoft Support |
0x80070520 |
ERROR_NO_SUCH_LOGON_SESSION: a specified logon session does not exist, it may already have been terminated | Microsoft Learn |
0xC004F025 |
A licensing-service failure raised in the same exchange. Not in Microsoft’s published Office activation tables | not published by the vendor |
0x8004E102 |
Seen alongside during activation. Microsoft publishes no meaning for it | not published by the vendor |
0x8004E104 |
Seen alongside during activation. Microsoft publishes no meaning for it | not published by the vendor |
Confirm the fix worked
- Open Word and confirm File, then Account shows the product as activated with no prompt.
- Confirm Windows Update reports the machine as up to date and nothing is waiting on a restart.
- Confirm LOCAL SERVICE is no longer in the local Administrators group if you used the workaround:
net localgroup Administrators. - On a shared host, confirm a token exists under
%localappdata%\Microsoft\Office\16.0\Licensingfor the affected user. - Sign out and back in, then open Excel, to prove activation survives a new session.
Questions people ask about this
Is 0x8004FC12 a shared computer activation error?
Not according to Microsoft. The only page it publishes for this code describes an activation failure after upgrading Windows. Its shared computer activation troubleshooting pages do not list this code at all, and the shared computer failures they do document carry their own distinct messages.
Is adding LOCAL SERVICE to Administrators safe?
It is Microsoft’s published workaround for this error on a machine that cannot be updated yet, and it raises the privilege of an account designed to have very little. Use it as a temporary bridge, reverse it with net localgroup Administrators localservice /delete once Windows is current, and do not roll it out across an estate.
Does fixing this need a different licence?
No. Nothing in Microsoft’s documented cause or fix for this code involves entitlement. If the on-screen message says your products cannot be used to activate Office in shared computer scenarios, that is a different, documented condition – and that one is a licence question.
Where is the shared computer licensing token kept?
By default at %localappdata%\Microsoft\Office\16.0\Licensing, and Microsoft states it is valid for 30 days, with Microsoft 365 Apps attempting renewal automatically as the expiry approaches while the user is signed in.
Do I need to reboot after the workaround?
Yes. Microsoft’s instruction is to run the three commands and then reboot before attempting activation again. The IP stack reset in particular does not take effect until the restart.
