Microsoft Pauses KB5002907 Update After Office License Deactivations

Introduction

Microsoft has paused the rollout of the KB5002907 Microsoft 365 update after users reported that it deactivated — or in some cases completely removed — perpetual Office 2016 and Office 2019 installations.

KB5002907, titled "Optional update for out-of-date Microsoft 365 Apps installations," was released to help users update Microsoft 365 Apps installations that are more than 90 days out of date.

What Happened: Office Installs Deactivated or Removed

Shortly after the update was released, BleepingComputer was told by Christian Van Hautte, who runs an MSP in Belgium, that several of his customers suddenly found their perpetual Office installations showing as an "Unlicensed Product."

Van Hautte said re-entering the original Office product key restored activation on affected systems.

Furthermore, Van Hautte warned that even though the update is listed as optional, it installed automatically on his customers' devices.

Who Is Affected

Product	License Type	Impact
Office 2016	Perpetual / one-time purchase	Deactivated or removed
Office 2019	Perpetual / one-time purchase	Deactivated or removed
Office 2016 / 2019 Home & Business	Perpetual / one-time purchase	Deactivated or removed

Reports from other administrators and users began appearing online at approximately the same time:

• One Reddit user reported that multiple Office 2019 installations suddenly became deactivated, and said entering the product keys again restored activation on at least some devices
• The same Reddit user later updated the post to say the problem was not limited to Office 2019, and that some systems required signing into a Microsoft account and selecting the license rather than just entering the key
• Another administrator said several unrelated customers contacted them after Office had been completely uninstalled
• A user replied: "My Office 2019 and dad's Office 2016 installs both got nuked overnight... both are 100% legit keys purchased long ago"
• Similar reports appeared in Microsoft forums, where multiple people reported similar issues after installing the update

The Mixed-Bitness Problem: Why Some Installs Disappeared

Van Hautte later discovered that KB5002907 appears to remove and reinstall, or migrate, the existing Office installation as part of its update process.

This is where things got worse for some businesses. Van Hautte says that on systems with Office components of different architectures — such as:

• A 32-bit Office 2016 or 2019 installation alongside
• A 64-bit Microsoft Access Runtime

...the reinstall can fail because Microsoft Office setup does not allow mixing 32-bit and 64-bit Office products.

Microsoft has not confirmed that mixed-bitness installations cause this behavior.

Microsoft's Response: Update Paused

After BleepingComputer contacted Microsoft about the reports, the company confirmed that it had paused the update while investigating the issue.

Microsoft also updated the KB5002907 support bulletin to acknowledge the problems:

Microsoft confirms that affected Office installations can suffer from two different problems:

• Office appears unlicensed — Microsoft recommends that customers reactivate their purchased product
• Office is removed entirely — Described by Microsoft as "rare cases," those users must download and reinstall their purchased copy of Office 2016 or Office 2019

Full Timeline of the Incident

How to Recover: Reactivation and Reinstall

If your business has been affected, here's how to recover:

If Office Shows as "Unlicensed Product"

If Office Was Completely Removed

Why This Matters for Every Business

This incident is a reminder of something every business should understand: "optional" updates are not always optional, and even well-intentioned updates can cause serious disruption.

• Updates can break production systems — This wasn't a security patch; it was a "helpful" update that disabled Office across multiple organizations
• Automatic installation compounds the risk — Even updates labeled "optional" installed automatically on many devices
• Mixed-architecture environments are especially vulnerable — 32-bit Office alongside 64-bit runtimes created failures where Office was removed but not reinstalled
• Perpetual licenses are still widely used — Despite Microsoft's push to subscription, many businesses still rely on Office 2016 and 2019
• Recovery takes time — Even when the fix is simple (re-entering a key), doing it across dozens or hundreds of PCs is disruptive
• Trust in automatic updates is damaged — Businesses will think twice before letting updates install automatically in the future

Why Businesses Rely on Managed IT Services for Update Management

Here's the hard truth: most small and mid-sized businesses have no way to prevent this kind of update disaster on their own. Updates install automatically. Users don't know to defer them. And when something breaks, there's no one to catch it before dozens of PCs are affected.

That's where Managed IT Services (MSPs) come in. A modern MSP provides the patch management discipline, testing processes, and rapid response capability that protect a business from exactly this kind of incident.

Why SMBs Choose Managed IT Over DIY

For most organizations, the "we'll deal with it if it happens" approach fails when updates break critical systems:

• You can't recover from a problem you don't know about — Without monitoring, incidents are discovered by users, not IT
• Manual recovery doesn't scale — Re-entering product keys across hundreds of PCs takes days
• Microsoft isn't your support line — Vendor support is slow; MSPs know how to work around issues
• Rollback requires planning — You need backup images or restore points to undo a bad update
• Prevention is cheaper than recovery — Pilot testing and update deferral cost far less than a full-day outage
• Skill gap — Patch management, testing, and incident response are specialized disciplines

What to Ask a Potential MSP Partner About Update Management

If you're evaluating MSPs (or wondering whether your current one is doing enough), ask these questions:

• Do you test updates in a pilot group before broad deployment?
• Do you have a policy for deferring optional updates?
• Can you roll back a bad update quickly?
• Do you monitor for activation failures and application errors?
• Do you track our Office license keys and activation records?
• Do you have response playbooks for update-related incidents?
• How quickly can you respond if dozens of PCs are affected?

At SystemLogicIT, we provide Managed IT Services and Microsoft 365 governance tailored to businesses across the United States and United Kingdom. If your organization needs help with patch management, update testing, or recovery from incidents like this, we'd be glad to talk.

What Businesses Should Do

Whether you manage IT in-house or through a partner, here's a practical checklist based on this incident:

• Don't install KB5002907 — The update has been paused by Microsoft; do not force-install it
• Audit your Office installations — Check whether any Office 2016 or 2019 installs show as "Unlicensed Product"
• Locate your product keys — Ensure you have Office 2016 and 2019 product keys stored securely
• Check for mixed-bitness configurations — 32-bit Office alongside 64-bit runtimes creates elevated risk
• Review update deferral settings — Consider deferring optional updates by a week or more
• Implement update testing — Pilot critical updates in a small group before broad rollout
• Set up monitoring — Alert on activation failures, Office errors, and unexpected application issues
• Prepare rollback capability — Backup images or restore points allow fast recovery from bad updates
• Communicate to users — Tell employees how to reactivate Office if they see "Unlicensed Product"
• Engage a Managed IT Services partner — If patch management discipline isn't in place today

Final Thoughts

The KB5002907 incident is a reminder that updates are not always safe, and "optional" doesn't always mean optional. A well-intentioned Microsoft update designed to help out-of-date installations ended up disabling legitimate Office 2016 and 2019 licenses across multiple organizations.

Microsoft did the right thing by pausing the update quickly. But the incident exposed a gap that most small and mid-sized businesses have: no testing, no rollback, no monitoring, no rapid response.

The businesses that avoided this incident — or recovered from it quickly — were the ones with patch management discipline already in place.

Key takeaways:

• KB5002907 deactivated Office installs — Affecting perpetual Office 2016 and 2019 licenses
• Some installs were completely removed — Especially on mixed 32-bit/64-bit configurations
• "Optional" didn't mean optional — The update installed automatically on many devices
• Microsoft paused the update — On September 26, after BleepingComputer contacted them
• Recovery is possible — Re-enter product keys or reinstall Office
• Two problems confirmed — Unlicensed appearance and complete removal
• Mixed-bitness installs at higher risk — Setup can't mix 32-bit and 64-bit Office
• Patch management discipline matters — Testing, deferral, and rollback prevent incidents like this
• Managed IT Services bridge the gap — Controlled deployment, monitoring, and rapid response
• Prevention is cheaper than recovery — Always test updates before broad rollout

If your organization needs help with patch management, update testing, or Office license recovery, contact SystemLogicIT for expert Managed IT Services and Microsoft 365 governance across the United States and United Kingdom.