Microsoft 365 Apps install and activation error codes: a quick reference

Microsoft 365 Apps reports install problems as short Click-to-Run codes such as 30174-4, activation problems as a hex code at the end of a "something went wrong" dialog, and shared computer activation problems as plain-language banners. This quick reference collects the ones Microsoft documents, with the usual cause and the first check, plus the tools that reset a device when a fix doesn't stick.

How to read these codes#

• Click-to-Run install codes are two numbers joined by a hyphen (30174-4), sometimes with a third in brackets (30015-4 (1392)). Read the whole code: Microsoft documents some codes exactly and others by prefix, for example "an error that contains 30068".
• Activation codes appear in brackets after "We're sorry, something went wrong and we can't do this for you right now. Please try again later." The hex value is what you look up.
• Shared computer activation messages appear as banners in the Office app. They only apply when the device really runs in that mode, so confirm it first (see below).
• Office LTSC is different. Volume-licensed Office uses KMS or MAK activation and its own codes, read with ospp.vbs. The callout at the end of the activation section covers it.

Click-to-Run writes its logs to the temp folder of the account that ran setup: %temp% for a user-started install, C:\Windows\Temp when Intune or Configuration Manager runs it as SYSTEM. Open the newest log whose name starts with the computer name and search for the error code.

To confirm shared computer activation, open an Office app and go to File › Account › About: the line under the version shows Shared Computer Activation instead of a Product ID. In the registry, HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration should hold SharedComputerLicensing = 1.

Click-to-Run install errors#

Microsoft's user-facing advice for the network codes includes "try a wired connection" and "install from another location". On managed devices the equivalent is to remove the network from the equation: download the source once with the Office Deployment Tool and install from it.

setup.exe /download configuration.xml
setup.exe /configure configuration.xml

Point the SourcePath in the XML at the downloaded files. If the offline install succeeds, the failure was the path to the Office CDN: check the proxy, TLS inspection and the endpoints in Microsoft 365 URLs and IP address ranges. For deployments through Configuration Manager, see deploying and updating Microsoft 365 Apps with Configuration Manager.

Activation errors#

The title-bar states "Unlicensed Product", "We couldn't find any Office products" and the account and device messages are covered in Microsoft 365 Apps activation errors; this page doesn't repeat them.

Shared computer activation messages#

When activation succeeds in this mode, token files appear in %localappdata%\Microsoft\Office\16.0\Licensing (or in the roaming location you configured). Don't edit them.

Shared computer activation is chosen at install time, for example with <Property Name="SharedComputerLicensing" Value="1" /> in the Office Deployment Tool XML. If About still shows a Product ID, the device uses normal activation and the messages above don't apply: switching a device to the other license mode is one of the cases where Microsoft tells you to reset the activation state first.

Resetting activation when a fix doesn't stick#

For tenant-to-tenant migrations, repurposed devices or a change of license mode, Microsoft documents a clean reset of Microsoft 365 Apps activation. Close all Office apps, then use one of these:

• The Microsoft 365 activation troubleshooter in Get Help, or the Enterprise version of the Microsoft Support and Recovery Assistant.
• OLicenseCleanup.vbs to remove Office licenses and cached accounts. If signoutofwamaccounts.ps1 sits in the same folder, it runs too.
• signoutofwamaccounts.ps1, run elevated, to remove Office tokens and accounts from Web Account Manager on Microsoft Entra joined and hybrid joined devices without touching device SSO.
• WPJCleanUp.cmd to remove Workplace Joined accounts.

How to verify a fix#

1. Install: the apps open, and the Click-to-Run service is running.
   PowerShell

   Get-Service ClickToRunSvc | Select-Object Status, StartType
   Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration' |
       Select-Object VersionToReport, SharedComputerLicensing

2. Updates: File › Account › Update Options › Update Now completes without an error.
3. Activation: the title bar no longer shows Unlicensed Product, and File › Account shows the product with the user's work account.
4. Shared computers: About shows Shared Computer Activation and the licensing token files exist for the user.

References#

• Troubleshoot issues with shared computer activation for Microsoft 365 Apps
• Reset activation state for Microsoft 365 Apps for enterprise
• Troubleshoot volume activation of Office
• Microsoft Support install and activation error pages, linked from each code in the tables