Skip to main content

Latest update to Windows 10 has a bug that could break VPN services

Windows 10 Surface Pro 4 stock photo
Mark Von Holden/AP Images for AP Images for Windows/Microsoft Image Gallery

Microsoft has announced a bug in the Windows 10 May 2019 Update which could hamper the operation of virtual private networks (VPNs). The issue affects the Remote Access Connection Manager service, which is what Windows uses to manage connections to a VPN.

Remote Access Connection Manager, also known as RASMAN, needs to run in the background for always-on VPNs to work, or for VPN users who connect to the internet via dial-up. If the service stops working, it will interfere with these users’ VPN connections.

Given how many people around the world use a VPN to access the internet, whether for security reasons or convenience, there are millions of users who could be affected by this bug. It affects the latest version of Windows 10, KB4501375 (OS Build 18362.207), which was released on June 27.

“The Remote Access Connection Manager (RASMAN) service may stop working and you may receive the error ‘0xc0000005’,” Microsoft warns on an updated support page. “You may also receive an error in the Application section of Windows Logs in Event Viewer with Event ID 1000 referencing ‘svchost.exe_RasMan’ and ‘rasman.dll’.”

Microsoft does say, “This issue only occurs when a VPN profile is configured as an Always On VPN (AOVPN) connection with or without device tunnel. This does not affect manual only VPN profiles or connections.” But many people use always on VPN, especially in enterprise environments or if they are browsing from countries with severe censorship restrictions or high levels of government surveillance.

There is a workaround for the issue available, by changing a value in the group policy settings. Find the setting at Computer Configuration>Administrative Templates>Windows Components>Data Collection and Preview Builds>Allow Telemetry and change the value of Safe Policy Setting to Enabled and set it to 1 (Basic), 2 (Enhanced), or 3 (Full).

There’s also an alternative method, but it requires editing a Windows Registry file. If you’re confident with the Registry, you can locate the value for the SubKey HKEY_LOCAL_MACHINE>SOFTWARE>Policies>Microsoft>Windows>DataCollection, and change the AllowTelemetry setting to a value of 1 (Basic), 2 (Enhanced), or 3 (Full).

If you’d rather not play with registry files or group policy settings, you can wait for Microsoft to roll out a fix, which it estimates will be available later this month.

Editors' Recommendations

Georgina Torbet
Georgina is the Digital Trends space writer, covering human space exploration, planetary science, and cosmology. She…
If your PC is running slowly, the latest Windows 11 update may be to blame
A laptop running Windows 11.

Microsoft may have a problem on its hands -- the latest Windows 11 update doesn't seem to be working as intended. According to various user reports, the update drastically slows SSD speeds, in some cases even cutting them in half.

If you've noticed that your PC is loading slowly or programs aren't running as quickly as you'd hoped, you might be affected by this problem. Here's how to fix it.

Read more
Windows 11 could be hurting your gaming performance
Overwatch 2 running on the LG OLED 27 gaming monitor.

If you’ve been wondering why your beefy graphics card hasn’t been performing as well as it should in Windows 11 or Windows 10, the answer could be Microsoft’s Virtualization Based Security (VBS). According to testing done by Tom’s Hardware, VBS could cause gaming performance to drop by as much as 10%.

In a suite of fresh benchmarks, Tom’s Hardware tested 15 different games, from Cyberpunk 2077 to Red Dead Redemption 2, both with VBS enabled and with the feature turned off. In some games, the results could be cause for concern.

Read more
Windows 11 has been causing problems with Intel graphics for months, and no one said a word
A Windows 11 device sits on a table.

If you're using Intel integrated graphics and you've been having some issues with DirectX apps, we may know the reason why -- outdated drivers paired with a recent Windows update.

According to Microsoft, a Windows 11 update may have caused some errors in Intel graphics. The update is not recent at all, so even if you haven't updated in the last few weeks, you may be affected.

Read more