Be aware: Begin Windows in Safe Mode to complete any of the following steps if you are unable to access Home windows usually because of the msvbvm50.dll error. Boot your system into Safe Mode. This is brought on by a situation where the Windows working system has locked the WASServiceMsg.dll file in order that it will probably interpret messages logged within the Home windows Occasion Log. Now, click on on the Enable Login Commands box, and set up to 5 commands, as you can see in this image below. As soon as the account has been enabled, you will then need to login as the Administrator (with out a password), then attempt to run whichever program or operate that is causing the error in order to see if the problem nonetheless exists. Troubleshoot for a hardware downside if any atl.dll errors persist. The clasic problem that usually arises is: simptcp.dll is lacking, simptcp.dll not found, dll is corrupt, dll is errors and many others..