Microsoft Pauses KB5002907 After Office 2016 and 2019 Licensing Failures
Microsoft has paused the rollout of KB5002907 after reports that some Windows devices running Office 2016 or Office 2019 were left with an unlicensed product or, in rarer cases, without a working Office installation. Microsoft's support bulletin now directs affected users to reactivate their purchased Office product when licensing was lost, or reinstall the purchased Office release when it was removed.
KB5002907 is an optional Microsoft 365 Apps repair update delivered through Windows Update. Its intended target is narrower than the affected Office reports: Windows PCs running Microsoft 365 Apps on Current Channel or Monthly Enterprise Channel where the installation is more than 90 days out of date or has stopped updating normally. Microsoft classifies it as a Microsoft 365 Apps update delivered through Windows Update and has paused its rollout to prevent additional devices from being affected.
The incident matters most to administrators with mixed or older Office estates. Office 2016 and Office 2019 are specifically named in Microsoft's incident notice, while the normal KB eligibility rules target stale Microsoft 365 Apps installations. Administrators should distinguish those two populations when checking affected machines and deciding what recovery action is required.
What Microsoft says went wrong
Microsoft says KB5002907 was intended to repair devices that were no longer receiving Microsoft 365 Apps updates. The repair action left some devices without functioning Microsoft 365 Apps or Office installations.
Microsoft documents two observed outcomes:
| Observed state | Microsoft recovery guidance |
|---|---|
| Purchased Office appears unlicensed | Reactivate the purchased Office product |
| Purchased Office was removed | Download and reinstall the purchased Office version |
Microsoft describes removal as a rare case. Its current support page has not yet published a root-cause analysis for why Office 2016 or Office 2019 installations were affected.
Independent reporting from BleepingComputer documented administrator reports of Office 2016 and Office 2019 Home & Business perpetual installations becoming unlicensed, with some systems losing Office entirely. Microsoft subsequently confirmed the pause and added the incident notice to its KB5002907 documentation.
Which systems KB5002907 was designed for
Microsoft's eligibility conditions are specific. The optional update is intended for Windows PCs where Microsoft 365 Apps:
- is more than 90 days out of date or has stopped updating normally;
- uses Current Channel or Monthly Enterprise Channel; and
- receives applicable Microsoft-product updates through Windows Update.
The support page lists Windows 11 23H2, 24H2, 25H2 and 26H1, Windows 10 22H2, Windows Server 2019, Windows Server 2022 and Windows Server 2025 in its Applies To section.
Microsoft says installations on other Microsoft 365 Apps update channels are outside the update's scope. Devices whose Microsoft 365 Apps updates are managed through Group Policy or Cloud Update receive no changes from KB5002907 under the documented behavior.
The update also leaves the device's assigned Microsoft 365 Apps channel unchanged. On an eligible machine, its purpose is to restart the Microsoft 365 Apps update process and move the installation toward a current build for the already assigned channel.
What administrators should do now
The rollout is paused. The immediate task is identifying machines that received KB5002907 and checking Office health before making further deployment changes.
For machines with Office 2016 or Office 2019, verify that Word, Excel and other installed Office applications still launch and report an activated product under the account/licensing view. If the product reports an unlicensed state, Microsoft's supported response is to reactivate the purchased product.
If Office has been removed, Microsoft directs users to its Office download and reinstall workflow for the purchased Office release. Preserve licensing and deployment records before rebuilding managed machines so the restored installation matches the organization's entitlement and architecture.
For stale Microsoft 365 Apps installations that never received KB5002907, use the organization's normal update-management path while Microsoft investigates. Microsoft's support page also recommends checking connectivity and free disk space, restarting the device, and using File > Account > Update Options > Update Now where that option is available.
Optional update and field reports about installation
Microsoft's current documentation classifies KB5002907 as optional and says users choose it when it appears among optional updates for other Microsoft products.
BleepingComputer reported administrator observations that the package appeared to install automatically on some affected customer systems. That conflicts with the documented delivery behavior and remains field reporting rather than a confirmed change to Microsoft's servicing rules. The operational priority is checking systems that actually received the package and validating their Office state.
Why mixed Office estates deserve attention
The incident exposes a servicing boundary that can be easy to miss in long-lived Windows environments. A machine may have Microsoft 365-related components, perpetual Office software, Access Runtime, add-ins or other Office-era dependencies accumulated across several deployment cycles.
BleepingComputer reported one administrator's hypothesis that mixed 32-bit and 64-bit Office components contributed to failed reinstall behavior on some machines. Microsoft has not confirmed that explanation. Administrators can still use architecture and installed-product inventory as useful incident-triage data while the root cause remains under investigation.
For managed fleets, record at least the Office product, version, activation state, update channel, architecture and KB5002907 presence on affected endpoints. That creates a clean comparison set if Microsoft publishes a more detailed root-cause or remediation update.
Bottom line
KB5002907 was designed as an optional repair path for Microsoft 365 Apps installations more than 90 days out of date on Current Channel or Monthly Enterprise Channel. Microsoft paused the rollout after some Office 2016 and Office 2019 devices lost licensing or a working Office installation.
Affected systems should follow Microsoft's documented recovery split: reactivate purchased Office when it is unlicensed, or reinstall the purchased release when it was removed. Administrators should keep broader deployment changes on hold until Microsoft updates the support bulletin with the results of its investigation.
Sources
- Microsoft Support — KB5002907: Optional update for out-of-date Microsoft 365 Apps installations: https://support.microsoft.com/en-us/servicing/os/microsoft-365/kb5002907-optional-update-for-out-of-date-microsoft-365-apps-installations
- Microsoft Support — Activate Office for Windows: https://support.microsoft.com/en-us/microsoft-365-activation-licensing/office-install/activate-office-for-windows
- Microsoft Support — Download and install or reinstall Office 2021, Office 2019, or Office 2016: https://support.microsoft.com/en-us/office/lifecycle/officeinstall/download-and-install-or-reinstall-office-2021-office-2019-or-office-2016
- BleepingComputer — Microsoft pauses KB5002907 update after Office license deactivations: https://www.bleepingcomputer.com/news/microsoft/microsoft-365-kb5002907-update-paused-after-office-license-deactivations/