Skip to content
tricknfixGAMING · TECHNOLOGIE · INFORMATIQUE
Create

Windows 11 Always On VPN stuck on Connecting after September updates: KB5127936 fix

Editorial illustration of an abstract network tunnel and lock motif, suggesting a Windows Always On VPN connection stuck after an update.
Crédit : TricknFix — illustration éditoriale.

After September 2026 security updates, some Always On VPN profiles using automatic protocol selection could stay stuck on Connecting or show “The specified port is already in use.” Microsoft briefly marked the issue Resolved on Oct 13 then withdrew that claim. KB5127936 (Oct 28 preview for 25H2/26H2) lists the Always On VPN fix; IT can mitigate by forcing SSTP only or IKEv2 only.

Microsoft’s KB5127936 preview (dated 28 October 2026) lists a fix for Always On VPN problems that appeared after installing a September security update. On affected profiles that used automatic protocol selection or protocol fallback, connections could remain stuck in a Connecting state or fail after an initial attempt. In some cases, later attempts showed the error “The specified port is already in use.”

This article covers that Always On VPN issue, the status timeline reported around mid-October 2026, the KB5127936 fix path for Windows 11 25H2 and 26H2, and the IT single-protocol mitigation. It does not rehash other TricknFix pieces already published from the same preview (Smart App Control grayed out, File Explorer customizable context menu, Cloud rebuild, restore summary).

No hands-on VPN lab test is claimed here. Facts follow Microsoft’s KB notes and clearly attributed secondary reporting, consulted on 6 November 2026 (Europe/Paris). On a managed PC, ask your IT team before changing VPN profiles or installing optional updates — and do not uninstall security updates to “fix” connectivity.

What broke for Always On VPN

According to the Always On VPN item under normal rollout on KB5127936:

  • The issue affects Always On VPN connections after installing a September security update
  • 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
  • In some cases, subsequent connection attempts could display “The specified port is already in use.”
Always On VPN is an enterprise-oriented VPN model (often used with domain-joined, non-domain-joined, or Microsoft Entra ID–joined devices). Home users without Always On VPN profiles are outside this specific symptom set.

Status timeline: Resolved claim withdrawn (secondary reporting)

As of 21 October 2026, BleepingComputer (Sergiu Gatlan) reported that Microsoft had mistakenly updated a service disclosure for this VPN issue to Resolved on 13 October 2026, then returned its status to Mitigated. The same reporting said a resolution was planned in an update in the coming weeks, and paraphrased Microsoft’s mitigation for IT: change the Always On VPN profile from automatic protocol selection to a single protocol — SSTP only or IKEv2 only, depending on the environment.

Treat that Oct 13 → Mitigated chronology as secondary reporting of Microsoft’s service-alert language. This article does not invent Microsoft alert IDs beyond what that page states. Prefer the live KB5127936 text for the fix description.

On Windows release health for Windows 11, version 25H2 (consulted the same day), a dedicated Always On VPN known-issues row was not found; other issues such as USB audio (still Mitigated) are out of scope here. Remote Desktop error 0xC000000D appears there as Resolved KB5127936 and is covered separately as a community discussion topic, not as this article’s main angle.

The fix for Windows 11 25H2 and 26H2: KB5127936

The KB5127936 preview page (dated 28 October 2026) lists:

  • Applies to Windows 11 version 26H2 and 25H2 (all editions listed on that page)
  • OS builds 26300.9818 (26H2) and 26200.9818 (25H2)
  • Under normal rollout: [Always On VPN] Fixed — same Connecting / port-in-use description after the September security update when automatic protocol selection or fallback was configured
How Microsoft documents obtaining the optional preview: open Start > Settings > Windows Update > Advanced options > Optional updates, then check for available optional updates.

Important scope note from the same KB: starting with the October 2026 release, non-security preview updates are available only for Windows 11 versions 25H2 and 26H2. Windows 11 version 24H2 no longer receives those non-security preview updates (Enterprise and Education continue monthly security updates). Organizations still on 24H2 should follow their IT update channel rather than expect this non-security preview package.

If your device already has KB5127936 or a later update that includes the same Always On VPN fix, Microsoft’s KB framing treats the issue as addressed for that package — prefer the official update path over staying on a long-term workaround when IT allows it.

IT workaround: single protocol (SSTP only or IKEv2 only)

Until a fixed update is installed (or if your channel does not yet offer KB5127936), attributed reporting of Microsoft’s mitigation says IT administrators can change the Always On VPN profile from automatic protocol selection to a single protocol:

  • SSTP only, or
  • IKEv2 only
Choose based on the organization’s environment, security, and deployment requirements. This is an IT-managed change — end users on corporate laptops should not rewrite VPN profiles on their own. Do not strip September (or later) security updates as a DIY “fix.”

Other KB5127936 items already on TricknFix

KB5127936 is a large preview. Separate TricknFix articles already cover other features from that package; they are different intents:

Sources

30 views

Conversation (0)