Office 2016/2019, Microsoft 365 Apps: update KB5002907 reported to break licensing
Summary
Optional update KB5002907 is reported to cause Microsoft 365 Apps and Office 2016/2019 to lose their licence status. This is reported by users and trade media, not yet confirmed by the vendor. No vendor workaround or fix is known.
Symptoms
- Office apps show as unlicensed with a yellow banner warning of days left.
- Some devices were left with no working Office.
- Users report needing several reactivations and sign-outs to stabilise the licence state.
Affected
- Microsoft 365 Apps on Windows
- Office 2016 and Office 2019 on Windows
- Systems with optional update KB5002907 installed (exact builds not stated in the sources)
Workaround
No workaround known.
Fix
Not fixed yet. No vendor statement available.
Recommendation
Do not roll out optional update KB5002907 broadly until Microsoft confirms the issue or publishes a fix. Test it on a few pilot devices first. If devices are already affected, sign out and reactivate Office as reported by users, and watch for a vendor statement.
Check script: am I affected? (PowerShell, read-only)
Check: Office 2016/2019, Microsoft 365 Apps: update KB5002907 reported to break licensing
- What it checks
- Checks whether the update named in the community reports is installed on this device. It changes nothing, writes no file and needs no internet.
- What to do if affected
- Compare the symptoms with the entry; watch for a statement from the vendor before changing anything.
Community report: not yet confirmed by the vendor. The check is based only on the details of the reports (e.g. the update named) and is an indication, not proof.
Result and exit code: AFFECTED = 5, NOT AFFECTED = 0, FIXED – solution installed = 0, UNCLEAR = 6, error = 1 (as an Intune detection script: 1 = affected, otherwise 0).
What exactly happens?
- Only reads – changes nothing, writes no file, needs no internet and asks no questions.
- Checks: update KB5002907 installed
- Reports the result with one line per condition and the next step.
What is checked
- Indication of being affected: update KB5002907 installed
How to use the script – step by step
- Download: on the entry page, read the terms and conditions (section "Free scripts") and the disclaimer, tick "I accept" and click "Download script". The file is saved in your "Downloads" folder.
- Open PowerShell: press the Start key, type "PowerShell", press Enter. No administrator rights are needed – only if the result reports conditions as "not checkable", open PowerShell as administrator (right-click "Windows PowerShell" › "Run as administrator").
- Change to the Downloads folder (type or paste the command, then press Enter):
cd "$env:USERPROFILE\Downloads" - Compare the checksum: the command shows a long string. It must be exactly the same as "SHA-256" on the entry page (57CFC2DD6FE81CFF0F78213DE21708B807FD7EE96376C335DA98C266ADD2BA79). If it differs, delete the file and do not run it.
(Get-FileHash .\ITSB-Check-optional-update-kb5002907-breaks-microsoft-365-apps-and-offi-v1.ps1 -Algorithm SHA256).Hash - Unblock the file (Windows marks downloaded files). Alternatively in Explorer: right-click the file › Properties › tick "Unblock" at the bottom › OK.
Unblock-File .\ITSB-Check-optional-update-kb5002907-breaks-microsoft-365-apps-and-offi-v1.ps1 - Allow scripts for this PowerShell window only. This only applies until you close the window – the computer's setting stays unchanged. If PowerShell asks, confirm with "Y".
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass - Run the script. It only checks: it changes nothing, writes no file and needs no internet.
.\ITSB-Check-optional-update-kb5002907-breaks-microsoft-365-apps-and-offi-v1.ps1 - Read the result (at the bottom): "AFFECTED" – follow the steps under "what to do" (e.g. install the update or use the entry's fix script). "NOT AFFECTED" – nothing to do. "FIXED – solution installed" – nothing to do; you can undo a workaround you applied earlier. "UNCLEAR" – not everything could be checked: compare the details in the entry manually.
- Download without a browser (RMM, software distribution): the address needs "&agb=1". This means the person deploying the script accepts the terms and conditions (section "Free scripts") and the disclaimer on behalf of their organisation.
Invoke-WebRequest "https://www.it-sb.ch/ki-api/?a=dl&f=ITSB-Check-optional-update-kb5002907-breaks-microsoft-365-apps-and-offi-v1.ps1&agb=1" -OutFile ".\ITSB-Check-optional-update-kb5002907-breaks-microsoft-365-apps-and-offi-v1.ps1" - For many devices (RMM, scheduled task): command below, exit codes 0 = not affected or fixed, 5 = affected, 6 = unclear, 1 = error. Upload it as the detection script of an Intune remediation ("Run script in 64-bit PowerShell" = Yes): there it automatically reports 1 = affected, otherwise 0 (manually with -Intune).
powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\ITSB-Check-optional-update-kb5002907-breaks-microsoft-365-apps-and-offi-v1.ps1powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\ITSB-Check-optional-update-kb5002907-breaks-microsoft-365-apps-and-offi-v1.ps1 -Intune
Use at your own risk – no warranty, no liability if anything does not work or is wrong. Test before use and make a backup. Our terms and conditions (free scripts) apply. Generated automatically from the vendor’s statement and checked (rules, second AI review).
Download without a browser (RMM, software distribution): address with "&agb=1" – this means the person deploying the script accepts the terms on behalf of their organisation: https://www.it-sb.ch/ki-api/?a=dl&f=ITSB-Check-optional-update-kb5002907-breaks-microsoft-365-apps-and-offi-v1.ps1&agb=1
Reports from the community and trade media
Reports from forums, Q&A sites, Reddit and trade media – linked only, without the names of the authors; the vendor’s statement is authoritative.
- Office 2016 and 2019 holdouts blame update for license deactivation bug News · theregister.com, 25 Sep 2026
- Microsoft Office suddenly needs to reactivate: a bad update might be why News · pcworld.com, 28 Sep 2026
Sources
- Office 2016 and 2019 holdouts blame update for license deactivation bug News · www.theregister.com
- Microsoft Office suddenly needs to reactivate: a bad update might be why News · www.pcworld.com
Compiled from community reports and web research and translated with AI (Claude) – not yet confirmed by the vendor. The vendor’s statements are authoritative. Updated 2 Nov 2026, 00:36.
Where the information comes from
We continuously read the vendors’ official sources, community reports and trade media and summarise them in our own words, with a link to the source:
- Microsoft: Windows release health (Windows 10/11, Server 2016 to 2025), Windows message center, known issues of Microsoft 365 Apps (Outlook, Excel, Word, PowerPoint), Edge, Intune, Autopilot, Windows 365 and Entra Connect, Microsoft KB articles with timelines, Exchange and Windows IT Pro blogs, optionally Microsoft 365 service health and message center
- other vendors: Veeam KB, Citrix (known issues), Ubuntu and Debian (regressions), Broadcom (VMware), Fortinet, Cisco, Mozilla, Let’s Encrypt
- community (title, short excerpt and link only, without the names of the authors): Microsoft Q&A, Microsoft Tech Community (discussions), Veeam R&D Forums, Eleven Forum
- targeted web research with AI (Claude), e.g. on the updates of the month – this also finds discussions on Reddit and in forums; such entries are labelled as community reports until the vendor confirms them
- early warning from trade media (title and link only): Born’s Tech and Windows World, BleepingComputer, AskWoody, Windows Latest, Windows Central, gHacks, The Windows Club, Deskmodder, Dr. Windows, WindowsArea, Frankys Web, heise online
Summary and translation with AI (Claude by Anthropic) – without any data of visitors.
Affected? We can help.
We check whether your systems are affected, apply workarounds properly and plan for dated changes in good time.
