Microsoft retracts claim that October updates fixed Windows 11 Always On VPN bug

Microsoft stated on October 13, 2026, that its October Patch Tuesday updates for Windows 11 did not actually fix a persistent bug affecting Always On VPN connections. The company had previously flagged the issue as resolved, but a subsequent service alert to IT administrators clarified that the problems remained unaddressed and a permanent fix is planned for future releases.

According to BleepingComputer, Microsoft returned the service alert status from "Resolved" back to "Mitigated" after realizing the October cumulative updates failed to patch the defect. The vendor apologized for the confusion and indicated that a true resolution would ship in an update released in the coming weeks, leaving administrators to manage the ongoing instability.

Context and Background

The connectivity issue was first acknowledged by Microsoft in late September 2026, following the installation of the September 2026 security updates on systems running Windows 11 24H2 and later. The bug triggers when the initial Always On VPN connection attempt fails, particularly when automatic protocol selection or protocol fallback is configured with IKEv2 and SSTP.

When the flaw manifests, affected VPN connections may remain stuck in a Connecting state or fail to establish a link after the initial failure. In some instances, subsequent connection attempts display an error message stating that the specified port is already in use, disrupting remote access for enterprise users.

Who Is Affected

Always On VPN is a feature that replaced the legacy DirectAccess technology, supporting domain-joined, non-domain-joined, and Microsoft Entra ID–joined devices running Windows 10, Windows 11, and Windows Server. It operates in the background to establish secure tunnels back to corporate networks whenever a device connects to the internet.

The specific bug impacts users on Windows 11 24H2 and later versions who installed the September 2026 cumulative updates. While the feature supports multiple operating systems, this particular incident has been tied to the recent Windows 11 updates, causing disruption for organizations relying on automatic protocol selection for their remote access strategies.

What should you do?

Microsoft has provided a temporary workaround for organizations facing these connectivity issues. IT administrators can mitigate the problem by modifying the Always On VPN profile to disable automatic protocol selection. Instead, administrators should configure the profile to use a single protocol, choosing either SSTP only or IKEv2 only based on their specific environment and security requirements.

Organizations should evaluate their deployment needs to select the appropriate single protocol. This manual configuration bypasses the faulty automatic selection logic that causes the connection failures. Until Microsoft releases a permanent fix in an upcoming update, this manual intervention remains the primary method for restoring stable VPN connectivity.

What to do and how to stay safe: Microsoft

• Review your Always On VPN profiles to check if automatic protocol selection is currently enabled.
• Configure devices to use a single tunneling protocol, such as SSTP or IKEv2, to bypass the bug.
• Monitor Microsoft service alerts for announcements regarding a permanent fix in future updates.
• Verify that your security and deployment requirements are met by the chosen single protocol.

Step-by-step guide: Mobile Device Security: How to Protect Data Beyond Passwords

General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

Did the October 2026 Windows 11 update fix the Always On VPN bug?

No, Microsoft admitted that the October updates did not resolve the issue and mistakenly marked it as fixed.

How can administrators work around the VPN connection failure?

Administrators can mitigate the issue by changing the VPN profile to use only SSTP or only IKEv2.

Which Windows versions are affected by this specific bug?

The issue affects systems running Windows 11 24H2 and later that installed the September 2026 updates.