Microsoft pauses KB5002907 update after Office license deactivations

ALL office version users please read this ASAP!!

1 Like

Hi SoulAsylum:

My “perpetual” retail edition of Microsoft Office Home and Business 2019 C2R was affected by this bug after an automatic Windows Update delivered an update on 24-Sep-2026 called “Click-to-Run Update Support“ that was NOT optional (i.e., entering wmic qfe | find “KB5002907” in an elevated command prompt shows I did not receive the optional KB5002907 described in that BleepingComputer article). See my 24-Sep-2026 post # 2880629 in Richard Mitnick’s Office Updates in the AskWoody forum for further details.

My retail edition of MS Office 2019 C2R reached end of support on 14-Oct-2025 and the release history <here> still shows that Version 2508 / Build 19127.20302 (rel. 14-Oct-2025) is latest available version, but since the forced re-install and re-activation on 24-Sep-2026 my product is now at Version 2508 / Build 19127.20800 (a.k.a. v16.0.19127.20800).


Dell Inspiron 15 5584 | 64-bit Win 10 Pro v22H2 build 19045.7725 | Microsoft Defender v4.18.26080.4-1.1.26080.3 | Malwarebytes Premium v5.7.1.346-165.0.5751 | Microsoft Office Home and Business 2019 C2R Version 2508 / Build 19127.20800

1 Like

Having checked my Windows 10 daily use machine a bit ago, I do see the “click to run support” update my side as well. Thanks for the post.

Edited: I might add that the office update installed entirely on its own accord without any intervention on my part. I have Windows Updates set to manual as well. Interesting.

Fortunately, having rebooted this machine several times, my install has NOT required reinstall nor reactivation at this point. Checking Word I have the following: Microsoft® Word 2021 MSO (Version 2512 Build 16.0.19530.20144) 64-bit

SA

According to this article Microsoft has shard a fix for the issues with KB5002907.

https://www.neowin.net/news/microsoft-shares-fix-as-kb5002907-accidentally-breaks-licenses-deletes-windows-office-apps/

According to this article Microsoft has shard a fix for the issues with KB5002907.

https://www.neowin.net/news/microsoft-shares-fix-as-kb5002907-accidentally-breaks-licenses-deletes-windows-office-apps/

Hi SoulAsylum:

The link in that Neowin article only points to the MS support article KB5002907: Optional update for out-of-date Microsoft 365 Apps installations, which says that some affected MS Office 2016 and 2019 users may have to perform a clean reinstall of their Office product to get it working correctly again . That’s not much of a “fix” in my opinion.

At this point I’m not even sure if I will need to reinstall my Microsoft Office Home and Business 2019 C2R, but I’d like to delay that decision until Microsoft figures out why the problematic KB5002907 was pushed out to out-of-support Office C2R installations in the first place. All my Office programs seem to be working correctly since KB5002907 "Click-to-Run Update Support“ update triggered an automatic online repair that installed Version 2508 / Build 19127.20800 on my system, but according to a Microsoft Update Catalog search <here> this build is a 14-Sep-2026 “Semi-Annual Enterprise Channel (Preview) Feature Update” for Microsoft 365 Apps/Office 2019/Office LTSC.

My retail edition of MS Office 2019 C2R is on the Current Channel release channel and reached end of support on 14-Oct-2025. The release history <here> still shows that Version 2508 / Build 19127.20302 (rel. 14-Oct-2025) is latest available version.


Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.7725 * Microsoft Defender v4.18.26080.4-1.1.26080.3 * Malwarebytes Premium v5.7.1.346-165.0.5751 * Microsoft Office Home and Business 2019 C2R Version 2508 / Build 19127.20800

The issue was/is that Microsoft’s intent was to discontinue the “lightweight” free companion apps. The update in question borked a lot more instead. My Office 2021 retail install works as is as well. I’m just following this in case others start seeing their installs stop working and what the corrective actions will be.

SA

Hi SoulAsylum:

I’m not sure that was the intent if you are referring to the companion apps described in the 24-Sep-2026 Neowin article Microsoft killing Windows 11’s free Office companion apps which installed automatically. That article states those apps were exclusive to Win 11, and I have a Win 10 OS.

According to the Microsoft support article KB5002907: Optional update for out-of-date Microsoft 365 Apps installations the “Click-to-Run Update Support“ update was released on or around 24-Sep-2026 to fix the following problem :

“This optional update is available only for Windows PCs with Microsoft 365 Apps installations that are more than 90 days out of date and use Current Channel or Monthly Enterprise Channel. Installing the update can help the apps resume updating and move to a current build for the device’s assigned update channel … Consider installing the update if Microsoft 365 Apps on your Windows PC is more than 90 days out of date or has stopped updating normally.”

Windows Update delivered this “Click-to-Run Update Support“ update to my Win 10 machine as a mandatory (i.e., not optional) update, and I suspect it was incorrectly pushed to out-of-support MS Office 2016 C2R and 2019 C2R (and possibly MS Office 2021 C2R, which doesn’t reach end of support until 13-Oct-2026) products by mistake because of a glitch in the metadata that incorrectly targeted ALL Microsoft 365 and Office products that had not been updated in the past 90 days.


Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.7725 * Microsoft Defender v4.18.26080.4-1.1.26080.3 * Malwarebytes Premium v5.7.1.346-165.0.5751 * Microsoft Office Home and Business 2019 C2R Version 2508 / Build 19127.20800

My intent was that readers would read between the line of things and understand that. Microsoft broke installs for some that were NOT intended to be touched. Also that the update in question hit both Windows 10 and 11, whether set to automatically install or manually. My systems are set to get other product updates and Windows updates when I manually check yet the update was installed. Hope that clears things up a bit. :upside_down_face:

SA