If Word or another Microsoft 365 app reports error 0x800004005, first copy the code exactly as displayed. Microsoft documents a closely related 0x8004005 shared-computer license error; the extra zero means you should not assume the two messages are identical. In either case, the usual issue is that Office cannot obtain or verify the licensing token required by the signed-in user. Confirm that the account has an eligible desktop-app subscription, shared-computer activation is enabled, the computer can reach Microsoft’s licensing service, and then reset stale activation data if necessary.
What Office error 0x800004005 means
On a shared Windows computer, Microsoft 365 Apps does not rely on one permanent activation for every person. Each user signs in with a licensed account and receives a licensing token from the Office Licensing Service. Office uses that token to determine whether the user may run the desktop applications. The token must be obtained and renewed over a reliable internet connection.
As an Amazon Associate I earn from qualifying purchases.
When Word says, Sorry, we cannot verify the license currently installed for this product.
, Microsoft describes the condition as a problem with the user’s licensing token on the shared computer. A missing token, an expired or corrupted token, an account signed in to the wrong tenant, a blocked connection, or a subscription that does not include shared-computer activation can all produce a similar result.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Do not confuse the two code strings
| Code shown in the dialog | What is established | How to handle it |
|---|---|---|
| 0x800004005 | This exact spelling appears in a Microsoft-hosted question about Word/Microsoft 365 sign-in and licensing on a shared computer. It is not formally indexed in Microsoft’s main shared-computer article. | Record every character, the app, Windows version, device type, and signed-in account before troubleshooting. |
| 0x8004005 | Microsoft’s shared-computer troubleshooting material documents this closely related code as a license-verification failure. | Follow the shared-activation and token steps below, while still verifying the exact code on your own screen. |
The practical diagnosis is therefore not “repair a random hexadecimal error.” It is to establish whether the user is entitled to shared activation and whether Office can retrieve and use that entitlement.
#1 Best Overall
Record the context before changing anything
Write down the complete message or take a screenshot. Also record:
- The exact code, including the number of zeros.
- The Office application that displays it, such as Word, Excel, or Outlook.
- The Windows edition and version.
- Whether the computer is a normal shared PC, Remote Desktop Services (RDS), a virtual desktop (VDI), Citrix, or an environment using FSLogix profiles.
- The account currently shown under Office’s account page and the organization or tenant to which that account belongs.
- Whether other users on the same computer can activate Office.
This information separates a user-specific token problem from a deployment-wide configuration or subscription problem. Do not delete registry keys or licensing files before collecting it.
Step 1: Verify the account and Microsoft 365 entitlement
Sign in with the licensed account
- Close every Office application.
- Open Word again and choose Sign in if prompted.
- Use the work, school, or personal account that owns the Microsoft 365 Apps license, or the account to which an administrator assigned it.
- If more than one account is listed, sign out of accounts that do not contain the desktop-app entitlement, then restart Word and sign in with the correct one.
A successful web sign-in does not by itself prove that the account has a desktop-app license. The subscription must include the installed Microsoft 365 desktop applications and must permit shared-computer activation.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Check whether the plan supports shared-computer activation
Ask the Microsoft 365 administrator to confirm the assigned plan and its service entitlements. Shared-computer activation is a licensing and deployment feature, not a setting that can create eligibility where none exists. If the plan lacks desktop Apps or does not support shared activation, Office cannot obtain the required token on that computer. The remedy is an eligible plan or a different deployment model, not a registry hack.
For an organization, verify that the user is assigned the license in the correct tenant and that the assignment has not expired, been removed, or been replaced by a plan without desktop Apps. If the subscription is inactive, restore it through the organization’s normal licensing process before attempting resets.
Rank #2
Step 2: Confirm that shared-computer activation is enabled
Check in Word
- Open Word.
- Go to File > Account.
- Select About Word.
- Look for the text Shared Computer Activation.
If that wording is absent on a computer intended for shared use, the installed Click-to-Run configuration may not have been deployed for shared activation. An administrator should review the Office deployment configuration rather than repeatedly signing users in.
Check the Click-to-Run registry value
Administrators can inspect the following key:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftOfficeClickToRunConfigurationThe SharedComputerLicensing value should be set to 1 for shared-computer activation. Use Registry Editor only if you understand the deployment policy and have administrative permission. A value change alone does not provide a license; it must match an eligible subscription and a correctly deployed Office build.
On 64-bit Windows, the path shown above is the standard Click-to-Run configuration location. If your organization manages Office with policy or deployment tooling, that tooling may overwrite manual edits. Have the administrator correct the source configuration instead of changing the value repeatedly.
Step 3: Remove common activation conditions that block token issuance
Check date, time, and time zone
Windows must have the correct date, time, and time zone for authentication and token validation. Open Settings > Time & language > Date & time, enable automatic time setting where appropriate, choose the correct time zone, and select Sync now. Restart Word after the clock is corrected.
Test the network path
Sign-in and token renewal require reliable access to Microsoft’s Office licensing services. Temporarily move the computer to a known-working network if permitted by your organization. Check whether a proxy, firewall, content filter, VPN, or endpoint security policy blocks Office authentication. Corporate administrators should review proxy authentication and allow the Microsoft 365 endpoints required by their tenant. Do not disable security controls permanently; use the organization’s approved exception process.
Install Office and Windows updates
- In Word, open File > Account.
- Choose Update Options > Update Now, if that control is available.
- Install pending Windows updates through Settings > Windows Update.
- Restart Windows and test activation again.
Older Click-to-Run builds can contain activation defects that have already been corrected in later updates. If an administrator controls updates, ask which Office channel and build the computer is receiving.
Look for duplicate Office installations
Open Settings > Apps > Installed apps (or Apps & features on an older Windows version) and look for multiple Microsoft 365 or Office installations. Microsoft recommends removing the unused or conflicting copy. Keep the installation managed by your organization, and restart Windows after an uninstall before testing the remaining copy.
Try an elevated launch only as a diagnostic
Right-click Word and choose Run as administrator once to determine whether permissions are preventing activation data from being written. If activation works only when elevated, the underlying user-profile or policy permissions need correction; running Office permanently as administrator is not a proper shared-computer solution.
Step 4: Check whether a licensing token was created
On a shared computer, successful activation creates licensing files under:
%localappdata%MicrosoftOffice16.0LicensingThe folder is inside the profile of the user who activated Office, so another user’s profile may contain different files. The presence of files is not proof that the token is valid, and an empty folder does not identify the cause by itself. Do not edit, rename, or delete individual licensing files manually. Manual changes can leave the profile in a less predictable state and can interfere with the supported cleanup tools.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsIf one user can activate while another receives the error, compare the accounts, license assignments, profile location, and network conditions rather than changing the computer-wide registry first. In RDS, VDI, Citrix, or FSLogix environments, profile persistence and container permissions can determine whether a token survives sign-out.
Step 5: Reset stale activation data with Microsoft’s supported tools
Use the guided reset for one computer
Microsoft provides a Get Help or Support and Recovery Assistant scenario for resetting Office activation. Start the Microsoft support utility on the affected Windows profile, choose the Office activation or licensing problem, and follow its prompts. The guided process removes old account and license information so Office can request a fresh token. Close all Office applications when the utility asks you to do so, and restart Windows when it completes.
Use the reset after confirming the account and plan. A cleanup cannot manufacture an entitlement, and repeatedly running it will not solve a plan that does not support shared activation.
Use OLicenseCleanup for managed deployments
For enterprise computers, Microsoft documents an OLicenseCleanup process and related account-cleanup scripts. These procedures remove old Office licenses and cached account information across a deployment so users can authenticate again. They require elevated permissions and should be run only by an administrator following Microsoft’s current script instructions for the organization’s Office version and deployment type.
Before a scripted cleanup, identify which profiles and devices are in scope, close Office processes, and confirm that users know they will need to sign in again. Test the procedure on one representative computer before applying it broadly. In a nonpersistent virtual desktop, coordinate the cleanup with the image and profile-management workflow; otherwise, the old state may return at the next reset.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Step 6: Sign in again and request a fresh token
- Restart Windows after the guided or administrative cleanup.
- Open Word from the affected user profile.
- Sign in with the account that has the eligible Microsoft 365 Apps license.
- Wait for activation to complete while the computer has a reliable internet connection.
- Open File > Account > About Word and confirm that Shared Computer Activation appears when the device is configured for that mode.
- Create a test document, save it, close Word, and reopen it to verify that the token remains usable after a normal restart.
If the same account fails on several shared computers, the administrator should investigate the license assignment, tenant policy, and service health rather than repeating local cleanup on each device.
When the subscription is the blocker
If the assigned plan does not support shared-computer activation, there is no local repair that can make it eligible. The organization must obtain a Microsoft 365 Apps plan that includes the required entitlement, or deploy Office under a licensing model intended for a single-user computer. The choice depends on how the device is used, whether several people sign in, and whether the organization requires RDS, VDI, Citrix, or FSLogix support.
Do not use cracks, activators, unofficial license bypasses, or registry cleaners. They cannot provide a legitimate Office entitlement, can damage the installation, and can expose business credentials or documents.
Choose the remedy by symptom and environment
| Observed situation | Most likely area | Next action |
|---|---|---|
| Only one user fails; other users activate normally. | Wrong account, missing assignment, or a stale profile token. | Confirm the account’s desktop-app license, run the guided activation reset for that profile, and sign in again. |
| Every user fails on one shared computer. | Shared activation configuration, network access, duplicate installation, or computer-wide policy. | Check the Word account page, the SharedComputerLicensing registry value, updates, proxy/firewall rules, and installed Office copies. |
| Users fail on many computers. | Tenant licensing, deployment configuration, or service connectivity. | Have the Microsoft 365 administrator verify plan eligibility, deployment settings, and service status. |
| Activation works until the user signs out or the virtual desktop resets. | Profile persistence or token storage in RDS, VDI, Citrix, or FSLogix. | Review the profile/container design and apply Microsoft’s shared-activation guidance for that platform. |
| The dialog shows 0x800004005, but documentation mentions 0x8004005. | Code transcription or a related licensing condition. | Copy the exact dialog text and troubleshoot entitlement and token issuance without assuming the codes are interchangeable. |
What to do if the error remains
- Verify once more that the subscription includes desktop Microsoft 365 Apps and shared-computer activation.
- Confirm the account is assigned in the correct organization and that the subscription is active.
- Check that Office reports shared activation and that
SharedComputerLicensingis set to1where the deployment requires it. - Correct Windows time, install Office updates, and test an unrestricted approved network path.
- Remove an unused duplicate Office installation.
- Run the supported Get Help or Support and Recovery Assistant reset, or have an administrator perform the documented OLicenseCleanup process.
- Capture the exact code, account, Office build, Windows version, device type, and results of each step before contacting the organization’s Microsoft 365 administrator or Microsoft Support.
Escalation is appropriate when an eligible plan still cannot obtain a token after connectivity, sign-in, configuration, and cleanup checks. The administrator can then distinguish a tenant entitlement issue from a local profile or deployment fault.
Quick Recap
As an optional shortcut after the manual checks, Outbyte PC Repair can address more than 100 common Windows issues, including broken system elements, invalid redirects, shared DLL problems, cleanup tasks, and app-crash logging. It runs on Windows 11, 10, 8, and 7 and offers a category-based free trial of at least two days before a subscription. Results vary; it complements antivirus software, does not replace it, and no tool repairs every crash or supplies a missing Microsoft 365 entitlement.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
