Windows 10: connection problems in the home office due to VPN bug

As Microsoft has announced, a bug in the Windows update KB4535996 leads to problems when using the VPN under Windows 10. The company reports that the problems in particular arise when using Office 365 and Microsoft Teams Redmond in his message with.

According to Microsoft, systems affected by this problem are increasingly struggling with connection breaks when using VPN and proxy clients and a restricted or non-existent Internet connection status.

Restarting Windows 10 is said to temporarily fix the problem while Microsoft is working on a patch for its operating system. Windows 10 1909, 1903 and 1809 as well as current Windows Server operating systems are affected.

Devices that use a manual or automatically configured proxy, especially with a virtual private network (VPN), may show a limited or no connection status in the notification area.

This can happen when a VPN is connected or disconnected, or after the status between the two has changed.

Microsoft

KB4535996 again causes problems

It’s not the first time that the Windows update is causing problems on Windows 10. The update KB4535996 caused systems to crash in early March and increased the number of blue screens and error codes of type 0x800f0922.

The security patch 4524244 had previously been withdrawn and problems with the cumulative update KB4532693 had been confirmed, which could even lead to data loss in some cases due to incorrect temporary user profiles.

For the current VPN problem, that especially in times of increased home office due to the direct consequences of the corona virus (SARS-CoV-2) can be very annoying, Microsoft is now promising a corresponding bugfix in early April.

However, users who increasingly use VPN and proxy clients and do not want to restart their system regularly can temporarily uninstall the update KB4535996 using the Windows 10 Control Panel.

We are working on a resolution and are targeting a Microsoft Catalog only release of an out-of-band update to resolve this issue by early April.

Microsoft

–