Microsoft Rettracts Claim That Always On VPN Glitch Was Fixed in October Update
Microsoft admits the October 13 update did not resolve the Always On VPN issue, reverting its status to Mitigated after mistakenly marking it as Resolved.
Key points
- Microsoft corrected the status of the Always On VPN issue from Resolved to Mitigated after admitting the October 13 fix failed.
- The flaw affects Windows 11 versions 24H2 through 26H2, causing connections to hang or fail with port-in-use errors.
- Administrators must continue using the workaround of disabling automatic protocol selection to maintain connectivity.
Microsoft has officially admitted that the Always On VPN glitch, which the company claimed to have resolved in its October 13 security update, remains unfixed. The software giant reversed its previous statement, correcting the issue’s status from Resolved back to Mitigated in advisory WI1482218. This correction follows reports that the earlier update did not actually address the underlying connectivity problems for affected users.
The company apologized for the confusion caused by the premature declaration of a fix. According to Microsoft, the disclosure was mistakenly updated to Resolved status on October 13, 2026. The vendor has since returned the status to Mitigated, acknowledging that the problem persists. This admission means that organizations relying on the October update to restore VPN functionality have not received the expected resolution.
Context and Background
The Always On VPN feature allows Windows devices to maintain a secure connection to corporate networks without requiring user interaction or repeated authentication prompts. This functionality has been part of the operating system since Windows 10, providing seamless access for remote workers and managed devices. The current instability began after the September 2026 Windows security update inadvertently broke this feature, disrupting connections for many enterprises.
Microsoft initially alerted administrators to these problems following the September update. The issue specifically arises when the VPN is configured to attempt alternative connection methods if the primary method fails. For example, using automatic protocol selection with IKEv2 and SSTP can trigger the bug. This configuration is common in environments where network conditions vary and fallback protocols are necessary for reliability.
Who Is Affected
The connectivity issues impact Windows 11 versions ranging from 24H2 through 26H2. Users on these specific versions may experience VPN connections that remain stuck in a Connecting state indefinitely. Alternatively, the system may repeatedly attempt to connect without succeeding, leading to significant delays in accessing network resources. These symptoms disrupt productivity and complicate remote access strategies for IT departments.
Affected connections may also display an error message stating that the specified port is already in use. This error prevents subsequent connection attempts from succeeding, further locking users out of the network. The problem is not universal but occurs specifically under the conditions where automatic protocol selection is enabled. This limits the scope to configurations that rely on dynamic protocol switching for resilience.
What should you do?
Microsoft maintains that the workaround provided on October 13 remains the only effective solution until a proper fix is released. Administrators should change their VPN configuration from automatic protocol selection to a single, static protocol. This adjustment bypasses the logic that triggers the bug, allowing connections to establish successfully. The vendor has not confirmed a timeline for a permanent code fix.
As Threat Times reported on October 20, 2026, Microsoft’s October updates have also destabilized Exchange Server, causing OWA failures and email delays. While that issue has a registry workaround, the Always On VPN problem requires configuration changes. IT teams should monitor both issues, as they represent separate but concurrent stability challenges in the October 2026 update cycle.
What to do and how to stay safe: Microsoft
- Review your VPN client settings and disable automatic protocol selection if you are using IKEv2 and SSTP.
- Manually select a single protocol for your VPN connection to bypass the connectivity loop.
- Monitor internal logs for errors indicating that the specified port is already in use.
- Wait for an official vendor update before reverting any temporary configuration changes.
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 13 update fix the Always On VPN issue?
No, Microsoft admitted that the fix was not effective and reverted the status to Mitigated.
Which Windows versions are affected by this VPN glitch?
The issue affects Windows 11 versions from 24H2 through 26H2.
What is the current workaround for the VPN connection failures?
Change the configuration from automatic protocol selection to a single protocol.
