If you are running Windows 10 May 2019 update on your PC you may have received a cumualtive update on Tuesday with Windows 10 Build 18362.239 aka KB4507453. This cumulative update brings lots of fixes and improvements along with itself buy may also cause some issues as listed by Microsoft in the known issues list.
In fact there are four known issues listed by Microsoft for KB4507453 and three of those issues may result in errors 0x80070002, 0xc0000005 & 0xc0000001. Windows Sandbox may still fail with “ERROR_FILE_NOT_FOUND (0x80070002) while the Remote Access Connection Manager (RASMAN) service may stop working and you may receive the error “0xc0000005”.
Read the known issues in detail below and do let us know if you are facing any such issue in comments below.
|Windows Sandbox may fail to start with “ERROR_FILE_NOT_FOUND (0x80070002)” on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903.
|Microsoft is working on a resolution and will provide an update in an upcoming release.
The Remote Access Connection Manager (RASMAN) service may stop working and you may receive the error “0xc0000005” on devices where the diagnostic data level is manually configured to the non-default 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.
|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:
Value: 1, 2 or 3
Note If the Remote Access Connection Manager service is not running after setting the Group Policy or registry key, you will need to manually start the service or restart the device.
We are working on a resolution and estimate a solution will be available in late July.
|After installing this update, opening or using the Window-Eyes screen reader app may result in an error and some features may not function as expected.
Note Users who have already migrated from Window-Eyes to Freedom Scientific’s other screen reader, JAWS, should not be affected by this issue.
|We are working on a resolution and will provide an update in an upcoming release.
|Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) or System Center Configuration Manager (SCCM) may fail to start with the error “Status: 0xc0000001, Info: A required device isn’t connected or can’t be accessed” after installing this update on a WDS server.
|For mitigation instructions, see KB4512816.
We are working on a resolution and will provide an update in an upcoming release.