Is Copilot the best AI companion out there? Help us find out by answering a couple of quick questions!
Around a month ago Microsoft released KB4497935 to Windows 10 users, taking the OS to Build 18362.145. The update addressed the issue with drive letter re-assignment, some networking and DNS issues and a few other security and bug issues.
Unfortunately, despite testing in the slow and release preview ring the Cumulative Update also introduced an issue which Microsoft just acknowledged.
On their issues page Microsoft reports that for some Windows 10 users on the May 2019 update, Remote Access Connection Manager (RASMAN) service may stop working and users may receive the error “0xc0000005” when devices are manually configured to the non-default telemetry setting of 0.
Users 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”.
The 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.
Microsoft is working on a fix, but in the meantime, the following mitigation procedure should help:
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.
Read more at Microsoft here.