Win7 64bit driver sigining issue

[HelpMePlease]

I'm sorry to repeat this, there have been multiple posts in the past but each was different and none of them seem to have solutions that work for me.

I'm trying to install 4.3.8 on my Win7 64 bit machine and I'm getting the "Oracle vm VirtualBox 4.3.8 setup wizard ended prematurely" error. When I go into the log (attached) I see the error "Signature verification failed while checking integrity of driver package 'VBoxUSBMon.inf'".

I have checked the root certificates and the root for the exe file shows as "This certificate is ok". I've updated the root certificates as suggested in Ticket 10436 and that doesn't seem to be making anything better. If the root certificate looks fine for the exe why would it throw the error for the .inf files during install?

I realize that in the past when this question has been asked it's been reported that it is a windows problem, not a VirtualBox problem, and the item has been closed off, but I feel like it would be worthwhile to try to write out a series of clear steps to try to resolve the problem since it seems to pop up over and over again. Sorry for the duplicate post in the "Discuss the 4.3.8 Release" thread, I'll delete that if you'd like since it's not very informative.

Thanks for your help and your time to look this over.

[HelpMePlease]

Some additional details, this is a fresh install, there has never been a copy of VirtualBox on this computer. Temp files have been cleared with no effect. C:\Program Files\Oracle\VirtualBox\ is empty other than the directory structure \drivers\USB\filter which is empty. I've tried unpacking the msi file and installing the VirtualBox-4.3.8-r92456-MultiArch_amd64.msi file directly and that has not worked. When I turn off USB support and networking (the imf files that throw errors) then it throws an error on VBoxDrv.inf.

I'm sure there's more I could list, please let me know what details I can add.

[mpack]

You should change the Driver Verification Signature feature so that it prompts you when there's a signature problem, instead of discarding the install.

I believe the devs are aware of a signature issue in the current release, which will be fixed asap.

[HelpMePlease]

Ok, I tried a few things that the internets showed me as potential ways to disable the signature verification:

First, I opened a command prompt as admin, and then typed "bcdedit /set nointegritychecks ON", restarted, and tried the install. No luck.

Second, I opened gpedit.msc, went to User Config/Admin Templ./System/Driver installation, enabled the option for Code signed drivers, and then set to "Ignore". Restarted, and tried the install. No luck.

I tried both of these together, no luck. BTW, you reset the first by typing "bcdedit /set nointegritychecks OFF"

I tried both of these together while in safe mode (after enabling the windows installer) and no luck.

Each time it failed on VBoxUSBMon.inf

Earlier I booted into the safe mode menu and tried to boot using "Disable Driver Signing Enforcement" and that didn't work either.

I'll keep looking for ways to get this to work, but so far windows either isn't disabling the check, or something weird is going on. Admittedly I'm on a managed network and don't have full control over my PC (i.e. there are Info Assurance settings that I know nothing about) but I was hoping that booting into safe mode would strip some of those protections away.

[HelpMePlease]

Additionally, I manually put the certificate for the inf files (VeriSign Class 3 Code Signing 2010 CA) in the trusted Root Certificates for the machine. That didn't work either, same error. Honestly I didn't think it would matter since it showed as 'OK' for the .exe file. Still, one more thing that didn't help.

[mpack]

I'm afraid that you're now straying into Windows support territory, which we can only address in a limited way on a VBox support site. Bear in mind that most free software won't be signed at all, and anyway being open source is a far better guarantee of "not malware" than any paid-for rubber stamp. If the Sony rootkit scam had come out last week on Win64 you can be damn sure it would have been correctly signed. Ditto for your NSA spyware.

[HelpMePlease]

I'm afraid that you're now straying into Windows support territory, which we can only address in a limited way on a VBox support site. Bear in mind that most free software won't be signed at all, and anyway being open source is a far better guarantee of "not malware" than any paid-for rubber stamp. If the Sony rootkit scam had come out last week on Win64 you can be damn sure it would have been correctly signed. Ditto for your NSA spyware.

I'm not worried about it, but I can't control the policies of my company. It just seems weird that there is a subset of 64 bit customers that consistently have this problem. If we could figure out the settings or group of settings that cause it then the community would be better off. And me...but it would help more than just me.

[NotOracle]

I don't care if this is a "windows issue". Your installer fails with a useless message. This is obviously a very common problem that development and support actually taunting the user base. YOUR installer is failing. Come up with a resolution. i.e. a set of steps to follow to resolve the issue. Whatever it is. I'll just use VMWare thanks.

[mpack]

How can the "VirtualBox installer fail with a useless message"? VirtualBox doesn't have an installer for Windows hosts. The installer used is the standard Windows one - MSI. If you have a problem with the error messages which MSI produces then go raise the matter with Microsoft.

You really should do some research before leaving such messages, as joining up to post an ignorant rant just makes you look like an idiot.