14 DAY TRIAL // Microsoft has recently acknowledged a new bug in Windows 10 version 1903, or May 2019 Update, explaining that devices where cumulative update KB4497935 is installed are likely to experience it.
This cumulative update was published on May 29, 2019 for Windows 10 version 1903, and it increased the OS build number to 18362.145.
According to the software giant itself, the glitch introduced by this cumulative update causes the Remote Access Connection Manager, also referred to as RASMAN, to stop working all of a sudden.
The service could hit error 0xc0000005, and the issue only occurs when a VPN profile is configured as an Always On VPN connection. The company explains the following:
“The Remote Access Connection Manager (RASMAN) service may stop working and you may receive the error “0xc0000005” when devices are manually configured to the non-default telemetry setting of 0. 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”.
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.”
The most important tidbit in this advisory is the one explaining where the issue occurs:
“when devices are manually configured to the non-default telemetry setting of 0”
Microsoft says a full patch for the bug will be released “in an upcoming” update, but no specifics are available. The next Patch Tuesday cycle takes place on July 9.
Taking into consideration the telemetry factor, the workaround comes down to setting the default telemetry level to basic, enhanced, or full. There are two ways to do this in order to fix the Remote Access Connection Manager service bug: the Group Policy Editor and the Windows Registry Editor.
If you want to use the Group Policy Editor, launch the app by clicking Start menu > type gpedit.msc. Browse to the following path:
Computer Configuration\Administrative Templates\Windows Components\Data Collection and Preview Builds\Allow Telemetry
You need to reboot RASMAN after making the policy changes in order to save your settings.
On the other hand, if you want to use the Registry Editor fix, the workaround comes down to creating or changing (if it already exists) a registry item.
Open the Registry Editor by clicking the Start menu > type regedit.exe. Browse to the following location:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection
AllowTelemetry
Double-click it to change the value and enter 1, 2, or 3, according to the following list:
1 = Basic
2 = Enhanced
3 = Full
The bug only affects Windows 10 May 2019 Update, so it does not exist in the Windows 10 October 2018 Update or earlier. The latest cumulative updates do not fix it.