virtualbox.org

I'm currently running VB 4.3.6. Each time I try to upgrade to a newer version, my VB fails to start. I tried 5.0.2 today which failed, then I tried 4.3.30 which also failed to start. I would love to be more current, but I'm not sure what the problem is. My Host is Windows7 64, and my Guest is Windows7 64 as well. I also installed the Extension pack for each version.

The VBoxStartupLog is too big to upload as single file, so I broke it up in to two separate files and attached them. Can someone tell me what settings are incorrect, or what the problem is?

Thanks!!

Valdemort wrote:The VBoxStartupLog is too big to upload as single file, so I broke it up in to two separate files and attached them.

Or you could simply have zipped the file first.

As to the error you get, it is this :-

VBoxStartup.log wrote: d28.17d8: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Windows\system32\crypt32.dll' (C:\Windows\system32\crypt32.dll): rcNt=0xc0000190
d28.17d8: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0xc0000190 'C:\Windows\system32\crypt32.dll'
d28.17d8: Fatal error:
d28.17d8: Error loading 'crypt32.dll': 1790 [C:\Windows\system32\crypt32.dll]

so you now know as much as I do about it. You could try checking the certification on that DLL, and consider why it might be involved at all.

Perhaps this thread might help: viewtopic.php?t=65056&f=6

erdeslawe wrote:Perhaps this thread might help: viewtopic.php?t=65056&f=6

Thank you. I did come across this topic earlier. I have a company machine and updates are locked down. I can't install/uninstall any updates. I also came across a patch from MS, but I can't install that either.

Is there any other way to get around this update or fix the cert.?

Thanks for your help!

What you are seeing is a security fix which was added in 4.3.14 and later versions to stop virus/malware processes to infect VirtualBox due to a security vulnerability. So there is no going back from it.
The error is that the file is not what VirtualBox expect and could have been corrupted. Many false positives have been solved but if your case is a legitimate of not legitimate file, then that's the end of the line.
This is usually caused by Antivirus or some software that patch DDLs for their own purposes (like a theme manager). If you don't have admin rights on the machine to test, then no, nothing can be done expect stay on the version you're on.

... or call on the IT people who do have the authority to fix your problem.