Microsoft fixes Always On VPN connection issues caused by September Windows updates

October Patch Tuesday releases KB5127648 and KB5127646 resolve the bug, with a workaround available for those unable to install immediately

By LineZotpaper
Published
Read Time2 min
Microsoft has released cumulative updates that fix a known issue causing Always On VPN connection failures on Windows 11 systems after installing the September 2026 security updates. The October Patch Tuesday releases include KB5127648 and KB5127646, which address the bug on all affected versions.

Microsoft has resolved a known issue that caused Always On VPN connection failures after the September 2026 Windows 11 security updates. The company acknowledged the problem in a late September service alert to IT administrators, noting that the bug triggered failures when the initial connection failed, such as when using automatic protocol selection with IKEv2 and SSTP on systems running Windows 11 24H2 and later.

"When automatic protocol selection or protocol fallback was configured, affected VPN connections could remain stuck in a Connecting state or fail to connect after an initial connection attempt failed," Microsoft said in a support document. "In some cases, subsequent connection attempts could display the error, 'The specified port is already in use.'"

The Always On VPN remote access solution replaces legacy DirectAccess technology and works with domain-joined, non-domain-joined, and Microsoft Entra ID–joined Windows 10, Windows 11, and Windows Server devices. It runs in the background, automatically establishing a secure tunnel to corporate networks whenever a device connects to the internet.

For customers unable to install the October updates immediately, Microsoft has provided a temporary workaround: IT administrators can change the Always On VPN profile from automatic protocol selection to a single protocol—either SSTP only or IKEv2 only—depending on their environment and configuration.

The September updates also triggered other issues, prompting Microsoft to release emergency fixes for Remote Desktop Services failures, Hyper-V issues, and USB audio problems affecting both home and enterprise Windows users.

§

Analysis

Why This Matters

  • Always On VPN is a core remote access tool for many enterprises; connection failures can disrupt productivity and remote work.
  • IT administrators face an additional patching burden and may need to implement workarounds if they cannot deploy the October update quickly.
  • The recurrence of post-update issues underscores the importance of testing Windows updates in non-production environments before broad rollout.

Background

Always On VPN is Microsoft's recommended remote access solution, replacing the older DirectAccess technology. It is widely used in corporate environments to provide secure, automatic connections to internal networks. The September 2026 security updates caused multiple problems, including VPN failures, Remote Desktop Services issues, Hyper-V problems, and USB audio glitches, prompting emergency out-of-band fixes for some of those.

Key Perspectives

Microsoft: The company acknowledged the bug promptly, provided a temporary protocol-selection workaround, and fixed the issue in the October cumulative updates. It continues to recommend Always On VPN for secure remote access. IT Administrators: They face the challenge of deploying updates and workarounds while managing user expectations and maintaining connectivity. The need to reconfigure VPN profiles manually is a short-term inconvenience. Enterprise Users: Employees relying on Always On VPN may have experienced connection drops or failed attempts; the fix restores normal operation once the new updates are deployed.

What to Watch

  • How quickly enterprise IT teams deploy the October cumulative updates across their Windows 11 fleets.
  • Whether future security updates introduce similar regressions for Always On VPN or other networking features.
  • If Microsoft improves its update testing processes to catch such issues before release.

Sources

Zotpaper

Written by software from the reporting listed above, scored by an automated standards desk, and published without a person reading it first. If something here is wrong, tell the editor and it will be put right.

How we workSubscribe