Windows 10 Build 14267 VirtualBox error

[rseiler]

Is anyone seeing this upon starting a VM? It doesn't seem to matter what OS is in the VM, as it happens instantly.

err2.JPG (33.5 KiB) Viewed 18743 times

err.JPG (29.81 KiB) Viewed 18743 times

[Jacob Klein]

Yes, I confirm the VERR_SUP_VP_MEMORY_VS_FILE_MISMATCH error on Windows 10 Insider Preview Build 14267 for:
- 4.3.36 r105129
- 5.0.15 r105570 (the latest Testbuild)

More specifically, the error is:
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.

I'm not sure if this is an Oracle VirtualBox problem, or a Microsoft Windows problem. My workaround will be to run BOINC and VirtualBox, using my "Windows 10 Release" partition, instead of my "Windows 10 Insider" partition... until this is fixed.

==================================================================
For Windows Insiders experiencing this problem, if you'd like Microsoft to know, please copy/paste the following into File Explorer or a browser. It should open my feedback item, in the Windows Feedback app. You can then optionally add some text if you'd like, and then click "Upvote". Thanks!
Windows-Feedback:?contextid=156&feedbackid=1322b77c-073d-4bd6-93de-7e3de6277778&form=1&src=2
==================================================================

Thanks,
Jacob Klein

==================================================================
Here (attached) are the details for 4.3.36 r105129, including the error text:

4.3.36 Error Message 1.png (14.5 KiB) Viewed 18736 times

4.3.36 Error Message 2.png (14.76 KiB) Viewed 18736 times

4.3.36 VBoxHardening.log

(10.73 KiB) Downloaded 130 times

4.3.36 r105129:

Code: Select all

---------------------------
VirtualBox - Error In supR3HardenedWin...
---------------------------
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 Verficiation Failure: The memory content does not match the image file.

Code: Select all

---------------------------
VirtualBox - Error
---------------------------
Failed to open a session for the virtual machine boinc_46aa81c5f147fed7 Clone 14 Clone.

The virtual machine 'boinc_46aa81c5f147fed7 Clone 14 Clone' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'E:\VirtualBox VMs\boinc_46aa81c5f147fed7 Clone 14 Clone\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

Code: Select all

==================================================================
From VBoxHardening.log:

23d0.a54: supR3HardenedVmProcessInit: Opening vboxdrv stub...
23d0.a54: supR3HardenedWinReadErrorInfoDevice: 'ntdll.dll: 4 differences between 0x14a050 and 0x14a053 in #5 (.da'
23d0.a54: Error -5600 in supR3HardenedWinReSpawn! (enmWhat=3)
23d0.a54: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5600 (0xffffea20) (rcNt=0xe986ea20)
VBoxDrvStub error: ntdll.dll: 4 differences between 0x14a050 and 0x14a053 in #5 (.da
2b34.2a5c: supR3HardenedWinCheckChild: enmRequest=2 rc=-5600 enmWhat=3 supR3HardenedWinReSpawn: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5600 (0xffffea20) (rcNt=0xe986ea20)
VBoxDrvStub error: ntdll.dll: 4 differences between 0x14a050 and 0x14a053 in #5 (.da
2b34.2a5c: Error -5600 in supR3HardenedWinReSpawn! (enmWhat=3)
2b34.2a5c: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5600 (0xffffea20) (rcNt=0xe986ea20)
VBoxDrvStub error: ntdll.dll: 4 differences between 0x14a050 and 0x14a053 in #5 (.da
==================================================================

[Jacob Klein]

Here (attached) are the details for 5.0.15 r105570, including the error text:

5.0.15 Error Message 1.png (14.1 KiB) Viewed 18735 times

5.0.15 Error Message 2.png (14.4 KiB) Viewed 18735 times

5.0.15 VBoxHardening.log

(11.04 KiB) Downloaded 128 times

5.0.15 r105570:

Code: Select all

---------------------------
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.

Code: Select all

---------------------------
VirtualBox - Error
---------------------------
Failed to open a session for the virtual machine boinc_46aa81c5f147fed7 Clone 13 Clone.

The virtual machine 'boinc_46aa81c5f147fed7 Clone 13 Clone' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'E:\VirtualBox VMs\boinc_46aa81c5f147fed7 Clone 13 Clone\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

Code: Select all

==================================================================
From VBoxHardening.log:

2240.28c4: supR3HardenedVmProcessInit: Opening vboxdrv stub...
2240.28c4: supR3HardenedWinReadErrorInfoDevice: 'ntdll.dll: 4 differences between 0x14a050 and 0x14a053 in #5 (.da'
2240.28c4: Error -5600 in supR3HardenedWinReSpawn! (enmWhat=3)
2240.28c4: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5600 (0xffffea20) (rcNt=0xe986ea20)
VBoxDrvStub error: ntdll.dll: 4 differences between 0x14a050 and 0x14a053 in #5 (.da
2128.20a4: supR3HardenedWinCheckChild: enmRequest=2 rc=-5600 enmWhat=3 supR3HardenedWinReSpawn: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5600 (0xffffea20) (rcNt=0xe986ea20)
VBoxDrvStub error: ntdll.dll: 4 differences between 0x14a050 and 0x14a053 in #5 (.da
2128.20a4: Error -5600 in supR3HardenedWinReSpawn! (enmWhat=3)
2128.20a4: NtCreateFile(\Device\VBoxDrvStub) failed: Unknown Status -5600 (0xffffea20) (rcNt=0xe986ea20)
VBoxDrvStub error: ntdll.dll: 4 differences between 0x14a050 and 0x14a053 in #5 (.da
==================================================================

[kowalski]

Same problem here since windows 10 14267.
Also reported to Windows Feedback

[users]

I have the same issue:

Code: Select all

Failed to open a session for the virtual machine Windows XP.

The virtual machine 'Windows XP' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'E:\Documents and Settings\RRR\VirtualBox VMs\Windows XP\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

Microsoft Windows NT 6.2.9200.0
Windows 10 Pro Insider Preview
Version 1511 (OS Build 14267.1000)
BuildLab 14267.rs1_release.160213-0213

Virtual box Version 5.0.14 r105127

[Heldchen]

same problem here on Windows 10 Build 14267.rs1_release.160213-0213 and virtualbox 5.0.15 r105570

[mfelker]

Yes I have the exact same problem. VB ran and created VMs ine on Build 14257 and is broken instantly for all BMs on Build 14267. FWIW VMwaRe 11.1.3 runs perfectly.

[AntonioRibeiro]

Exact same problem here.

Tested on

VirtualBox-5.0.15-105570-Win
VirtualBox-5.0.14-105127-Win
VirtualBox-4.3.36-105129-Win

All the same.

Happened after upgrading to Windows 10 Build 14267

[mfelker]

These fatal problems with Virtualbox on Windows Preview Builds was fixed in the last one 14257 when it was broken in the one before that. Thanks for letting me know that is't broke on VB 5.0.15 - savers me from trying it out to no avail.

[jwalsh2]

Same issue here, any know work around yet? Updated to 5.0.15 testbuild and confirm it also has the same problem. Kind of wish I did not do the last MS preview now.

[CooperRJ]

Same Problem on VB 5.0.15 r105609.

[rseiler]

Same issue here, any know work around yet? Updated to 5.0.15 testbuild and confirm it also has the same problem. Kind of wish I did not do the last MS preview now.

Unlikely, but until a dev steps in here, we won't know.

On the bright side, think of it as an opportunity to re-familiarize yourself with Hyper-V. I use Autoruns to disable the VB drivers (so they won't start on next boot), enable Hyper-V in "Programs and Features," and reboot. It's easy to revert that, too.

[Jacob Klein]

Same issue here, any know work around yet? Updated to 5.0.15 testbuild and confirm it also has the same problem. Kind of wish I did not do the last MS preview now.

The only "workarounds" I know are to either (a) use a Windows 10 Release partition (instead of an Insider partition) to run your VMs, or (b) run your VMs on an Insider host using a version of VirtualBox that doesn't have the windows process hardening functionality (so, v4.3.12 or earlier, which may run, but will lose out on all the bug fixes over the last 1.5 years)

I'm using option (a), since I've intentionally setup dual-boot (Windows 10 Release vs Windows 10 Insider), on all my Insider PCs, specifically because VirtualBox's code seems pretty touchy and keeps breaking on Insider builds.

[drbohner]

Has anyone attempted the "Restore to Previous Version of Windows" option?

I'm attempting it, now - just curious if it was just a false hope. If no one else replies, I'll update with my results.

<and this is frustrating as hades>

(db)

[mfelker]

Well even though its "politically incorrect" another workaround is to use VMware. But I also use VB on my Windows Server 2016 TP4 box - works great. I suppose the free VMware Player will work on the Windows Insider Preview builds but I purchased and upgraded VMware since version 1 in 1998 or 99