微软被迫承认，其声称已在 10 月 13 日的更新中修复的 Always On VPN 故障，实际上并未修复。我们都经历过这种情况：你修复了那个 Bug，或调整了配置设置，自己挺满意，结果发现没生效，不得不发一封“额，关于那个修复”的羞愧跟进邮件。微软也遭遇了同样的情况。在上一次安全更新中自豪地宣布问题已解决后，公司不得不将原本得意的宣称收回，在编号为 WI1482218 的消息中发出一声悲凉的小响——就像小丑喇叭的声音：“此披露于 2026 年 10 月 13 日被错误地更新为‘已解决’状态。我们已将其状态恢复为‘已缓解’。‘对造成的任何不便或困惑，我们深表歉意。’”
Microsoft has been forced to admit that the Always On VPN glitch – which it said it had fixed in an update on October 13 – was not actually fixed after all. We've all been there. You fix that bug, or tweak the configuration setting, and you're pleased with yourself, but it turns out it didn't take, and you have to send the "er, about that fix" follow-up email of shame. The same has happened to Microsoft. After proudly declaring the problem resolved as part of its last security update, the company had to roll back its triumphant trumpeting to a sad little parp from a clown's horn in the message WI1482218: "This disclosure was mistakenly updated to Resolved status on October 13, 2026. We have returned its status to Mitigated. "We apologize for any inconvenience or confusion."
有问题的是操作系统的 Always On VPN 功能，这是一段实用的代码，能在后台悄悄打开 VPN 连接，免去繁琐的身份验证提示。它可追溯至 Windows 10，微软在 2026 年 9 月 Windows 安全更新无意中破坏了该功能后，提醒管理员注意相关问题。该问题影响 Windows 11 24H2 至 26H2 版本。当 VPN 设置为在初始连接失败时尝试不同的连接方法时（微软举了使用自动协议选择搭配 IKEv2 和 SSTP 的例子），可能会出现该问题。
The bug in question concerns the operating system's Always On VPN functionality, a useful bit of code that quietly opens a VPN connection in the background without tiresome prompts for authentication. It dates back to Windows 10, and Microsoft alerted administrators to problems after the September 2026 Windows security update inadvertently broke it. The issue affects Windows 11 versions from 24H2 through 26H2. The problem could occur when the VPN was set to try a different connection method if the initial connection failed (Microsoft gave the example of using automatic protocol selection with IKEv2 and SSTP).
据微软称：“受影响的 VPN 连接可能会保持‘正在连接’状态，或反复尝试连接而不成功。后续连接尝试还可能显示错误：‘指定的端口已在使用中’。”这对管理员来说并不理想。微软在 10 月 13 日强调的变通方法是将自动协议选择改为单一协议，这至少能让受影响的用户先用起来。该变通方法保持不变。
According to Microsoft: "Affected VPN connections might remain in a 'Connecting' state or repeatedly attempt to connect without succeeding. Subsequent connection attempts might also display the error: 'The specified port is already in use'." This is not ideal for administrators. The workaround Microsoft highlighted back on October 13 was to change from automatic protocol selection to a single protocol, which would at least get affected users up and running. The workaround remains the same.
坏消息是，因为上周的修复方案不起作用，受影响的管理员需要再使用临时方案一段时间。微软声称：“解决此问题的方案计划于即将在未来几周发布的更新中纳入。”
The bad news is that, because last week's fix did not work, affected administrators will need to apply the workaround for a bit longer. Microsoft claimed, "A resolution for this issue is planned to be included in an update to be released in the coming weeks." ®