Padlock graphic with the text Windows 11 Always On VPN bug not fixed after all

Windows 11 Always On VPN Bug Isn’t Fixed After All: Here’s the Workaround

The Windows 11 Always On VPN bug is not fixed. Microsoft marked it as resolved after the October 2026 update, then admitted that label was a mistake. If your work VPN hangs on “Connecting,” this is probably why.

The good news is that there is a clean workaround, and a permanent fix is promised in the coming weeks.

Here are the key facts at a glance:

  • Affects Windows 11 24H2 and later, after the September 2026 security updates.
  • Hits Always On VPN profiles that use automatic protocol selection (IKEv2 and SSTP fallback).
  • Microsoft changed the status back to “Mitigated” (tracked as WI1482218).
  • No release date for the fix yet, only “the coming weeks.”

That list is the short version. The rest of this post covers what breaks, how to dodge it, and who actually needs to worry.

What the Windows 11 Always On VPN bug actually does

After a first connection attempt fails, the VPN can get stuck in a “Connecting” state. Later attempts may then throw the error “The specified port is already in use.”

The trigger is protocol fallback. When a profile is set to pick a protocol automatically, Windows tries one (say IKEv2) and falls back to another (SSTP). That handoff is where things jam.

Always On VPN is Microsoft’s built-in business VPN feature, usually pushed to laptops by IT teams. The reports so far do not say that third-party VPN apps are affected.

Why Microsoft’s “fixed” label was wrong

Microsoft first acknowledged the problem in late September. Then the known-issue entry was “mistakenly updated to Resolved status” on October 13, the same day as Patch Tuesday, according to BleepingComputer.

A service alert to IT admins this week corrected it. The October cumulative update, KB5127648, did not fix the VPN problem, as Windows Report also notes.

Here is the timeline in one place:

When What happened
Late September 2026 Microsoft acknowledges VPN failures after the September security updates.
October 13, 2026 Issue wrongly marked “Resolved” around Patch Tuesday.
Week of October 19 Status corrected to “Mitigated”; October updates confirmed not to fix it.
Coming weeks Permanent fix promised, no exact date.

If you skipped the big October rollup because of its size, our October 2026 Patch Tuesday breakdown explains what it did fix, including three zero-days.

How to work around it today (for IT admins)

The only official workaround is to stop using automatic protocol selection. Here is how to apply it:

  • Open the Always On VPN profile assigned to the affected devices.
  • Replace automatic selection with one protocol: SSTP only or IKEv2 only.
  • Push the updated profile and check that connections no longer stall.

There is a catch. With fallback gone, the protocol you choose has to work on every network your users connect from. Hotel and airport Wi-Fi often block IKEv2 ports, so SSTP over port 443 is the safer pick for travelers. That is our reading of the trade-off, not Microsoft’s advice.

Plan to revert the profile once the fix lands, so users get fallback back.

What regular users should do about the VPN problem

If you use a work laptop, send IT a short note with the exact error text. It speeds up their diagnosis and tells them you are on an affected build.

Do not uninstall security updates to chase this. The October release closes real holes, and rolling it back leaves you more exposed than a flaky VPN does.

This is also not the only October headache. If your office Wi-Fi misbehaved after the same update, see our guide to the KB5127648 802.1X login fix.

How can you tell it is this bug and not a bad network? Look for three signs together: the problem began after the September updates, the VPN sits on “Connecting” instead of failing fast, and a retry brings the port error. If a restart makes it work once and it breaks again later, that pattern fits too.

Home users with a personal VPN app can relax for now. This one lives in the managed, business side of Windows.

Frequently Asked Questions

Is the Windows 11 Always On VPN bug fixed?

No. Microsoft has the issue listed as “Mitigated,” and a permanent fix is planned for an update in the coming weeks.

Which Windows versions are affected?

Windows 11 24H2 and later, once the September 2026 security updates are installed.

What does “The specified port is already in use” mean here?

It is the error some users see on retry after a failed connection attempt. It points to the protocol fallback getting stuck, not to another app on your PC.

Does this affect NordVPN or other VPN apps?

The reports only describe Always On VPN profiles. Nothing published so far says third-party VPN apps are hit.

The takeaway

Admins should not wait. Lock affected profiles to a single protocol today, note it in your change log, and set a reminder to undo it when Microsoft ships the fix. The bigger lesson is to treat “Resolved” in a vendor dashboard as a claim to test, not a fact, at least until you see your own connections working.


Comments

Leave a Reply

Your email address will not be published. Required fields are marked *