Error Details
| Fact | Value | Source | Note |
|---|
| Exact error string | We couldn't activate Office. Error code: 0-1011 (17) | Office activation dialog and ribbon banner | -> |
| OS build range | Windows 10 / Windows 11 | Microsoft 365 Apps documentation | -> |
| Registry key for TenantId | HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration | Windows Registry | -> Verify matches organization's tenant GUID. |
| Log file signature | HRESULT 0x8004E107 or 0x803D0013 | C:\Users\%USERNAME%\AppData\Local\Temp\OfficeSvcMgrLogs\OfficeSvcMgr.log | -> Indicates license token failure. |
| Event ID for license validation failure | 8198 | Windows Logs > Application (OSPPSVC logs) | -> Confirms activation issue. |
Log Files to Check
C:\Users\%USERNAME%\AppData\Local\Temp\OfficeSvcMgrLogs\OfficeSvcMgr.logWindows Logs > Application (Event ID 8198)
What This Error Actually Means
The error code 0-1011 (17) indicates that the Microsoft Office Software Protection Platform (OSPPSVC) service failed to validate a valid license token for the current user session. This error is raised by the Office client's activation mechanism when it cannot find or validate a proper Microsoft 365 Apps subscription tied to the logged-in user account. The OSPPSVC logs in Event Viewer will show this failure with specific Event ID 8198, and the OfficeSvcMgr.log file will contain HRESULT codes such as
0x8004E107 or
0x803D0013, which are direct indicators of license validation failures.
Affected Versions and Scope
This error affects Windows 10 and Windows 11 operating systems running Microsoft 365 Apps (formerly Office 365) in Click-to-Run deployments. It is particularly common in environments where:
- Users are licensed via Microsoft Entra ID (Azure AD) but have not properly signed into Office with their work or school account.
- The Office installation tenant ID (
TenantId registry key) does not match the user's Microsoft 365 tenant.
- Shared Computer Activation (SCA) is required but not configured on Remote Desktop Services (RDS) or Azure Virtual Desktop (AVD) hosts.
Where To Look First: Logs and Event IDs
1. **Event Viewer**: Filter for events from the Office Software Protection Platform Service provider with Event ID 8198 (
Get-WinEvent -FilterHashtable @{LogName='Application'; ProviderName='Office Software Protection Platform Service'} | Where-Object {$_.Id -eq 8198}). This event contains detailed information about the license validation failure.
2. **OfficeSvcMgr.log**: Located at
C:\Users\%USERNAME%\AppData\Local\Temp\OfficeSvcMgrLogs\OfficeSvcMgr.log. Search for lines containing
HRESULT 0x8004E107 or
HRESULT 0x803D0013.
3. **Registry**: Check the tenant configuration at
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration. Look for mismatches between the installed
TenantId and the user's Microsoft Entra tenant ID.
Root Causes
1. User License Expired or Unassigned
The most common cause is a missing or expired Microsoft 365 Apps license for the user account. This can be verified by checking the Microsoft 365 admin center under
Users > Active users > [User] > Licenses and apps.
2. Incorrect Account Signed In
The Office application is signed into a personal Microsoft account instead of the work or school account tied to the Microsoft 365 license. This can be diagnosed by examining the
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Common\Identity\Adal registry key for cached identities.
3. Tenant ID Mismatch
The Office installation's tenant ID (
TenantId in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration) does not match the user's Microsoft Entra tenant ID. This mismatch prevents proper license validation.
4. Corrupted License Token Cache
The OSPPSVC service may have cached invalid or expired license tokens, preventing successful re-activation. This can be identified by examining the
ospp.vbs /dstatus output for stale product keys.
Fix Procedure
- Verify User License in Microsoft 365 Admin Center:
- Navigate to
Microsoft 365 admin center > Users > Active users.
- Select the affected user and check the
Licenses and apps tab.
- If no Microsoft 365 Apps license is assigned, click
Add licenses and select a valid plan.
- Clear ADAL Identity Cache:
Warning: This step will remove all cached identities. Ensure users have their credentials ready.
Remove-Item 'HKCU:\SOFTWARE\Microsoft\Office\16.0\Common\Identity' -Recurse -Force
- Run Office Support and Recovery Assistant (SaRA):
- Download SaRA from aka.ms/SaRA-OfficeActivation.
- Run the tool to analyze
C:\Users\%USERNAME%\AppData\Local\Temp\OfficeSvcMgrLogs\OfficeSvcMgr.log.
- Remove Stale Product Keys:
- Open an elevated command prompt.
- Run
cscript.exe 'C:\Program Files\Microsoft Office\Office16\ospp.vbs' /dstatus to list installed keys.
- Remove each stale key using
cscript.exe 'C:\Program Files\Microsoft Office\Office16\ospp.vbs' /unpkey:.
- Perform Online Repair:
- Open Settings > Apps > Microsoft 365 Apps.
- Select
Modify and choose Online Repair.
- After repair, verify the
TenantId in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration.
Error Code Variants
| Error Code | Description |
| 0-1011 (17) | Licensing token validation failure due to missing or invalid license. |
| 0-1024 (18) | Network connectivity issues preventing activation. |
| 0-1035 (27) | Invalid product key format during manual activation. |
Verification
After applying fixes:
- Open Microsoft Word and check the
File > Account page for "Product Activated" status.
- Verify no new Event ID 8198 entries appear in Event Viewer.
- Confirm the correct
TenantId persists in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration.
Prevention
Implement these measures to avoid recurrence:
1. Use Intune policies to enforce automatic updates for Microsoft 365 Apps.
2. Monitor Microsoft Entra ID tenant configurations to prevent accidental tenant mismatches.
3. Ensure Shared Computer Activation is properly configured on RDS/AVD hosts with
SharedComputerLicensing set to
1.
4. Regularly audit user licenses in the Microsoft 365 admin center.
Tip: Use the following PowerShell script to quickly check tenant alignment:
$installedTenant = (Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration').TenantId
$entraTenant = "your-tenant-id-here"
if ($installedTenant -ne $entraTenant) {
Write-Host "Mismatch detected!" -ForegroundColor Red
}