VirtualBox fails to launch any virtual machine: NtCreateFile failed

[Sose]

Please see ​https://forums.virtualbox.org/viewtopic.php?f=6&t=67355#. When I try and select a virtual machine and click Start the attached error message shows up saying:

NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5600 (0xffffea20)(rcNt=0xe986ea20) VBoxDrvStub error: ntdll.dll: 7981 difference between 0x300c and 0x4fff in #1 (.text., first: 4c != 1f (rc=-5600)

Host is Windows 8.1 Professional 64-bit. Tried with multiple guests and the same issue occurs. Problem occurred after installing Windows updates. I have attached a list of recently installed Windows updates.

[Sose]

List of recently installed Windows updates

[Sose]

Error message

[Sose]

VBox Startup Log

[Sose]

VBox.log

[--force]

For Windows 8 Pro 64-bit (6.2, build 9200), problem goes away after rolling back the following updates:

​https://support.microsoft.com/en-us/kb/3049508 ​https://support.microsoft.com/en-us/kb/3038314

Rolling back all of the above might not be required.

[linkerstorm]

I have the same problem and opened a bug (14051).

In my case, rolling back the KB3045999 update has solved the issue.

[dww]

I'm experiencing a similar issue with Windows 7

[Scootin159]

Several other people (myself included) have reported the same issue with Windows 8 here as well: ​https://forums.virtualbox.org/viewtopic.php?f=6&t=66639&start=45#p318687

In all cases, uninstalling KB3045999 corrected the issue

[Sose]

Replying to Scootin159:

Several other people (myself included) have reported the same issue with Windows 8 here as well: ​https://forums.virtualbox.org/viewtopic.php?f=6&t=66639&start=45#p318687

In all cases, uninstalling KB3045999 corrected the issue

I'm not trying to nitpick here but uninstalling KB3045999 still leaves a Windows security vulnerability that allows escalation of privileges in certain circumstances as referenced in ​https://support.microsoft.com/en-us/kb/3045999. I wouldn't necessarily write this issue off as having been solved by any means. I do thank those who found the workaround though as it's saved me for the time being.

[Sose]

Replying to Scootin159:

Several other people (myself included) have reported the same issue with Windows 8 here as well: ​https://forums.virtualbox.org/viewtopic.php?f=6&t=66639&start=45#p318687

In all cases, uninstalling KB3045999 corrected the issue

BTW Scootin, thanks for the additional thread!

[Scootin159]

Replying to Sose:

I'm not trying to nitpick here but uninstalling KB3045999 still leaves a Windows security vulnerability that allows escalation of privileges in certain circumstances as referenced in ​https://support.microsoft.com/en-us/kb/3045999. I wouldn't necessarily write this issue off as having been solved by any means. I do thank those who found the workaround though as it's saved me for the time being.

I completely agree, it's a temporary workaround at best. The more valuable information though is that there's a direct correlation to KB3045999, which should make the issue easier for the testers & programmers to better diagnose and fix the root issue.

[pteriss]

Hi!

I just wanted to chime in, that I am experiencing the exact same issue regarding KB3045999 on Windows 8 x64. Uninstalling helps, but as I am in an enterprise environment, the same update is being pushed to my pc almost daily. Really looking forward for a fix!

[sir-game-a-lot]

Just want to say thanks and confirm that uninstalling KB3045999 fixed the exact error. Hopefully M$ will patch it up asap. The problem is that if I leave automatic updates enabled it installs back KB3045999. Changed windows update from "Install updates automatically" to "Download updates but let me choose whether to install them"

[mrtimuk]

I have this issue too: Win 8.1 x64. KB3045999, KB3038314 and KB3049508 are installed. My machine is on corporate domain etc.

[Frank Mehnert]

Please could you try the latest Windows test build? It contains a fix which should allow you to install the Microsoft hotfixes which is highly recommended as they contain important security fixes. Thank you!

[zimbo]

Just installing the latest test build has solved the issue for me, thanks frank.

[mrtimuk]

Broken in 4.3.26 r98988. Fixed in 4.3.27 r100091. Thanks

[Scootin159]

+1, it didn't work in 4.3.26 for me. Worked in 4.3.27 r10091.

[Frank Mehnert]

Thank you all for the feedback!

[Frank Mehnert]

Fix is part of VBox 4.3.28.

[jaccarmac]

This issue pops up again when using Windows Insider build 14267 and Virtualbox 5.0.15 r105570.

The issue has been filed with Windows as well; Not sure where the appropriate place for the fix is.

Should this be in a new ticket or can it be considered a continuation of this one?

[winter98]

have the same problem - didn't windows break virtualbox in 14252 and then fix in 14257 ? feels like it's windows previews mucking about with something and (hopefully) will be fixed in another preview. Annoying.

[birdbox]

Same here. Can't start any of my VM's due to....

NtCreateFile(\Device\VboxDrvStub) failed:0xc0000034 STATUS_OBJECT_NAME_NOT_FOUND error.

Also says 'make sure the kernal module has been loaded successfully' and 'where:supR3HardenedWinReSpawn what:3 VERR_OPEN_FAILED(-101)- File/Device open failed...

Please help!

[Djago]

Same here, same Windows, but vBox r105127. I think this ticket has to be re-opened...

[SchlauFuchs]

Windows 10 Build 14267.rs1_release.160213-2013 has changed the signature of ntdll.dll and renders VirtualBox useless. Please fix.

[emwtur]

Windows 10.0.14267.1000 (rs1_release.160213-0213)

Error message :

VirtualBox - Error In supR3HardenedWinReSpawn

NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5600 (0xffffea20) (rcNt=0xe986ea20)
VBoxDrvStub error: ntdll.dll: 4 differences between 0x14a050 and 0x14a053 in #5 (.da (rc=-5600)
Make sure the kernel module has been loaded successfully.

where: supR3HardenedWinReSpawn
what: 3
VERR_SUP_VP_MEMORY_VS_FILE_MISMATCH (-5600) - Process Verification Failure: The memory content does not match the image file.

[karzzyk]

Windows 10.0.14267.1000 (rs1_release.160213-0213)

error message :

VirtualBox - Error In supR3HardenedWinReSpawn

Same issue here need this fixed for college asap, how long did they tale to fix this last time?

[Frank Mehnert]

Should be fixed in the most recent Windows test build.

[vicanfon]

Replying to frank:

Should be fixed in the most recent Windows test build.

Frank, with that version I skip the supR3 error but I am getting VT-x is not available (VERR_VMX_NO_VMX). I have check that partition has hypervisorlaunchtype off. What is going on?

[Frank Mehnert]

Replying to vicanfon:

Replying to frank:

Should be fixed in the most recent Windows test build.

Frank, with that version I skip the supR3 error but I am getting VT-x is not available (VERR_VMX_NO_VMX). I have check that partition has hypervisorlaunchtype off. What is going on?

No idea. We didn't change anything related to VT-x. A VBox.log file might show the reason.

[jaccarmac]

Docker Machine is working for me again, and that was the use case for which I noticed the regression. I can't duplicate the VT-x issue on any of my VMs.

[Jacob Klein]

Replying to frank:

Should be fixed in the most recent Windows test build.

Frank, I noticed on the Test Builds page, that 4.3.x is missing the fix. Could we get the fix on that branch too please? Thanks, Jacob

[Frank Mehnert]

Sure, just updated the 4.3 Windows build on the test builds page.

[Jacob Klein]

Excellent -- I'll test it now! Thanks :)

[Jacob Klein]

I tested the 4.3.x test builds 105697 and 105748 - they both start VMs correctly in Windows 10 Insider Build 14271. Thanks again!

[Frank Mehnert]

Fix is part of VBox 5.0.16.

[jwalklett]

I've just come to use one of my VM's and none of them will open. I'm getting the NTCreateFile failed error. I was affected by the previous bug, which was then fixed by installing 5.16, however I rebooted my host machine today after a week of being out of the office and I'm getting the error again. Host machine is Windows 8.1 64bit Intel.