On the morning of September 24, support phones began ringing at a managed service provider in Belgium as commercial workstations suddenly lost access to their core productivity software. Within ten minutes, five separate client organizations reported that their desktop suites displayed an Unlicensed Product warning or had vanished entirely from local storage. The common culprit behind the sudden disruption was the KB5002907 update, a deployment package that Microsoft pushed to address out-of-date subscription software but erroneously distributed to standalone perpetual systems. Microsoft confirmed the reports and paused the worldwide rollout to prevent further workstation failures [1].
How the KB5002907 Update Reached Perpetual Machines
According to official release notes from Microsoft, the package carried the formal title “Optional update for out-of-date Microsoft 365 Apps installations” and had an explicitly narrow operational mandate. The vendor engineered the package specifically for Windows PCs running Microsoft 365 Apps that had fallen more than 90 days out of date on either the Current Channel or the Monthly Enterprise Channel. Its designated purpose was to refresh stranded background services, restore broken update pipelines, and bring client software back to the latest supported builds. Under standard operating guidelines, Microsoft published the package as an optional download through Windows Update that should have required administrative consent before applying [1].
Despite those designated parameters, the package failed to respect its intended boundaries. Multiple system administrators reported that the KB5002907 update bypassed manual approval settings and installed itself automatically across client environments. Furthermore, instead of restricting its scope to cloud-connected Microsoft 365 Apps subscriptions, the patch actively executed on machines configured with perpetual licenses for Office 2016 and Office 2019. Unlike the silent Excel copy-paste bug that compromised data calculations within spreadsheet workbooks, this deployment failure directly severed local activation states [1].
The silent delivery caught commercial networks completely off guard. Christian Van Hautte, who operates a managed service provider in Belgium, documented that dozens of client endpoints across multiple organizations took the update on September 24 without any user intervention. Van Hautte observed that every affected machine ran perpetual Office 2016 or Office 2019 Home & Business editions (perpetual one-time purchase licenses). The KB5002907 update arrived around September 23 and immediately stripped license credentials from systems that had operated stably for years. Dozens of endpoints failed simultaneously [1].
IT Administrators Uncover Widespread License Deactivations
When workers attempted to launch Word or Excel, the applications opened with disabled features and displayed an Unlicensed Product banner across the top title bar [1]. Richard Speed reported in The Register that perpetual software holdouts running legacy versions bore the brunt of the licensing glitch after applying recent updates. The disruption immediately raised concerns among business managers who wondered: can administrative updates disrupt local installations without warning? The sudden deactivations paralyzed routine office communications and triggered emergency support tickets across independent corporate networks [1, 2].
System administrators who inspected the broken workstations discovered that the underlying software had not expired. Entering the original 25-character product key restored activation on several machines handled by Van Hautte’s support team. However, recovery was not uniform across every environment. Discussion threads on Reddit and the official Microsoft community forums revealed varying license behaviors. One administrator noted that entering the original alphanumeric key resolved the problem on some endpoints, whereas other installations required users to log directly into an associated Microsoft account to select their digital perpetual license [1].
User frustrations mounted as reports spread beyond managed corporate environments to independent home workstations. One affected user on Reddit reported that legitimate Office 2019 and Office 2016 suites across family devices vanished overnight despite holding valid, fully paid retail keys. Both licenses were genuine. The sudden loss of desktop functionality caused some users to question whether a background policy update could lock their machines, illustrating how licensing breaks mimic broader operating system freezes [1].
Mixed Architecture Conflicts Trigger Full Office Removals
In severe instances, the update went far beyond deactivating credentials. Office vanished entirely. Local folders emptied, shortcuts disappeared, and program files were erased from storage drives [1].
Van Hautte examined affected client drives to determine why the software had uninstalled itself rather than merely dropping its licensing flags. His technical investigation revealed that the installer for the KB5002907 update executes a multi-stage migration routine that quietly removes the existing Office suite before attempting a clean reinstallation of modernized application binaries [1]. Under typical deployment circumstances, this removal and reinstallation process finishes seamlessly without operator awareness.
That reinstallation routine encountered catastrophic failure on computers maintaining mixed software architectures (a configuration combining components of different bitness on a single operating system). Van Hautte discovered that workstations pairing a 32-bit installation of Office 2016 or Office 2019 with a 64-bit edition of Microsoft Access Runtime triggered an immediate installer block, because the standard Microsoft Office setup engine strictly prohibits installing 32-bit and 64-bit productivity programs on the same Windows device. When the KB5002907 mechanism removed the existing 32-bit suite and initiated the setup routine, the installer halted upon detecting the 64-bit Access Runtime dependency, leaving the operating system completely devoid of its primary Office applications without initiating an automated rollback. Office setup prohibits mixed architectures [1].
Microsoft Halts Deployment to Investigate KB5002907
Following outreach from BleepingComputer regarding the mounting wave of administrator complaints, Microsoft officially acknowledged the anomalous behavior and paused the update to prevent further workstation failures. “We are aware of these reports and have paused the update while we investigate,” a Microsoft spokesperson told BleepingComputer. The company stated that additional customer guidance would be published across official support channels once software engineers determined the root cause of the deployment defect [1].
Microsoft subsequently updated its official KB5002907 support bulletin to warn system administrators about the documented installation hazards. “Microsoft is investigating reports of unexpected results on some devices running Office 2016 or Office 2019 after this update is installed,” the updated support document noted. The documentation formally stated: “To prevent additional devices from being affected, we have paused the rollout of this update”. Microsoft acknowledged the unexpected behavior. The common factor was KB5002907 [1].
The company confirmed that affected systems generally encounter one of two distinct failure modes following the update process. In the majority of scenarios, desktop applications remain present on disk but revert to an unlicensed status. In what Microsoft described as “rare cases,” the entire suite is removed from the local machine. The vendor noted that its technical investigation remains active, though the company has not yet verified whether mixed-bitness installations account for the complete application uninstalls reported by external technicians [1].
Recommended Recovery Steps for Affected Workstations
For endpoints currently experiencing licensing errors, Microsoft instructs users to manually re-enter their original product license key through application settings to restore full functionality. Administrators should launch Word or Excel, navigate to the Account management panel, and input their perpetual Home & Business key or authenticate the associated Microsoft commercial account. In organizations managing multiple seats, re-authenticating the product key successfully clears the Unlicensed Product flag on the majority of affected endpoints without requiring software reinstalls [1].
Systems that suffered total suite removal require a comprehensive manual reinstallation procedure. Microsoft directs administrators and end users whose desktop programs were erased to log into their Microsoft account portal, download the original standalone installer for Office 2016 or Office 2019, and execute a fresh deployment. Technicians must verify that any secondary dependencies, such as Microsoft Access Runtime, match the bitness of the primary office suite before beginning the setup process to prevent installer clashes [1].
The incident highlights ongoing friction between continuous cloud update cycles and legacy perpetual software installations [2]. IT departments maintaining non-subscription Office builds are advised to monitor Windows Update catalogs closely and inspect incoming patches before broad deployment. Until Microsoft delivers revised guidance or a permanent remediation package, the pause on the KB5002907 update protects remaining perpetual machines from unintended deactivation [1].
- ONLINE NEWS Abrams, L. (2026, September 26). Microsoft pauses KB5002907 update after Office license deactivations. BleepingComputer. [Article Link]
- ONLINE NEWS Speed, R. (2026, September 25). Office 2016 and 2019 holdouts blame update for license deactivation bug. The Register. [Article Link]
