Opened 10 years ago
Closed 10 years ago
#13682 closed defect (duplicate)
Vbox cannot start virtual Windows10 after update of Windows 7 host
Reported by: | MacDknife | Owned by: | |
---|---|---|---|
Component: | virtual disk | Version: | VirtualBox 4.3.20 |
Keywords: | Error opening VBoxDrvStub | Cc: | |
Guest type: | Windows | Host type: | Windows |
Description
Hi! Everything was working fine (new installation) until my Windows 7 64 bit Pro did an update today (10 Dec., about 19:00). After it was finished I tried to start Windows 10 again, but received an error (excerpt from log file): 298.19a0: supR3HardNtEnableThreadCreation: a58.1c90: System32: \Device\HarddiskVolume2\Windows\System32 a58.1c90: WinSxS: \Device\HarddiskVolume2\Windows\winsxs a58.1c90: KnownDllPath: C:\Windows\system32 a58.1c90: supR3HardenedVmProcessInit: Opening vboxdrv stub... a58.1c90: Error opening VBoxDrvStub: STATUS_OBJECT_NAME_NOT_FOUND a58.1c90: supR3HardenedWinReadErrorInfoDevice: NtCreateFile -> 0xc0000034 a58.1c90: Error -101 in supR3HardenedWinReSpawn! (enmWhat=3) a58.1c90: NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND (0 retries) _ I then deleted and uninstalled everything, removed all traces with Ccleaner and tried again. Same result. I can create the fixed harddisk, but it apparently cannot start it. I don't even get to install Windows 10. I have not installed VirtualBox in the default path, but in a folder on my D: drive. As I said this was not a problem before the update. I will attach the log file.
I hope this is a personal error and not a public problem, otherwise you guys are in for a busy time... regards, MacDknife
Attachments (1)
Change History (3)
by , 10 years ago
Attachment: | VBoxStartup.log added |
---|
comment:1 by , 10 years ago
HI Mac
this is a public Problem that comes with the Windowas Update KB3004394. I fixed it by removing the mentioned Update blocked it and the reinstalled the VMBox.
I hope the Oracle guys fix it and give us an update.
Micha
comment:2 by , 10 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Duplicate of #13677 and no, it's not a VirtualBox bug but a bug of this Windows update, at least how it looks now.
VirtualBox log file