October's Windows Server updates: what to fix first, and what might break
Microsoft’s October 2026 security release fixed more than 1,400 vulnerabilities, the largest single month on record. A number that size makes for dramatic headlines, but it isn’t a useful way to decide what to do. Most of those fixes cover products you’ll never run, and only a handful matter for a typical Windows server.
This post covers the ones that do: what to patch first, what the update can break, and two support deadlines that passed on the same day.
What to prioritise
The flaw already being exploited. CVE-2026-96951 is a Windows Shell bug that lets a malicious file bypass Mark of the Web, the warning Windows normally shows for files that came from the internet. Microsoft confirmed it was being exploited before the fix shipped, and CISA added it to its Known Exploited Vulnerabilities catalogue on 13 October. It needs someone to open a crafted file or link, so it matters most on servers where people sign in over Remote Desktop and handle email, downloads or shared documents.
The domain controller bug. CVE-2026-70229 is a critical remote code execution flaw in Active Directory Domain Services, triggered by a crafted network packet. Microsoft rates it “exploitation more likely”. If you run domain controllers, they go to the front of the queue this month. They should also never be reachable from the internet, patch or no patch.
The publicly disclosed one. CVE-2026-108398, a .NET Framework flaw, was public before the fix arrived. It lets a malicious assembly slip past Windows Defender Application Control, so it matters if you rely on WDAC to restrict what runs on a server.
On-premises Exchange. The month’s Exchange updates include CVE-2026-70571, a critical remote code execution flaw that can be triggered by a malicious email. If you still run Exchange on your own servers, install the October Exchange security update as well as the Windows one.
What might break
Exchange and the RPC Endpoint Mapper. The October cumulative updates for Server 2016, 2019, 2022 and 2025 add a default limit to the RPC Endpoint Mapper, capping how much memory it uses to handle endpoint lookups. Busy Exchange servers can run into that limit. Microsoft has acknowledged the problem: people can’t sign in to Outlook on the web, mail queues grow, and database replication can fail. Administrators report that the symptoms tend to appear around a day after patching, and that a reboot only clears them temporarily.
Microsoft advises against uninstalling the update. The temporary workaround is a registry value, EpmapSavedContextCap, which raises the limit. Microsoft suggests starting at 65536. It lets Endpoint Mapper use more memory than the new default allows, so treat it as a stopgap until Microsoft ships a proper fix. Look for events 1006 and 4082 in the Application log as early signs. Servers without Exchange are unlikely to be affected.
Update, 11 November: Microsoft fixed this in the November Windows updates: KB5131080 for Server 2025, KB5131090 for 2022, KB5131085 for 2019 and KB5131291 for 2016. Once the Exchange server is running the November Windows update for its version, or a later cumulative update, the registry workaround is no longer needed. Microsoft says you can leave the value in place or remove it. On Server 2025 machines that use hotpatching, Microsoft’s notes for the hotpatch (KB5131077) don’t list the Exchange fix, so keep the value there until the full update is installed or Microsoft confirms the hotpatch carries the fix. See November’s Windows Server updates.
Update, 12 November: SQL Server linked servers. On 11 November, Microsoft confirmed a second problem caused by the October updates. On servers where SQL Server uses linked servers to reach external databases such as Oracle or PostgreSQL through OLE DB providers, connections can stay open after queries complete and build up over time, which can slow the server down. Microsoft lists Server 2016, 2019, 2022 and 2025 as affected. The November update doesn’t fix it; Microsoft says an out-of-band update will follow in the next few days. See November’s Windows Server updates for the details and what to do in the meantime.
Other changes in default behaviour. A few hardening changes arrived switched on, and they’re worth knowing about before someone reports something odd:
- NTLMv1 on Server 2025. On machines without Credential Guard, credentials derived from NTLMv1 are now blocked for single sign-on. Wi-Fi and VPN connections that use MS-CHAPv2 may stop connecting automatically. Microsoft’s long-term answer is certificate-based authentication, and a temporary registry setting puts the old behaviour back in audit mode.
- AD FS. Insecure permissions on the AD FS key container are now corrected automatically.
- ReFS. Auditing is now on for ReFS volumes on externally attached storage, ahead of enforcement later.
- Better NTLM auditing on Server 2019 and 2022. This isn’t a breaking change but a useful tool: it shows which systems still use NTLM and why, which helps plan its removal.
Two deadlines that passed on 13 October
Windows Server 2012 and 2012 R2 are finished. October brought the last Extended Security Update for both. From November, new vulnerabilities in these versions stay unfixed. None of the servers we host or manage run either version: we retired them from our own platform in 2022, well ahead of Microsoft ending support in October 2023, and haven’t taken on management of servers running them since. If you still have one, it needs to be isolated from the internet and other systems now, and replaced as soon as possible.
Windows Server 2022 has left mainstream support. This one is far less urgent. It still gets security updates until 14 October 2031, but no new features or non-security fixes. For new builds, Windows Server 2025 is now the sensible default.
Next in line is Windows Server 2016, which receives its last update on 12 January 2027. We’ll cover planning for that in a separate post.
A short checklist
- Confirm the update installed by checking the build number:
| Version | Build after the October update |
|---|---|
| Windows Server 2025 | 26100.33650 |
| Windows Server 2022 | 20348.5761 |
| Windows Server 2019 | 17763.9376 |
| Windows Server 2016 | 14393.9612 |
- Patch domain controllers and internet-facing servers first.
- Take a snapshot or confirm a recent backup before patching anything important.
- Keep everyday browsing and email off servers. It’s the easiest way to blunt flaws like CVE-2026-96951.
- If you run Exchange, watch for the symptoms above in the first couple of days, and keep the registry workaround ready.
- Check Microsoft’s Windows release health page during the week after an update for newly acknowledged issues.
Sources
- Microsoft: KB5126655, Windows Server 2022 October 2026 update
- Microsoft Message Center: NTLMv1 hardening changes (MC1508562)
- Microsoft Exchange Team: October 2026 Exchange Server security updates
- Tenable: October 2026 Patch Tuesday analysis
- Security Affairs: CISA adds Windows Shell flaw to KEV catalogue
- EighTwOne: Windows Server patches breaking Exchange
- endoflife.ai: the support deadlines of 13 October 2026
This post is general information, not professional advice for your specific setup.