Opened 6 years ago
Last modified 6 years ago
#18309 new defect
VirtualVox 6.0.0-127566 will not start VMs under latest Windows 10 update
Reported by: | Richard Sharpe | Owned by: | |
---|---|---|---|
Component: | VM control | Version: | VirtualBox 6.0.0 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | other |
Description
When trying to start a VM it fails with:
The virtual machine 'CentOS 7.5' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\${user}\VirtualBox VMs\CentOS 7.5\Logs\VBoxHardening.log'.
Looking in that file I find:
2598.95c: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume3\Program Files\Oracle\VirtualBox' 2598.95c: System32: \Device\HarddiskVolume3\Windows\System32 2598.95c: WinSxS: \Device\HarddiskVolume3\Windows\WinSxS 2598.95c: KnownDllPath: C:\WINDOWS\System32 2598.95c: supR3HardenedVmProcessInit: Opening vboxdrv stub... 2598.95c: supR3HardenedWinReadErrorInfoDevice: 'Unknown image file \Device\HarddiskVolume3\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe at 00007ff702ae0000. (rc83Exp=-91)' 2598.95c: Error -5633 in supR3HardenedWinReSpawn! (enmWhat=3) 2598.95c: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5633 (0xffffe9ff) (rcNt=0xe986e9ff) VBoxDrvStub error: Unknown image file \Device\HarddiskVolume3\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe at 00007ff702ae0000. (rc83Exp=-91) 41f8.421c: supR3HardenedWinCheckChild: enmRequest=2 rc=-5633 enmWhat=3 supR3HardenedWinReSpawn: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5633 (0xffffe9ff) (rcNt=0xe986e9ff) VBoxDrvStub error: Unknown image file \Device\HarddiskVolume3\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe at 00007ff702ae0000. (rc83Exp=-91) 41f8.421c: Error -5633 in supR3HardenedWinReSpawn! (enmWhat=3) 41f8.421c: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5633 (0xffffe9ff) (rcNt=0xe986e9ff) VBoxDrvStub error: Unknown image file \Device\HarddiskVolume3\Program Files\Oracle\VirtualBox\VirtualBoxVM.exe at 00007ff702ae0000. (rc83Exp=-91)
Here is the info from that file about my version of Windows 10. It was updated last Tuesday.
41f8.421c: Log file opened: 6.0.0r127566 g_hStartupLog=0000000000000070 g_uNtVerCombined=0xa0456300 41f8.421c: \SystemRoot\System32\ntdll.dll: 41f8.421c: CreationTime: 2019-01-10T02:36:52.431995500Z 41f8.421c: LastWriteTime: 2019-01-10T02:36:52.457392000Z 41f8.421c: ChangeTime: 2019-01-10T03:35:31.327390500Z 41f8.421c: FileAttributes: 0x20 41f8.421c: Size: 0x1e7010 41f8.421c: NT Headers: 0xe0 41f8.421c: Timestamp: 0xe8b54827 41f8.421c: Machine: 0x8664 - amd64 41f8.421c: Timestamp: 0xe8b54827 41f8.421c: Image Version: 10.0 41f8.421c: SizeOfImage: 0x1ed000 (2019328) 41f8.421c: Resource Dir: 0x17d000 LB 0x6ea08 41f8.421c: [Version info resource found at 0xd8! (ID/Name: 0x1; SubID/SubName: 0x409)] 41f8.421c: [Raw version resource data: 0x17d0f0 LB 0x380, codepage 0x0 (reserved 0x0)] 41f8.421c: ProductName: Microsoft® Windows® Operating System 41f8.421c: ProductVersion: 10.0.17763.194 41f8.421c: FileVersion: 10.0.17763.194 (WinBuild.160101.0800) 41f8.421c: FileDescription: NT Layer DLL 41f8.421c: \SystemRoot\System32\kernel32.dll: 41f8.421c: CreationTime: 2018-09-15T07:28:44.342269900Z 41f8.421c: LastWriteTime: 2018-09-15T07:28:44.342269900Z 41f8.421c: ChangeTime: 2019-01-10T03:35:31.154027900Z 41f8.421c: FileAttributes: 0x20 41f8.421c: Size: 0xb1380
Change History (2)
comment:1 by , 6 years ago
comment:2 by , 6 years ago
Richard,
It's usually better and faster, if issues get first addressed in the VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".
Please read really carefully the following FAQ: Diagnosing VirtualBox Hardening Issues for some guidelines/ideas.
Hmmmm, those messages got a bit screwed up there.
The error message is:
The Info from the start of the log file is: