Microsoft Halts KB5002907 Rollout After Office License Failures
Microsoft announced today that it is suspending the distribution of the KB5002907 update for Microsoft 365 after a wave of reports indicated that the patch interfered with perpetual licenses for Office 2016 and Office 2019.
The update, released as part of the regular monthly cadence of Microsoft 365 patches, was intended to address a range of security vulnerabilities and performance issues across the suite. It is delivered through the same Windows Update mechanism that many enterprises rely on to keep their software current.
Shortly after deployment began, users of the traditional, non‑subscription versions of Office began posting that the update either deactivated their product keys or, in some cases, caused the applications to disappear entirely from the system. The problem appeared to affect both Office 2016 and Office 2019 installations that were licensed for perpetual use, a model still common in many corporate environments.
For organizations that depend on these perpetual licenses, the unexpected deactivation creates immediate operational challenges. Employees may lose access to core productivity tools, and IT departments must scramble to re‑activate or reinstall software, potentially disrupting normal business workflows.
Microsoft responded by pausing the rollout while it investigates the root cause. In a brief statement, the company said it is working with affected customers to restore functionality and will issue a corrective update once the issue is resolved. The firm also advised administrators to hold off on applying the KB5002907 patch until further notice.
Analysts note that the incident underscores the complexities of maintaining a mixed environment of subscription‑based and perpetual software. Going forward, Microsoft is expected to provide clearer guidance on testing updates in heterogeneous deployments and may adjust its release schedule to prevent similar setbacks. Users are encouraged to monitor official channels for updates on the status of the patch and any recommended remediation steps.
Comments (0)
Be the first to comment.
Join the discussion