Changes between Initial Version and Version 10 of Ticket #16318
- Timestamp:
- Jan 2, 2017 10:33:02 AM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #16318 – Description
initial v10 1 I have just installed VirtualBox 5.1.12r112440 on a Windows host running Windows 10 Professional, and when trying to run a VB image for the first time I get this error:1 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: 2 2 3 --------------------------- 4 VirtualBox - Error In supR3HardenedWinReSpawn 5 --------------------------- 6 <html><b>NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5657 (0xffffe9e7) (rcNt=0xe986e9e7)<br>VBoxDrvStub error: Not signed with the build certificate.: \Device\HarddiskVolume4\Program Files\Oracle\VirtualBox\VirtualBox.exe (rc=-5657)</b><br/><br/>Make sure the kernel module has been loaded successfully.<br><br><!--EOM-->where: supR3HardenedWinReSpawn 7 what: 3 8 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. 9 </html> 10 --------------------------- 11 OK 12 --------------------------- 3 ''!VirtualBox - Error In supR3HardenedWinReSpawn 4 NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5657 (0xffffe9e7) (rcNt=0xe986e9e7) 5 VBoxDrvStub error: Not signed with the build certificate.: \Device\HarddiskVolume4\Program Files\Oracle\!VirtualBox\!VirtualBox.exe (rc=-5657) 6 Make sure the kernel module has been loaded successfully.'' 13 7 14 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. 8 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. 9 10 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.
