Windows 10 users might need pest control or in technical terms a “fix” for what is now a newly discovered bug called RASMAN or Remote Access connection Manager bug. The bug seemingly affects only the version 1903 of Windows 10 and not any older versions.
What does Remote Access connection Manager or the RASMAN bug Do?
RASMAN basically is a software that manages VPNs and Windows connections to the outside world or to the more commonly known internet.
The bug will consequently affect this part of Windows functioning. Microsoft even went on their support page and said that RASMAN would stop working and an error “0xc0000005” will be displayed. It has also been noted that this bug seems to be seen only on PCs where the VPN is pegged as always on or “AOVPN” instead of manual only VPN connections.
Microsoft says that they are working on a fix as we speak or as I type and will most probably be available later this month.
At present there are no real estimates of the range of this bug. But according to Forbes the number of users affected could range in the 50 million range.
The RASMAN bug only affects user’s VPN connections. The bug was first discovered in the recent Windows 10 May 2019 Update. Remote Access Connection Manager typically runs in the background to ensure smooth functioning for the always – on – kinda – VPN. Besides the always – on variety, even VPNs with dial up connections may be impacted.
There are many people worldwide who use a VPN connection, so the number of users affected is likely to be huge. Running in the millions.
Besides getting the error mentioned by Microsoft, you may also see error in the application section in windows Logs coming with Event ID 1000. This will reference an error “svchost.exe_RasMan” and you may also see “rasman.dll”.
As mentioned earlier only users with an always on VPN connection will be affected. So, this is most likely going to affect users in enterprises or in countries subject to strict government control or high levels of censorship.
There is also a workaround for the issue by tweaking a few settings. First you have to go to Computer configuration, then Administrative templates. When there, go on to windows components and then data collection and preview builds. There choose allow telemetry and then change the value of safe policy to enabled and set it to either 1 which is basic or 2 enhanced or 3 full.
The alternate route involves the registry file. If you’re someone comfortable with doing this then locate the value for SubKey
HKEY_LOCAL_MACHINE>SOFTWARE>Policies>Microsoft>Windows>dataCollection and then you can change the telemetry settings to 1, 2 or 3 depending on whether you want it as basic, enhanced or full.
If, however you don’t like messing around with registry files or group policy settings then you can always wait for the Windows fix.
What does Remote Access connection Manager or the RASMAN bug Do?
RASMAN basically is a software that manages VPNs and Windows connections to the outside world or to the more commonly known internet.
The bug will consequently affect this part of Windows functioning. Microsoft even went on their support page and said that RASMAN would stop working and an error “0xc0000005” will be displayed. It has also been noted that this bug seems to be seen only on PCs where the VPN is pegged as always on or “AOVPN” instead of manual only VPN connections.
A Fix for the RASMAN Bug in Store?
Microsoft says that they are working on a fix as we speak or as I type and will most probably be available later this month.
At present there are no real estimates of the range of this bug. But according to Forbes the number of users affected could range in the 50 million range.
Who’s Affected by the RASMAN Bug?
The RASMAN bug only affects user’s VPN connections. The bug was first discovered in the recent Windows 10 May 2019 Update. Remote Access Connection Manager typically runs in the background to ensure smooth functioning for the always – on – kinda – VPN. Besides the always – on variety, even VPNs with dial up connections may be impacted.
There are many people worldwide who use a VPN connection, so the number of users affected is likely to be huge. Running in the millions.
Besides getting the error mentioned by Microsoft, you may also see error in the application section in windows Logs coming with Event ID 1000. This will reference an error “svchost.exe_RasMan” and you may also see “rasman.dll”.
As mentioned earlier only users with an always on VPN connection will be affected. So, this is most likely going to affect users in enterprises or in countries subject to strict government control or high levels of censorship.
A Workaround?
There is also a workaround for the issue by tweaking a few settings. First you have to go to Computer configuration, then Administrative templates. When there, go on to windows components and then data collection and preview builds. There choose allow telemetry and then change the value of safe policy to enabled and set it to either 1 which is basic or 2 enhanced or 3 full.
The alternate route involves the registry file. If you’re someone comfortable with doing this then locate the value for SubKey
HKEY_LOCAL_MACHINE>SOFTWARE>Policies>Microsoft>Windows>dataCollection and then you can change the telemetry settings to 1, 2 or 3 depending on whether you want it as basic, enhanced or full.
If, however you don’t like messing around with registry files or group policy settings then you can always wait for the Windows fix.
