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