Microsoft Admits Always On VPN Fix Failed in October Update
The tech giant confirms the VPN connectivity bug remains unresolved despite previous claims.
1The Failed Fix Disclosure
Microsoft officially acknowledged that the Always On VPN issue, previously marked as resolved on October 13, 2026, remains active. The company updated its status from Resolved back to Mitigated in message WI1482218. This admission follows a premature announcement that the security update had successfully addressed the connectivity failures reported by enterprise system administrators.
2Scope of the VPN Bug
The technical issue specifically impacts Windows 11 versions ranging from 24H2 through 26H2. It originated following the September 2026 Windows security update, which inadvertently broke the background authentication mechanism. This functionality is critical for users who rely on seamless, automated VPN connections without needing to manually input credentials for every single session.
3Technical Failure Mechanism
The bug manifests when the VPN is configured to attempt alternative connection methods after an initial failure. Microsoft identified that using automatic protocol selection, specifically between IKEv2 and SSTP, triggers the error. Affected connections often remain stuck in a perpetual 'Connecting' state or repeatedly fail, frequently displaying a 'port already in use' error message.
4Current Workaround Requirements
Since the October patch failed to resolve the underlying code defect, administrators must continue relying on the temporary workaround. Microsoft advises users to manually disable automatic protocol selection and force the system to use a single, specific protocol. This configuration change is currently the only viable method to restore stable network connectivity for users.
5Future Resolution Timeline
Microsoft has confirmed that a permanent resolution for the VPN connectivity bug is currently under development. The company stated that a fix is planned for release in an update scheduled for the coming weeks. Until this new patch is deployed, the existing workaround remains the primary recommendation for all affected Windows 11 environments.
6Impact on IT Operations
The failure to deliver a functional fix creates significant operational friction for IT teams managing large-scale Windows deployments. Administrators who relied on the October update to restore service must now re-evaluate their patching schedules. This situation highlights the complexities of maintaining stable VPN infrastructure within the evolving Windows 11 24H2 and 26H2 ecosystem.
7Communication and Transparency
The reversal of the status update serves as a reminder of the challenges in verifying security patches across diverse network configurations. By reverting the status to Mitigated, Microsoft aims to manage expectations while acknowledging the error. Clear communication regarding these technical regressions is essential for maintaining trust with enterprise clients managing critical remote access.
8Strategic Implications for Admins
System administrators should monitor future update releases closely to ensure the promised fix effectively addresses the IKEv2 and SSTP protocol conflicts. Given the recurring nature of this specific VPN issue, testing patches in isolated environments before full-scale deployment is highly recommended. Stability remains the priority until the official patch is verified and released.