Users and administrators are linking Microsoft KB5002907 to incidents in which some perpetual Office 2016 and Office 2019 installations became unlicensed or, in rarer reports, were removed. The cause is not established in Microsoft’s public support article, so the incident should be described as an observed association rather than a proven mechanism.
Microsoft’s KB page says the optional update is meant for Windows PCs running eligible Microsoft 365 Apps that are more than 90 days out of date. It is designed to resume updates on Current Channel or Monthly Enterprise Channel. Microsoft says it does not install automatically and should make no change when Group Policy or Cloud Update manages the device.
Why Microsoft KB5002907 drew complaints
Administrators and users posted reports that Office 2016 or 2019 lost activation soon after the update appeared. A Microsoft Q&A thread contains multiple first-hand accounts, but that forum content is user testimony, not an official engineering conclusion. Born’s IT blog collected similar reports and technical logs, while The Register spoke with an affected reader.
The Register reported that affected users often had to reactivate Office, sometimes repeatedly. Born’s IT published administrator reports and logs describing cases in which components were removed. Those observations are important, but they do not prove that every deactivation had the same cause. Mixed Office components, previous licensing state and device configuration could affect outcomes.
What is verified and what remains open
The verified baseline is narrow. KB5002907 exists, is optional and targets out-of-date Microsoft 365 Apps. Two independent outlets and direct user reports describe closely timed problems affecting perpetual Office versions. Microsoft’s public KB does not identify that issue. The root cause, scale and exact affected configurations remain unresolved in the evidence reviewed.
That distinction protects users from two bad conclusions: assuming every Office activation problem is caused by this update, or dismissing the reports because Microsoft has not published a final root-cause analysis. Enterprise teams need device-level evidence before applying a fleet-wide explanation.
The episode is a useful contrast with planned features such as Microsoft Copilot Home, Code and Autopilot. New automation can move quickly, but servicing systems also need conservative targeting and rollback. The operational discipline resembles security response: our coverage of Apple’s 200-plus flaw patch set and the Gyazo breach both underline the value of a precise inventory.
What IT teams should do now
Administrators should identify machines offered KB5002907, record Office edition, build, bitness and activation state, and preserve logs before making changes. They should avoid treating community workarounds as universal. If a licence is legitimate, use Microsoft’s official activation and reinstall paths or enterprise support.
For managed estates, the incident argues for staged deployment rings even for optional remediation packages. Teams should test perpetual and subscription editions separately, confirm recovery keys and installers are available, and define a stop condition when activation state changes unexpectedly.
The clean conclusion is not that Microsoft intentionally revoked old licences. It is that a narrowly described update coincided with credible disruption reports, and customers need a documented root cause and clear remediation before confidence is restored.
Facts at a glance
| Update | KB5002907, an optional Microsoft 365 Apps remediation update. |
|---|---|
| Intended scope | Windows devices with eligible Microsoft 365 Apps more than 90 days out of date. |
| Reports | Some perpetual Office 2016/2019 installs became unlicensed or were removed. |
| Public status | Microsoft’s support page does not name the reported perpetual-licence issue. |
| Caveat | Cause and affected population remain unconfirmed publicly. |
Frequently asked questions
Is KB5002907 a security update?
No. Microsoft describes it as an optional update to help eligible, out-of-date Microsoft 365 Apps resume updating.
Has Microsoft confirmed the root cause?
Not in the public support text reviewed. Reports say the company is investigating.
What should an affected user do?
Preserve licence records, document the device state and use Microsoft’s official activation or reinstall guidance; managed fleets should contact their administrator.
Reporting date: 2026-09-25. Full claim notes and URLs are preserved in the source ledger.
Get the day’s top stories in your inbox
One concise email. No spam, unsubscribe anytime.
