Page 1 of 1
4.3.26 VM won't start
Posted: 16. Apr 2015, 15:52
by Valdemort
I tried to upgrade VirtualBox from VirtualBox-4.3.12-93733. I read through some of the forums of versions between 4.3.12 and 4.3.26 to see if I could identify a problem. One article mentioned Windows Update causing a security problem in an earlier version. I can't seem to find that post now, but the KB update that was referenced as the issue is not on my host. I also read that it could have been a bad install. I uninstalled 4.3.26 and re-installed running as administrator. It still fails.
Host - Windows7 64
Guest - Windows7 64
I have attached a screenshot of the error, and my startup log. If I've missed something else I should check or try, point me to the thread and I follow those steps to see if the problem is corrected. Thanks for your help.
Re: 4.3.26 VM won't start
Posted: 16. Apr 2015, 22:58
by dR.
Hi,
it seems to me your virtual machine is corrupted. Can you try to create a new one and see if that works to see what we're working with?
Cheers!
Re: 4.3.26 VM won't start
Posted: 16. Apr 2015, 23:18
by Perryg
Actually your host is where the issue is. I know you said that you checked for a bad update from MS, but there was one this month as well. It messes with the verify process and needs to be removed until they get the fix. You need to look through the windows as host forum to find the kb number as I don't know what it is.
Re: 4.3.26 VM won't start
Posted: 17. Apr 2015, 00:40
by dR.
His problem does not afect ntdll as the windows update one does.
Re: 4.3.26 VM won't start
Posted: 17. Apr 2015, 01:07
by Perryg
Alright then good luck.
Re: 4.3.26 VM won't start
Posted: 17. Apr 2015, 13:35
by scottgus1
At the very bottom of the startup log there's this line:
Code: Select all
1740.1a4c: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Windows\system32\crypt32.dll' (C:\Windows\system32\crypt32.dll): rcNt=0xc0000190
Seems to indicate the Windows crypt32.dll is bad. Check for recent Windows updates that altered crypt32.dll and uninstall them, then see if Virtualbox runs.
The Windows update Perry mentioned that broke things this week (KB3045999) affected ntdll.dll. Maybe that update or another one affects crypt32.dll?
PS unless you have to update, perhaps because you want to run a most recent version of Linux or need a new feature, and you really need to run Virtualbox instead of troubleshooting, you don't have to update after 4.3.12, which runs Windows 8.1 and 10 preview. You just need to make sure your host doesn't have any malware on it, and you'll be OK. Browse and click safely on your host, and you'll stay OK.