From 4db0f53a67cbf44ec663c8d4ad13cef2e21e0889 Mon Sep 17 00:00:00 2001 From: John Liu <49762389+ShenLanJohn@users.noreply.github.com> Date: Fri, 28 Jun 2019 18:06:59 -0700 Subject: [PATCH] update issue for 1903 (#612) (#613) --- windows/release-information/status-windows-10-1903.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/windows/release-information/status-windows-10-1903.yml b/windows/release-information/status-windows-10-1903.yml index 85e00c90d8..2017e3b5d6 100644 --- a/windows/release-information/status-windows-10-1903.yml +++ b/windows/release-information/status-windows-10-1903.yml @@ -70,6 +70,7 @@ sections:
Details | Originating update | Status | History |
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”. 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. Affected platforms
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:
Or set the following registry value: SubKey: HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows\\DataCollection Setting: AllowTelemetry Type: REG_DWORD 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. Next Steps: We are working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 18362.145 May 29, 2019 KB4497935 | Mitigated | Last updated: June 28, 2019 05:01 PM PT Opened: June 28, 2019 05:01 PM PT |
Event Viewer may close or you may receive an error when using Custom Views When trying to expand, view, or create Custom Views in Event Viewer, you may receive the error, \"MMC has detected an error in a snap-in and will unload it.\" and the app may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs. Built-in views and other features of Event Viewer should work as expected. Affected platforms:
Resolution: This issue was resolved in KB4501375. Back to top | OS Build 18362.175 June 11, 2019 KB4503293 | Resolved KB4501375 | Resolved: June 27, 2019 10:00 AM PT Opened: June 12, 2019 11:11 AM PT |