Microsoft says October updates didn’t actually fix VPN issues
Description
Microsoft acknowledged that the October 2026 Windows 11 cumulative updates did not fix a known bug affecting Always On VPN connections. The issue causes VPN connections to remain stuck in a connecting state or fail, sometimes showing an error about ports already in use. Microsoft mistakenly marked the bug as resolved in October but reverted it to mitigated status, promising a fix in a future update. A temporary workaround involves configuring Always On VPN to use a single tunneling protocol (SSTP or IKEv2) instead of automatic protocol selection.
Affected software
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
A bug affecting Always On VPN connections on Windows 11 24H2 and later was initially reported after the September 2026 updates, causing connection failures when automatic protocol selection or fallback was enabled. Microsoft released October 2026 cumulative updates that were mistakenly flagged as resolving the issue. The company later clarified that the problem remains and that a fix will be included in an upcoming update. Meanwhile, IT administrators are advised to mitigate the issue by configuring VPN profiles to use either SSTP or IKEv2 exclusively rather than automatic protocol selection.
Potential Impact
The bug disrupts Always On VPN connectivity, causing connections to hang or fail, which can impact users' ability to securely connect to corporate networks. This affects devices running Windows 11 24H2 and later with Always On VPN configured for automatic protocol selection. The issue may cause operational disruptions for organizations relying on Always On VPN for secure remote access.
Defensive Guidance
Microsoft currently recommends a temporary workaround: IT administrators should configure Always On VPN profiles to use a single tunneling protocol, either SSTP only or IKEv2 only, based on their environment and security requirements. A permanent fix is planned for a future update. Administrators should monitor official Microsoft communications for the forthcoming patch.
Technical Details
- Classification
- {"confidence":0.3,"severitySource":"default","classifier":"rss-v2"}
- Article Source
- {"url":"https://www.bleepingcomputer.com/news/microsoft/microsoft-didnt-actually-fix-vpn-issues-caused-by-windows-updates/","fetched":true,"fetchedAt":"2026-10-21T10:33:30.188Z","wordCount":743}
Threat ID: 6ad894fa2cdf04f656deeb4d
Added to database: 10/21/2026, 10:33:30 UTC
Last enriched: 10/21/2026, 10:33:35 UTC
Last updated: 10/21/2026, 14:30:32 UTC
Views: 9
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.