Oh noes the dreaded NtCreateFile failed :-(

Discussions related to using VirtualBox on Windows hosts.
Post Reply
rasiel
Posts: 7
Joined: 22. Aug 2015, 03:39

Oh noes the dreaded NtCreateFile failed :-(

Post by rasiel »

Halp!

Last night I bit the bullet and upgraded to Win10 and for good measure to 5.0.2 w/ extensions. No problem in getting VirtualBox to open but it won't open any of my old hosts, all failing with:
00.jpg
00.jpg (64.26 KiB) Viewed 4950 times
Untitled-1.jpg
Untitled-1.jpg (74.33 KiB) Viewed 4950 times
I've spent hours looking for a solution in other threads but no joy. I have:

- Right-clicked VBoxDrv.inf and installed
- Run VirtualBox as admin and also in Win7 compatibility mode
- Created a clone of an old VM to see if somehow it would be imbued with the magics of the new build
- Attempted to relaunch same VM three times in a row (some users were reporting the 4th attempt worked)
- Tried guests in Linux, WinXP and MacOS flavors, all fail to launch with same error
- Deleted the log files
- Tried sc start vboxdrv from the root in a cmd prompt (get access is denied)

Have not yet tried:

- Rolling back to Win8.1
- Rolling back to VB 4.3.2

Host is a fairly high end Intel build with plenty of resources. No hardware changed since before the upgrade. Not that it makes any difference but one of the VMs contains a critical database with scientific data and is being used as a publicly accessible testbed so I'm quite distressed and crossing every finger and toe that this thing's not cooked. For what it's worth, the log file is huge but near the ending is:

1f0c.2714: supR3HardenedVmProcessInit: Opening vboxdrv stub...
1f0c.2714: supR3HardenedWinReadErrorInfoDevice: 'RTLdrOpenWithReader failed: -626 (Image='\Device\HarddiskVolume6\Windows\S'
1f0c.2714: Error -626 in supR3HardenedWinReSpawn! (enmWhat=3)
1f0c.2714: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -626 (0xfffffd8e) (rcNt=0xe986fd8e)
VBoxDrvStub error: RTLdrOpenWithReader failed: -626 (Image='\Device\HarddiskVolume6\Windows\S
12ec.288: supR3HardenedWinCheckChild: enmRequest=2 rc=-626 enmWhat=3 supR3HardenedWinReSpawn: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -626 (0xfffffd8e) (rcNt=0xe986fd8e)
VBoxDrvStub error: RTLdrOpenWithReader failed: -626 (Image='\Device\HarddiskVolume6\Windows\S
12ec.288: Error -626 in supR3HardenedWinReSpawn! (enmWhat=3)
12ec.288: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -626 (0xfffffd8e) (rcNt=0xe986fd8e)
VBoxDrvStub error: RTLdrOpenWithReader failed: -626 (Image='\Device\HarddiskVolume6\Windows\S


Please, if you have any ideas on how to get this thing running again I'd be *hugely* indebted!

Many, many thanks,

Ras
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Oh noes the dreaded NtCreateFile failed :-(

Post by mpack »

The first thing to do is - stop thrashing. It will only sink you deeper. Don't do anything unless you know in advance what the result will be.

A partial log isn't much use to us. Zip up the complete VBoxStartup.log and attach the zip here.
rasiel
Posts: 7
Joined: 22. Aug 2015, 03:39

Re: Oh noes the dreaded NtCreateFile failed :-(

Post by rasiel »

Alright, done!
Logs.zip
(3.65 KiB) Downloaded 73 times
Thank you for taking a stab at it :-)

Ras
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Oh noes the dreaded NtCreateFile failed :-(

Post by mpack »

I didn't appreciate that your host is Windows 10. VirtualBox does not currently support Windows 10 hosts. However you can try the latest test build - and see the "Windows 10 hosts" sticky at the top of this forum. Until support for Win10 hosts is formally announced we would prefer to limit the sprawl of these topics.
rasiel
Posts: 7
Joined: 22. Aug 2015, 03:39

Re: Oh noes the dreaded NtCreateFile failed :-(

Post by rasiel »

I'm sorry my choice of OS displeases you, however this did the trick which very much does please me!

At first it failed with an error 1912 (something about a driver mismatch). I uninstalled and reinstalled and the VMs came up without a fuss.

Thank you!
Post Reply