Microsoft's Windows 10 Version 1903 was thought to be a huge improvement from Version 1809, in terms of better user experience post update installation. However, only weeks after its delivery the May 2019 Update started rearing its ugly head, which its maker has admitted to.
The specific problem concerns the Remote Access Connection Manager Service (RASMAN) that according to Microsoft, could potentially crash in the aftermath of the May 29 cumulative update, tagged as KB4497935. Per its investigation, the company said that RASMAN is likely to stop working when a VPN Profile has been set as Always On VPN (AOVPN).
This means users with manual only VPN configurations will not be affected by the problem, which Microsoft classified as "Error 0xc0000005." For users' reference, the problem has been observed presently in Windows 10 1903, Build 18362.145.
While the issue is far from paralyzing and prevalent, Microsoft said users could mitigate the impact by implementing some workaround. This temporary fix is being offered in the absence of a permanent solution that likely will be deployed in the next batch of cumulative updates.
For now affected users can follow the instructions below, courtesy of WCCFTech:
To fix this issue, you can set a new 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)
The alternative is to make the following changes to Registry:
- SubKey: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection
- Setting: AllowTelemetry
- Type: REG_DWORD
- Value: 1, 2 or 3
For the full reconfiguration to take effect, Microsoft advises users to restart the RASMAN.
Now in another form of a coming clean statement, the Windows maker finally owned up to a monumental faux pas that could possibly lead to a system meltdown. According to the company: "Starting in Windows 10, version 1803, Windows no longer automatically backs up the system registry to the RegBack folder."
The reason for the move was to reduce the OS' footprint on a system, but the claim does not make sense as Forbes said Registry Backup only takes a maximum of 100MB, which obviously cloaks the feature's importance.
"Backing up a registry is a crucial last line of defense for many businesses and everyday users. Should a Windows System Restore point fail, barring the use of third-party software, the registry backup is all you have," the report said in underscoring the significance of Microsoft's misstep.
Forbes added mistakes like this only contribute to the distrust that is believed to prevail on millions of Windows 10 users. To put this into perspective, up to 800 million users could be affected by the OS bug that Microsoft itself has inadvertently caused.
