Windows 10 1903 breaks VPN connections if you have telemetry disabled

[Master Disaster]

Before we begin I feel it's important to stress, Microsoft have acknowledged this as a bug and have already stated it will be fixed in the future so t probably isn't intentional.

 

Yeah this one's a doozy, basically if you setup an automated VPN (actually any dial up connection) on Windows 10 1903 then it will cause the RASMAN (Remote Access Connections Manager) service to error out with error code 0xc0000005. Strangely this only happens on automatic connections, manual ones are (probably?) not affected. Older builds are not affected either.

Quote

Microsoft has recently confirmed a new issue affecting Windows 10 May 2019 Update (version 1903) on Build 18362.207 (KB4501375). A bug in Windows 10 May 2019 Update’s latest build breaks down the Remote Access Connection Manager service and affects the operation of VPN services.

 

Remote Access Connection Manager (also known as RASMAN) handles Windows’ connection to the services like VPN. It’s important to have RASMAN running in the background to operate certain VPN service or dial-up connections. Certain VPN connections may not work as expected when RASMAN is disabled on Windows 10.

 

In an updated support document, Microsoft stated that Remote Access Connection Manager service could stop working and return error 0xc0000005 on Windows 10 version 1903. The Redmond Giant also revealed that the problem occurs when users or administrators set up a VPN profile as an Always On VPN connection with or without device tunnel.

 

If you configure a VPN connection and use it in manual mode, RASMAN may not crash. It’s worth noting that Windows 10 version 1809, 1803 and older versions are not affected.

And the fix for this problem? Enable telemetry using GPO or the registry and it goes away.

Quote

A workaround does exist and affected users are required to manually configure the default telemetry settings by modifying Group Policies or Windows Registry.

 

To fix RASMAN error 0xc0000005 with Group Policies, follow these steps:

1.     Launch Group Policies (gpedit.msc) from Start or Windows Run.
2.     Browse to the following path:
3.     Computer Configuration\Administrative Templates\Windows Components\Data Collection and Preview Builds\Allow Telemetry
4.     Double-click on the policy to enable it.
5.     Choose one of the three levels – Basic, Enhanced, and Full.
6.     Open Start menu and search ‘Services’
7.     On the Services tab, look for Remote Access Connection Manager.
8.     Right-click on RASMAN and restart it.

You can also fix RASMAN error 0xc0000005 with Windows Registry:

1.     Launch Windows Registry.
2.     Browse to the following location:
3.     HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection
4.     Look for entry ‘AllowTelemetry’.
5.     Double-click it and enter value 1, 2, or 3 (Basic, Enhanced, Full respectively).

 

In case the AllowTelemetry does not exist, you can create it manually. To create the entry, right-click the right-pane blank area and create DWORD (32-bit) named ‘AllowTelemetry’.

 

After applying the changes to Registry, you may need to restart RASMAN from Windows Services settings.

Microsoft have confirmed this bug and are working on a patch.

Quote

Microsoft says it is already working on a patch and the fix will be included in a future release, but Microsoft hasn’t revealed when it plans to resolve problems with RASMAN.

https://www.windowslatest.com/2019/07/01/microsoft-acknowledges-new-bug-in-windows-10-may-2019-update/

 

I wonder how many people have been running VPNs for the last few months thinking they were safe and actually the service had crashed? According to some online estimates 50 million users are running 1903.

 

Now you have a choice, either have your ISP spy on you, or Microsoft.

[mr moose]

4 minutes ago, Master Disaster said:

I wonder how many people have been running VPNs for the last few months thinking they were safe and actually the service had crashed? According to some online estimates 50 million users are running 1903.

 

I would personally laugh if it turns out people breaking the law got caught because of this.  Its like wearing a hoody and mask to do a drive by but not checking if the number plates are hidden.

[Chunchunmaru_]

2 hours ago, Master Disaster said:

 Strangely this only happens on automatic connections, manual ones are (probably?) not affected. Older builds are not affected either.

And the fix for this problem? Enable telemetry using GPO or the registry and it goes away.

Microsoft have confirmed this bug and are working on a patch.

https://www.windowslatest.com/2019/07/01/microsoft-acknowledges-new-bug-in-windows-10-may-2019-update/

That's only when using the Windows network manager to set up a VPN connection, right?

 

This shouldn't be affected by users using a browser plugin or other frontends like OpenVPN I suppose

[Ashleyyyy]

can Microsoft ever make a piece of software that's not broken to shit? 

[jagdtigger]

4 hours ago, Master Disaster said:

this as a bug

Yeah right..... /s

[Doobeedoo]

That's quite interesting bug, good it's getting fixed soon. So also it's with some VPNs too. Oh well. 

[dfsdfgfkjsefoiqzemnd]

Funny how their bugs always have a negative impact on users' privacy.  I have yet to encounter one that increases it. 

[Blake]

14 hours ago, Master Disaster said:

Before we begin I feel it's important to stress, Microsoft have acknowledged this as a bug and have already stated it will be fixed in the future so t probably isn't intentional.

 

Yeah this one's a doozy, basically if you setup an automated VPN (actually any dial up connection) on Windows 10 1903 then it will cause the RASMAN (Remote Access Connections Manager) service to error out with error code 0xc0000005. Strangely this only happens on automatic connections, manual ones are (probably?) not affected. Older builds are not affected either.

And the fix for this problem? Enable telemetry using GPO or the registry and it goes away.

Microsoft have confirmed this bug and are working on a patch.

https://www.windowslatest.com/2019/07/01/microsoft-acknowledges-new-bug-in-windows-10-may-2019-update/

 

I wonder how many people have been running VPNs for the last few months thinking they were safe and actually the service had crashed? According to some online estimates 50 million users are running 1903.

 

Now you have a choice, either have your ISP spy on you, or Microsoft.

Keep in mind that there is 0 point to modifying that registry entry unless your running education or enterprise enditions on Windows 10 (as it wont actually disable telemtry on pro/home editions).

 

This "bug" was reported on Day 0 of the 1903 patch release, and has been floating around enterprise message boards for a while now 

 

[Ashleyyyy]

1 hour ago, Captain Chaos said:

Funny how their bugs always have a negative impact on users' privacy.  I have yet to encounter one that increases it. 

well 1809 deleted your files. they can't spy on your files if they delete them. 

[DrMacintosh]

Has there been a release of Windows 10 that was not plagued by major issues? 

[Arika]

people use the inbuilt VPN settings?

[looterz]

On 7/7/2019 at 8:59 PM, Arika S said:

people use the inbuilt VPN settings?

First thing that came to my mind as well, I honestly forgot it was a feature.

[DaRk0]

On 7/7/2019 at 11:19 AM, Chunchunmaru_ said:

That's only when using the Windows network manager to set up a VPN connection, right?

 

This shouldn't be affected by users using a browser plugin or other frontends like OpenVPN I suppose

Good question.

I experienced crashes with NordVPN service on Windows while it was working on mobile and MacBook. Now it makes more sense I guess.

 

Or maybe it's just a localized problem unrelated to Windows. Didn't have time to investigate.

[Curious Pineapple]

On 7/8/2019 at 2:56 AM, DrMacintosh said:

Has there been a release of Windows 10 that was not plagued by major issues? 

I have no issues at all