Quick Answer
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. The temporary workaround is to change the affected profile from automatic protocol selection to SSTP only or IKEv2 only. Connections may remain in a Connecting state, repeat failed attempts or display an error about the specified port being in use.
Which Windows 11 Builds Are Affected?
Microsoft’s September 23, 2026 service alert identifies the following originating updates for the Always On VPN issue:

| Windows 11 Build | KB | Reported Symptom |
|---|---|---|
| Version 26H1 | KB5124012 | Always On VPN may remain in a Connecting state, repeatedly attempt a connection or fail after the first attempt. |
| Version 25H2 | KB5124008 | Automatic protocol selection or protocol fallback may prevent a successful tunnel connection. |
| Version 24H2 | KB5124008 | Automatic protocol selection or protocol fallback may prevent a successful tunnel connection. |
The alert says Microsoft was still working on a permanent solution when it issued the temporary guidance. Microsoft later released the October 2026 cumulative updates KB5127648 and KB5127646 to address the known issue on affected systems, according to BleepingComputer’s October 14 report.
How Does the Failure Appear?
According to Microsoft’s service alert, the issue occurs when Always On VPN is configured to try another connection method if the initial attempt fails. Microsoft’s examples include automatic protocol selection with IKEv2 and SSTP.

An affected connection may remain in a Connecting state or repeatedly attempt to connect without succeeding. A subsequent attempt may also display the message: ‘The specified port is already in use.’
A Microsoft Q&A report from September 9 described a test involving Windows 11 24H2 and 25H2 clients using certificate-based authentication, RRAS and NPS on Windows Server 2019, and an Intune-deployed VPN profile. The reporter said Always On VPN worked before KB5124008 was installed, stopped working after installation and worked again after the update was uninstalled and the device restarted. The behavior was reproduced on multiple client devices.
Another response in that Microsoft Q&A thread described an automatic profile configured for IKEv2 followed by SSTP. The response said IKEv2 worked with certificate or EAP authentication, while the automatic transition to SSTP stopped after KB5124008 was installed. The response also said an SSTP-only profile worked. These reports describe particular configurations and do not establish that every Always On VPN installation encountered the issue.
What Is Microsoft’s Temporary Workaround?
Microsoft recommends changing the Always On VPN profile from automatic protocol selection to one tunneling protocol. The two options are:
- SSTP only
- IKEv2 only
Microsoft says organizations should choose the protocol according to their environment, security and deployment requirements. According to BleepingComputer, Microsoft released the KB5127648 and KB5127646 cumulative updates that address the known issue on affected systems, and the temporary fix is for customers who can’t immediately install the October 2026 Patch Tuesday update.
How Always on VPN Fits Into a Business Network
Always On VPN replaces the legacy DirectAccess technology and runs in the background. It establishes a secure tunnel to the corporate network when a device connects to the internet. The service supports Windows 10, Windows 11 and Windows Server, including domain-joined, non-domain-joined and Microsoft Entra ID joined devices.
Administrators can define which applications and services use the VPN connection. The service supports IKEv2, SSTP and multi-factor authentication. Microsoft says organizations should select the protocol based on their environment, security and deployment requirements.
Other Issues Reported Around the September Updates
Microsoft also released emergency updates for Hyper-V issues, Remote Desktop Services failures and USB audio problems associated with the September 2026 updates. The company separately provided a temporary workaround for a Windows 11 domain-credential sign-in issue and was working on a bug that could affect the built-in File History backup feature.
Check the affected builds and connection behavior, not just the September 2026 updates. Windows 11 26H1 KB5124012, 25H2 KB5124008 and 24H2 KB5124008 are linked to the Always On VPN protocol-selection problem. Connections may remain at Connecting or report ‘The specified port is already in use.’
What to Do Now
- Record the Windows 11 version, build and installed KB on devices assigned to staff who use Always On VPN.
- Ask staff for the exact connection behavior, including whether the client remains at Connecting or reports an error about the specified port.
- Inspect deployed Always On VPN profiles for automatic protocol selection or protocol fallback.
- Review the available options for changing the Always On VPN profile before applying a configuration change.
- Document VPN connectivity and the availability of expected applications before and after the profile change.
- Check the October 2026 cumulative updates KB5127648 and KB5127646 when deciding how to address the issue on affected systems.
Key Considerations
- Microsoft’s September 23 alert identified Windows 11 26H1 KB5124012, 25H2 KB5124008 and 24H2 KB5124008 as originating updates.
- The reported failure is tied to automatic protocol selection or protocol fallback, and Microsoft’s workaround selects either SSTP or IKEv2 alone.
- The Microsoft Q&A reports describe particular configurations and multiple devices.
- KB5127648 and KB5127646 were released in October 2026 to address the known issue on affected systems.
- Microsoft’s temporary guidance required administrators to consider their environment, security and deployment requirements before selecting a protocol.
FAQ
Which Windows 11 Updates Can Cause Always on VPN Connection Problems?
Microsoft’s September 23, 2026 service alert identified Windows 11 version 26H1 KB5124012, version 25H2 KB5124008 and version 24H2 KB5124008 as originating updates.
What Error Can Affected Always on VPN Connections Display?
A subsequent connection attempt may display the error: ‘The specified port is already in use.’
How Can IT Administrators Temporarily Address the Issue?
Microsoft recommends changing the Always On VPN profile from automatic protocol selection to a single protocol, either SSTP only or IKEv2 only, depending on the environment and configuration.
Which Devices Support Always on VPN?
Always On VPN is available on Windows 10, Windows 11 and Windows Server. It supports domain-joined, non-domain-joined and Microsoft Entra ID joined devices.
Which Cumulative Updates Fixed the Always on VPN Issue?
Microsoft released KB5127648 and KB5127646 in October 2026 to address the known Always On VPN issue on affected systems.
Related Coverage
- Microsoft Fixes USB Audio Issues From September Windows Updates (November 12, 2026): Microsoft says the November 2026 cumulative updates resolve USB audio issues plaguing Windows users who have installed security updates released since September.

