Microsoft fixes VPN failures caused by April Windows updates

Today, ​Microsoft fixed a known issue breaking VPN connections across client and server platforms after installing the April 2024 Windows security updates.

“Windows devices might face VPN connection failures after installing the April 2024 security update or the April 2024 non-security preview update,” Redmond explains on the Windows health dashboard.

The list of impacted Windows versions includes Windows 11, Windows 10, and Windows Server 2008 and later.

While Microsoft did not provide a root cause for these VPN failures, it advised home users to use the Windows Get Help app and small business and large enterprise customers to reach out via the dedicated “Support for Business” portal if they need support.

Two weeks after first acknowledging it, ​Microsoft fixed this known issue in Windows cumulative updates released during the May 2024 Patch Tuesday.

The complete list of affected Windows versions and the cumulative updates that fix the VPN failures includes:

Admins who cannot immediately install this month’s Patch Tuesday updates can temporarily address the VPN issues by removing the problematic April cumulative updates.

“To remove the LCU after installing the combined SSU and LCU package, use the DISM/Remove-Package command line option with the LCU package name as the argument. You can find the package name by using this command: DISM /online /get-packages,” Microsoft says.

However, since Redmond includes all security fixes in a single update, uninstalling the April updates will also remove all fixes for patched security flaws, even though it resolves the Windows VPN issues.

One year ago, Microsoft acknowledged major L2TP/IPsec VPN speed issues over Wi-Fi connections after installing the April 2023 non-security updates on Windows 11 systems.

In January 2022, it released emergency updates to address L2TP VPN issues when connecting via the Windows VPN client after installing the January 2022 Patch Tuesday updates.

Today, Microsoft also fixed a known issue causing domain controller reboots and NTLM authentication failures after installing last month’s Windows Server security updates and a zero-day bug actively exploited to deliver QakBot and other malware unpatched Windows systems.