Microsoft paused KB5002907 after some Office 2016 and 2019 installs lost their licence
The optional repair was meant for Microsoft 365 Apps more than 90 days behind. Microsoft says some perpetual Office installations became unlicensed and, in rare cases, were removed.
By Parminder Kumar Sharma · · 4 min read
A repair for stale Microsoft 365 Apps crossed into perpetual Office
Microsoft has paused the rollout of optional update KB5002907 while it investigates unexpected results on some devices running Office 2016 or Office 2019. The company says affected installations could appear unlicensed. In rare cases, the Office product was removed and needs to be reinstalled.
That was not the update's stated target. KB5002907 was designed to restart the update process for Microsoft 365 Apps installations that were more than 90 days out of date on the Current Channel or Monthly Enterprise Channel. It was offered through Windows Update as an optional update for other Microsoft products.
The eligibility conditions were narrow before the pause
What Microsoft says about the intended scope
| Condition | In the intended scope? | Explanation |
|---|---|---|
| Microsoft 365 Apps on Windows | Only when eligible | Installation had to be more than 90 days out of date |
| Current Channel | Yes | One of the two supported update channels |
| Monthly Enterprise Channel | Yes | The other supported update channel |
| Other Microsoft 365 Apps channels | No | Microsoft says the update does not apply |
| Updates managed by Group Policy or Cloud Update | No action | Microsoft says KB5002907 makes no changes |
| Microsoft 365 Apps on macOS or other operating systems | No | The package applies to Windows PCs |
| Office 2016 or Office 2019 | Not the intended repair target | These are the installations named in the incident notice |
The distinction between delivery and product target matters. The package appeared in Windows Update, but Microsoft states that it was an update for Microsoft 365 Apps rather than a Windows operating-system update. It did not install automatically and was meant to leave the assigned Microsoft 365 update channel unchanged.
On an eligible device, the repair starts the Microsoft 365 Apps update process and attempts to move the installation to a current build for its existing channel. The incident shows why detection based only on the distribution mechanism can be misleading: the package arrived through Windows Update, but its actions were inside the Office servicing path.
The recovery path depends on whether Office is present
Microsoft's two published recovery cases
| Observed result | Microsoft's resolution | Evidence to preserve |
|---|---|---|
| Office remains installed but appears unlicensed | Reactivate the purchased product | Installed edition, licence account or key, update history and the time activation failed |
| Office was removed | Download and reinstall the purchased Office 2016 or 2019 product | Update history, application inventory and any installer or servicing logs available |
A missing shortcut is not enough to decide which case applies. Confirm whether the Office binaries and installed-product records remain on the device. If the applications launch but show activation failure, preserve the licence and account information before making broad changes. If the product has been removed, use the organisation's known installation media or Microsoft's reinstall route for the purchased edition.
For managed estates, build the affected list from update history plus Office inventory. A user report can reveal the incident, but a fleet query is faster than waiting for every device owner to open Word and discover the same problem.
Administrators should separate exposure, symptom and recovery
Take this with you
Practical response sequence
- Identify devices that installed KB5002907 and record the installation time
- Inventory Microsoft 365 Apps, Office 2016 and Office 2019 separately
- Check whether Word, Excel and the installed-product records are still present
- Record licence or activation errors before reactivation or reinstall changes the evidence
- Reactivate installed products or reinstall removed products using Microsoft's current guidance
- Do not assume Group Policy or Cloud Update managed devices changed, but verify the local update history
- Pause internal deployment guidance that recommends KB5002907 while Microsoft's rollout remains paused
Optional repairs need the same change discipline as normal patches
KB5002907 was intended to fix a servicing failure, which can make it feel lower risk than a feature update. In practice, a repair package can change product state and licensing just as directly as a conventional software deployment.
The useful control is a staged ring with inventory checks before and after installation. Confirm the edition, channel, update-management method, build and activation state on a small set of representative devices. A successful install event does not establish that the applications remain licensed and usable.
Microsoft's pause limits further exposure. The remaining task for administrators is to find devices that already received the update, distinguish the two failure modes and document the recovery applied to each one.
Sources
- PrimaryKB5002907: Optional update for out-of-date Microsoft 365 Apps installationsMicrosoft Supportaccessed 2026-09-27
