Cumulative Update Sent to the Latest Windows 10 1903 Has Caused RASMAN Service to Stop Working
Microsoft has been trying to get over the Windows 10 October 2018 Update fiasco. While the overall update process of the latest version 1903 has been smooth and free of any major bugs, some little issues keep propping up.
The cumulative update delivered to the operating system on May 29 (KB4497935, Build 18362.145) brought in a potential issue with the Remote Access Connection Manager service (RASMAN) that could stop working for some users, giving error 0xc0000005.
RASMAN service may stop working and result in the error “0xc0000005”
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”.
Microsoft clarifies that the issue only occurs when a VPN profile is configured as an Always On VPN (AOVPN) connection on Windows 10 1903. “This does not affect manual only VPN profiles or connections,” the Windows maker said.
Microsoft has also provided a workaround to the issue, but as for the fix, the company said it’s working on a resolution and will deliver it through an upcoming update.
Here’s the temporary workaround:
Workaround: To mitigate this issue, use one of the steps below, either the group policy step or the registry step, to configure one of the default telemetry settings:
Set the value for the following group policy settings:
- Group Policy Path: Computer Configuration\Administrative Templates\Windows Components\Data Collection and Preview Builds\Allow Telemetry
- Safe Policy Setting: Enabled and set to 1 (Basic) or 2 (Enhanced) or 3 (Full)
Or set the following registry value:
Value: 1, 2 or 3
Note You may need to restart the Remote Access Connection Manager service after setting the Group Policy or registry key.