Quick Answer
Microsoft said the Always on VPN connection issue had been "mistakenly updated to Resolved status on October 13, 2026" and that it had returned its status to Mitigated. Until the update containing the resolution is available, affected small-business IT teams can change an Always On VPN profile from automatic protocol selection to SSTP only or IKEv2 only.
Affected Symptom
Microsoft first acknowledged the problem in a late-September 2026 service alert for IT administrators. The company said it affected devices running Windows 11 version 24H2 and later after installation of the September 2026 security updates when the initial Always On VPN connection attempt failed.

The affected configurations used automatic protocol selection or protocol fallback. In those cases, a connection could remain stuck in a Connecting state or fail after an initial attempt. Some later attempts displayed the message, "The specified port is already in use."
Always On VPN replaced the legacy DirectAccess technology. It supports domain-joined, non-domain-joined and Microsoft Entra ID joined devices running Windows 10, Windows 11 and Windows Server. It runs in the background and establishes secure tunnels to the user’s corporate network when a device connects to the internet.
What Changed in the October Updates
After releasing the October 2026 Patch Tuesday cumulative updates, Microsoft marked the issue as resolved, but in a Tuesday update it said the issues weren’t actually addressed and that a fix would ship later. The alert stated that the disclosure had been "mistakenly updated to Resolved status" and returned it to Mitigated.

The release notes for KB5127648 said the update fixed an Always On VPN connection issue affecting systems that had installed KB5124008. However, Microsoft later advised administrators that the issues weren’t actually addressed, and it said a resolution was planned to be included in an update to be released in the coming weeks. The service alert did not specify a release date for that update. Microsoft’s archived KB5127648 release notes provide the primary update record.
Microsoft’s Temporary Workaround
Microsoft’s temporary mitigation is to change the Always On VPN profile from automatic protocol selection to one tunneling protocol. The available choices in the alert are SSTP only and IKEv2 only.
The protocol choice depends on the environment and configuration. Microsoft’s guidance says organizations should consider their environment, security and deployment requirements before choosing one protocol.
The protocol supported by the tunnel type also matters. Microsoft’s Always On VPN overview states that User Tunnel supports SSTP and IKEv2, while Device Tunnel supports IKEv2 only and has no SSTP fallback option.
Small-Business IT Teams Should Check Before Changing the Profile
- Check the affected device’s Windows release against Microsoft’s official update records.
- Check whether the Always On VPN profile uses automatic protocol selection or protocol fallback.
- Confirm whether the deployment uses User Tunnel or Device Tunnel.
- Keep a record of the original profile settings.
- Validate access to the internal applications and services required for work after the change.
What to Do Now
- Review the Windows release and installed update records for affected devices.
- Review the Always On VPN profile settings for automatic protocol selection or fallback.
- Confirm the tunnel type and the protocol supported by the organization’s VPN gateway.
- Record the original settings and check the internal resources used by staff.
FAQ
Did the October 2026 Windows 11 Updates Fix the Always on VPN Issue?
No. Microsoft said the October cumulative updates did not resolve the issue and returned its service-alert status from Resolved to Mitigated.
Which Windows Versions Were Affected?
Microsoft said the issue affected systems running Windows 11 version 24H2 and later after installation of the September 2026 security updates.
What Temporary Workaround Did Microsoft Recommend?
Microsoft recommended changing the Always On VPN profile from automatic protocol selection to one protocol, either SSTP only or IKEv2 only.
When Was a Permanent Fix Expected?
Microsoft said a resolution was planned for an update released in the coming weeks. Its service alert did not provide a specific release date.
What Always on VPN Symptoms Did Microsoft Report?
Microsoft said affected connections could remain stuck in a Connecting state or fail to connect after an initial connection attempt failed. Some later attempts displayed a message stating that the specified port was already in use.
Related Coverage
- Microsoft Warns of Always on VPN Issues After September 2026 Updates (November 14, 2026): Microsoft has notified IT administrators that some Windows 11 devices may fail to connect to enterprise networks through Always On VPN after installing the September 2026 security updates.

