Windows 10 Build 15002+ - VirtualBox fails to start

[Bobbyw87]

5.1.13 Fixed the issue for me as well.

[Jacob Klein]

I have confirmed that the following do start correctly in Windows 10 Build 15002:
Oracle VirtualBox v5.1.13 Test Build 112780
Oracle VirtualBox v5.1.13 Test Build 112787
Oracle VirtualBox v5.0.31 Test Build 112781

Any chance for a v4.3.x Test Build? ::still crossing fingers::

[JensGibolde]

Can somebody already verify that the newest test builds run under Windows 15007?

Regards

Jens

[rseiler]

Yes, I didn't need to update the test build from a couple days ago.

[jadog]

I tried to get Virtual Box 5.1.12 r112440 to run on Windows 10 15002 and 15007 build and it the interface wont open. My current PC runs it and upgraded which broke Virtual box and I had to downgrade back to Build 14986. I tried Virtual Box including the Beta on my laptop with build 15002 and 15007 and neither will work.

Does anyone know a workaround to get this working or when do you expect to get support for the newer 15000 build of windows?

Thanks, Jason

[socratis]

@jadog
I merged your post with the thread that deals with the exact same issue. Please read the thread.

[rseiler]

I tried to get Virtual Box 5.1.12 r112440 to run on Windows 10 15002 and 15007 build and it the interface wont open.

https://www.virtualbox.org/wiki/Testbuilds

[citop]

i updated windows 10 to 15007 recently released, and find virtualbox can not start, there is a long error in system event list with error code 0x000005(or 0x100005, not sure)

[Mozzie_16]

Same issue, updated to 15007, virtual box 5.1.12 crash, un-install, re-install no change.
Windows error 1000

Faulting application name: VirtualBox.exe, version: 5.1.12.12440, time stamp: 0x58594e7b
Faulting module name: VirtualBox.exe, version: 5.1.12.12440, time stamp: 0x58594e7b
Exception code: 0xc0000005
Fault offset: 0x0000000000013a1d
Faulting process id: 0x2ea0
Faulting application start time: 0x01d26fc3a7b0d5d5
Faulting application path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Faulting module path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Report Id: 500ab843-83a2-4cb1-bb16-2765113a638f
Faulting package full name:
Faulting package-relative application ID:

then 1001 Appcrash

Fault bucket 120672157914, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: VirtualBox.exe
P2: 5.1.12.12440
P3: 58594e7b
P4: VirtualBox.exe
P5: 5.1.12.12440
P6: 58594e7b
P7: c0000005
P8: 0000000000013a1d
P9:
P10:

The WER file has nothing relevant

[socratis]

@citop, @Mozzie_16
I merged your post with the thread that deals with the exact same issue. Please read the thread. And use the search functionality please.

[rseiler]

Now out:
VirtualBox 5.1.14 (released 2017-01-17)

The fix from the test builds is included:
Windows hosts: another fix for recent Windows 10 hosts

[Dan Bennett]

Having this same issue. Not on the insider preview.

Was on 5.12. Went to 5.14 but no fix. Now on the latest test build (5.15) and the issue still occurs.

Code: Select all

The virtual machine 'test' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'D:\VMs\test\Logs\VBoxHardening.log'.

Result Code: 
E_FAIL (0x80004005)

Component: 
MachineWrap

Interface: 
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

VBoxHardening.log attached.

Before upgrading to the latest test built, I was also getting BSODs when attempting to start any VM. These cleared when updating, to instead give me the errors that were happening at the same time...

[Jacob Klein]

Dan,

If you're not using the Windows Insider Preview builds, then you shouldn't be posting here. And your issue is not the same as this thread's issue.
Please consider starting a thread within the normal "VirtualBox on Windows Hosts" forum, and potentially opening a ticket.
My hunch, though, is that your VM is corrupt and non-recoverable. Hope you had backups. Sorry.

Regards,
Jacob

[socratis]

My hunch, though, is that your VM is corrupt and non-recoverable. Hope you had backups. Sorry.

No, no, no, no, no!!! Absolutely not!!! The hardening error is definitely not corruption of the VM. It's a non-properly signed DLL that's trying to inject itself in the VirtualBox process. Think antivirus, GPU utilities, hacked themes, debuggers, etc.

You're absolutely right that "Dan Bennett" should open a new thread about that. Actually, scratch that, there are a gazillion of them open already. Makes you wonder why he chose the Windows pre-releases forum...

[Jacob Klein]

Whoops, sorry for jumping to conclusions. You're right, a 3rd-party dll could easily cause hardening to trip up.