November 3, 2026

Before October’s Patch Tuesday, Take Stock of Your Old Office Installs and Expiring Windows Support

The Office 2016 and 2019 updates that keep arriving after end of support caused trouble in September. Next week’s Patch Tuesday brings end-of-support milestones, too. Here is the calendar and a layered plan.

Illustration of a calendar grid with a highlighted week, stacked application windows and layered shield rings around a laptop

Here Is How Layered Defenses Help When Updates Can’t Be Trusted Alone

Patching is supposed to be the simple part of security. Lately it hasn’t been. Monthly fix counts keep breaking records, a Microsoft update aimed at one set of Office apps knocked out older ones, and several support deadlines arrive with next week’s release.

The dates and details here come from Help Net Security’s October 2026 Patch Tuesday forecast. Layer 7 has added the planning advice.

How we got here

October 14, 2025: Office 2016 and 2019 reach end of support

Microsoft ended support for both suites but kept the option to issue more updates. It has done so almost every month since. Because those versions are outside mainstream support, the forecast notes they probably aren’t tested against the newest updates built for other products.

July 2026: Enterprise update channels merge

Microsoft combined the Semi-Annual Enterprise Channel and the Monthly Enterprise Channel into one enterprise update channel. That is a welcome simplification after years of renamed and reshuffled Office channels.

September 2026: A record month and a bad update

September’s Patch Tuesday addressed 973 CVEs across Microsoft products, an all-time record. Only two were reported as known exploited and none as publicly disclosed. Separately, KB5002907, meant to update out-of-date Microsoft 365 apps, was followed by reports of Office 2016 and Office 2019 being removed or deactivated. The problem was widespread enough that Microsoft paused the update. The September updates also caused an Excel cut-and-paste failure and a File History/Windows Backup problem.

September 29, 2026: Windows 11 26H2 ships

The new release shares a kernel with 24H2 and 25H2, so those versions can move to it with an enablement package and minimal disruption.

Tuesday, October 13, 2026: Next Patch Tuesday

The forecast says this release will bring the final updates for Windows 11 version 24H2 Home and Pro, the last ESU updates for Windows Server 2012 and 2012 R2, and the end of ESU support for Exchange Server 2016 and 2019. Microsoft has said fixes for the Excel paste issue and the File History/Windows Backup issue are also coming. Expect high CVE counts again, plus a new Chrome desktop update and likely Firefox and Thunderbird fixes.

Here is how layered defenses help

When an update can break an unsupported app, and the fix list runs into the hundreds, patching alone can’t carry your security. Layers give you room to patch carefully instead of blindly.

  • Layer 1, a current software inventory. Know which machines still run Office 2016 or 2019, Windows 11 24H2 Home or Pro, Server 2012 or Exchange 2016/2019. Endpoint management tools (Microsoft Intune is one example, and many RMM platforms do the same) can produce this list.
  • Layer 2, staged patching. Apply updates to a small pilot group first, especially on machines with older Office, then roll out widely once nothing breaks. Prioritize the few vulnerabilities marked as actively exploited.
  • Layer 3, endpoint detection. A modern endpoint protection and detection tool covers the gap between release day and full deployment.
  • Layer 4, identity controls. Multifactor sign-in and least-privilege accounts limit the damage if an unpatched app gets exploited.
  • Layer 5, tested backups. Since the September updates disrupted File History and Windows Backup, check that your backups are actually completing, and keep a copy outside Windows’ built-in tools.

What this means for your company

Older Office suites and expiring Windows versions are quiet risks. They keep working, so nobody budgets to replace them, until an update breaks them or a vulnerability goes unpatched for good.

  • Make a replacement plan for any Office 2016 or 2019 installs. Decide whether a subscription or a current perpetual version fits, and settle on one update channel.
  • Move Windows 11 24H2 Home and Pro machines to a supported release. The 26H2 enablement package makes that a light lift.
  • Flag Server 2012/2012 R2 and Exchange 2016/2019 for migration or isolation now that the extended updates are ending.
  • Count your help desk tickets. If old Office versions drive a steady stream of support calls, the forecast’s advice to consolidate pays for itself.

Need help planning an Office cleanup or a patching routine that won’t break the tools your staff depends on? Reach out to Layer 7 Data Solutions to discuss how we’ve helped companies similar to yours.

About The Author