Not Signed with the Build Certificate error after installing 5.1.12 r112440

[Shaun Collier]

I have just installed VirtualBox 5.1.12 r112440 on a Windows host running Windows 10 Professional, and when trying to run a VB image for the first time I get this error:

VirtualBox - Error In supR3HardenedWinReSpawn NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5657 (0xffffe9e7) (rcNt=0xe986e9e7) VBoxDrvStub error: Not signed with the build certificate.: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe (rc=-5657) Make sure the kernel module has been loaded successfully.

VERR_SUP_VP_NOT_SIGNED_WITH_BUILD_CERT (-5657) - The image is required to be signed with the same certificate as the rest of VirtualBox.

Previous to installing this version, all VirtualBox images have worked perfectly fine, with the only change to my machine between last night and this morning being that I've installed the new version of VirtualBox.

[Shaun Collier]

HardeningLog

[Shaun Collier]

VBoxLog

[ci-zephyurus]

I have the same issue under Windows 10. I think the packaging step forgot to sign the executable or something like that. Reverting to 5.1.10 for now...

[rsalama]

Had the same error today after updating to 5.1.12 from 5.0.28. Installing 5.1.10 resolved it.

[GasanovIE]

Same happened to me after upgrading from 5.1.10 to 5.1.12 on Windows 10 x64 host, but everything is okay after a clean 5.1.12 install (i.e. without any previous version installed before).

[KarenArzumanyan]

And I confirm. It was the same problem. After uninstall VirtualBox 5.1.12, restart Windows 10 and reinstall VirtualBox 5.1.12, the problem is fixed.

[keremer]

Same error here over Windows 10. The error happened after upgrading form 5.1.10. Unistall - reboot - Reinstall 5.1.12 solved the problem. No need to downgrade to 5.1.10. It seems that there's a small logical error in the code. It does not do what it should do during upgrade but does it during clean install ..

[Mike-M]

Same issue on Windows 10.

342c.1d40: supR3HardNtEnableThreadCreation:
1f7c.3458: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume4\Program Files\Oracle\VirtualBox'
1f7c.3458: System32:  \Device\HarddiskVolume4\Windows\System32
1f7c.3458: WinSxS:    \Device\HarddiskVolume4\Windows\WinSxS
1f7c.3458: KnownDllPath: C:\WINDOWS\System32
1f7c.3458: supR3HardenedVmProcessInit: Opening vboxdrv stub...
1f7c.3458: supR3HardenedWinReadErrorInfoDevice: 'Not signed with the build certificate.: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe'
1f7c.3458: Error -5657 in supR3HardenedWinReSpawn! (enmWhat=3)
1f7c.3458: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5657 (0xffffe9e7) (rcNt=0xe986e9e7)
VBoxDrvStub error: Not signed with the build certificate.: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
342c.1d40: supR3HardenedWinCheckChild: enmRequest=2 rc=-5657 enmWhat=3 supR3HardenedWinReSpawn: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5657 (0xffffe9e7) (rcNt=0xe986e9e7)
VBoxDrvStub error: Not signed with the build certificate.: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe
342c.1d40: Error -5657 in supR3HardenedWinReSpawn! (enmWhat=3)
342c.1d40: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5657 (0xffffe9e7) (rcNt=0xe986e9e7)
VBoxDrvStub error: Not signed with the build certificate.: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe

[ci-zephyurus]

Unfortunately, there is something subtle going on, at least on my machine.

Uninstalled 5.0.10. Rebooted. Installed 5.0.12. Rebooted. But upon starting, again I got the not signed error. Uninstalled. Rebooted. Installed 5.0.12 again. Rebooted just in case. Again, I get the error about not signed error.

Revered and using 5.0.10 for now: but this version may have a few issues with kernel 4.8.0 which Debian's testing repository provides.

TIA

[ci-zephyurus]

BTW, this may be hard to believe. But is it possible that this could be experienced by someone who has more than one hard drive and file images that are mounted are scattered across different disk images, etc.? Just a shot in the dark.

[Mike-M]

Replying to Mike-M:

I have fixed this issue with actions as below:

1. Uninstall VirtualBox completely
2. Reboot
3. Install VirtualBox 5.1.12

[mattmichielsen]

Doing a "Repair" through "Programs and features" worked for me without uninstalling, etc. I did have to reboot (as prompted) after the repair.

[algot]

I still have this error on new VirtualBox 5.1.14-112924.

Repairing VB can't be performed because installer requires "VirtualBox-5.1.14-r112924-MultiArch_amd64.msi" file which is absent in my temp directory.

[Frank Mehnert]

algot, did you try to uninstall VBox completely, reboot the host then install VBox?

[algot]

Replying to frank:

algot, did you try to uninstall VBox completely, reboot the host then install VBox?

I reinstalled VBox completely and 5.1.14 version is installed correctly.

[ci-zephyurus]

HOST OS: Windows 10 64-bit

I am not sure if this applies to other users who experience this issue. With 5.1.12, I could not get to make it work even though I removed VBox completely and reinstalled it.

With 5.1.14, I did the following and it works, but with a twist.

If you have once installed VBox under non-default drive under windows, you may want to check this out.

DETAILS:

I noticed that in the log that vboxdrv seems to be the binary that has the bad signature issue. On my PC, I once installed VBox binary under a different drive. That is, right now, VBox binary is under C: drive (SSD), but once it was on a different drive L: (an ordinary hard disk) to save usage on SSD. I noticed that there is still a vboxdrv.sys binary under L:. (Maybe incorrect removal, etc.)

The day before, I installed 5.1.14 under C: drive, but still I get the bad signature error. On a hunch, after REPAIRING the installation, which is said to fix the issues for some, (now I got a different error when I tried to run the guest image), I REBOOTED the host OS and then I REMOVED the vboxdrv.sys under L: drive. This removal may have been the crux of the solution in my case, but I have no idea. Now, I could run 5.1.14 successfully.

[apraetor]

Does a work-around exist for this? Our university has been teaching students to install VirtualBox as a means of practicing with Linux virtual machines at home; this semester just started and effectively the entire class is unable to run VirtualBox at this time. Would appreciate any insight or help that can be offered. Thank you.

[Truandale]

Replying to mattmichielsen:

Doing a "Repair" through "Programs and features" worked for me without uninstalling, etc. I did have to reboot (as prompted) after the repair.

Thank you. Your advice is working fine. And reinstalling is working fine too.

[Frank Mehnert]

In general this error can only happen if there is a leftover from an old vboxdrv.sys driver of an older VirtualBox installation. This could be a bug in the VirtualBox installer or in the user environment. The general procedure to fix such problems is to unstall VirtualBox (your VMs will NOT vanish), then reboot, then re-install VirtualBox.

Before you re-install VirtualBox you should double-check if there are no old vboxdrv.sys drivers active, perhaps from an ancient VirtualBox installation. If you find such a driver, remove it and reboot the host again.

driverquery

should list all active drivers. If VirtualBox is not installed but the list contains VBoxDrv then make sure to remove any vboxdrv.sys instance you find on your system. Also make sure that VBoxNetAdp / VBoxNetFlt / VBoxNetLwf are not installed either.

Finally re-install VirtualBox.

[garg]

"Repair" through "Programs and features" worked fine without uninstalling, etc. You have to reboot (as prompted) after the repair.

[Frank Mehnert]

Thanks. Closing this ticket.

[HackerBaloo]

upgrade log 5.1.8 to 5.1.30

[HackerBaloo]

I can still repeat this problem on Windows 10 upgrading from 5.1.8 to 5.1.30, can it really be considered fixed, if the upgrade requires a repair and reboot after an upgrade? See attached log above

[HackerBaloo]

Replying to HackerBaloo:

I can still repeat this problem on Windows 10 upgrading from 5.1.8 to 5.1.30, can it really be considered fixed, if the upgrade requires a repair and reboot after an upgrade? See attached log above

However, I should also say that I can't reproduce it on Windows 7

[HackerBaloo]

I have found out that even if you first uninstall 5.1.8 and reboot before installing 5.1.30 you still get this need to reinstall and reboot. That got me thinking about what could be left after uninstalling. So I checked the drivers. After uninstalling and rebooting 5.1.30 on Windows 7 I still have: Driver: VBoxNetAdp: Stopped Driver: VBoxNetFlt: Stopped

[HackerBaloo]

Tried install of 5.1.8 on clean Windows Server 2012 R2 build 9600(German, just to test on none english OS) and then uninstall and reboot VBoxNetAdp was left behined. will test the same thing with the latest 5.2

[HackerBaloo]

Same result with 5.2.0 on same, but reinstalled, clean Server 2012.

[GA]

Same error for me on windows 10 (latest update as of today).

• Uninstalled my previous 5.1.8 VBox.
• Then installed latest 5.2.10 (installer run as administrator).
• No Dice :-( Some certificate build error.

Then searched and came upon this discussion and this time, I did a *REBOOT* before reinstalling latest Vbox. Worked !! Feels like going back to the time of windows 95 when we had to reboot for every single thing.

[Socratis]

Replying to GA:

Feels like going back to the time of windows 95 when we had to reboot for every single thing.

It's usually not required, that's why you don't get a prompt to reboot. I've never had the need to reboot for example, and I've done hundreds and hundreds of installations. I upgrade/downgrade all the time, for testing purposes, so I up/downgrade 2-4 times daily.

So, I'd say that something peculiar exists about your system that requires the reboot. You *are* installing kernel drivers after all, not a Notepad++ type of application... ;)

[Twisted Lucidity]

This also affects upgrade from 6.0.4 to 6.0.6 on Windows 10. A repair install and reboot seems to resolve it.

I realise that the fault probably lies with Windows being dreadful, but I think the installer needs to be a lot more defensive to shield users from these problems. e.g. if VboxDrvStub can't be unloaded, then report that Windows is at fault and suggest a uninstall/reboot/install or other relevant action.

[GA]

Replying to Twisted Lucidity:

This also affects upgrade from 6.0.4 to 6.0.6 on Windows 10. A repair install and reboot seems to resolve it.

Got the same error today (6.0.4 upgrading to 6.0.6). Repair and reboot did not work for me. What worked for me was:

• Complete uninstall of VBox.
• Reboot
• Reinstall VBox

[Mored1984]

Replying to GA:

Replying to Twisted Lucidity:

This also affects upgrade from 6.0.4 to 6.0.6 on Windows 10. A repair install and reboot seems to resolve it.

Got the same error today (6.0.4 upgrading to 6.0.6). Repair and reboot did not work for me. What worked for me was:

• Complete uninstall of VBox.
• Reboot
• Reinstall VBox

Same error her, I will follow your step to fix these bugs.

[denifednu]

Replying to Twisted Lucidity:

This also affects upgrade from 6.0.4 to 6.0.6 on Windows 10. A repair install and reboot seems to resolve it.

Thanks for this. Upgrading from 6.0.4 to 6.0.8 on Windows 10 had same issue for me. A repair install and reboot resolved it.

[klieber]

This is also affecting upgrading from 6.0.0 to 6.0.20 on Windows 10. I will try the

Uninstall of Vbox Reboot Reinstall VBox

I successfully fixed the issue by, as what others did, Complete uninstall of Vbox 6.0.0, Reboot, reinstall Vbox 6.0.20 Thanks all!

[i3v]

Same on Windows 10 after updating from 6.x.y (don't really remember the exact version) to 7.0.8 r156879.

Maybe that's somehow related to the fact that I've decided to install some Windows update (that asked me to reboot) just after Virtual Box installer asked me to reboot.

Fixed by uninstalling Virtual Box and installing it again.