Windows 10 Build 14291+ - VirtualBox fails to start

[rseiler]

It doesn't help much, but I've been using it regularly with 14393.5 and it's fine here.

Try a VB repair install and reboot.

I should say that I'm using 5.1.2. How about you?

[Jacob Klein]

14393.5 not working, i see the process in task manager and it kills itself !

And i'm getting this in events log

Faulting application name: VirtualBox.exe, version: 0.0.0.0, time stamp: 0x54dcccba
Faulting module name: VirtualBox.exe, version: 0.0.0.0, time stamp: 0x54dcccba
Exception code: 0xc0000005
Fault offset: 0x0000000000015652
Faulting process id: 0x5f0
Faulting application start time: 0x01d1e7a6ee5f5f05
Faulting application path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Faulting module path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Report Id: a98aa113-7561-4736-a826-6f7e0b049bf1
Faulting package full name:
Faulting package-relative application ID:

Uhh... are you maybe using an old version of VirtualBox? That "0.0.0.0" versioning info makes it look like a 4.3.x version, and ... only the latest Test Builds of 4.3.x will work on the newest builds of Windows 10. VirtualBox 4.3.38 won't work.

So, if you are using 4.3.x, are you using "Oracle VirtualBox v4.3.39 Test Build 108750" like you should be?
https://www.virtualbox.org/wiki/Testbuilds

They might release an official 4.3.40 version, soon that fixes it officially in a public release, but... 4.3.x is old...
They recommend 5.1.x (current), or 5.0.x (if needed for compatibility).
I use 4.3.x out of necessity, because I have long-running BOINC VM tasks that require 4.3.x. And "Oracle VirtualBox v4.3.39 Test Build 108750" does work.

[DALIDB19]

14393.5 not working, i see the process in task manager and it kills itself !

And i'm getting this in events log

Faulting application name: VirtualBox.exe, version: 0.0.0.0, time stamp: 0x54dcccba
Faulting module name: VirtualBox.exe, version: 0.0.0.0, time stamp: 0x54dcccba
Exception code: 0xc0000005
Fault offset: 0x0000000000015652
Faulting process id: 0x5f0
Faulting application start time: 0x01d1e7a6ee5f5f05
Faulting application path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Faulting module path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Report Id: a98aa113-7561-4736-a826-6f7e0b049bf1
Faulting package full name:
Faulting package-relative application ID:

Uhh... are you maybe using an old version of VirtualBox? That "0.0.0.0" versioning info makes it look like a 4.3.x version, and ... only the latest Test Builds of 4.3.x will work on the newest builds of Windows 10. VirtualBox 4.3.38 won't work.

So, if you are using 4.3.x, are you using "Oracle VirtualBox v4.3.39 Test Build 108750" like you should be?
https://www.virtualbox.org/wiki/Testbuilds

They might release an official 4.3.40 version, soon that fixes it officially in a public release, but... 4.3.x is old...
They recommend 5.1.x (current), or 5.0.x (if needed for compatibility).
I use 4.3.x out of necessity, because I have long-running BOINC VM tasks that require 4.3.x. And "Oracle VirtualBox v4.3.39 Test Build 108750" does work.

Thanks that worked, i'm trying to install Yosemite here !

[socratis]

Thanks that worked, i'm trying to install Yosemite here !

You host is a Windows one, so a word of caution: Mac OS X guest on a Windows Host.

[inaj]

I'm still having some problems with this on Win10 14393.10.

Both, VBoxManage 5.1.2 and 5.1.3 r109643 (latest test build atm) seem to crash if I run this command:

Code: Select all

"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" showvminfo Default --machinereadable

Windows' Event Log says the following:

Code: Select all

Faulting application name: VBoxManage.exe, version: 5.1.3.9643, time stamp: 0x57a470e5
Faulting module name: VBoxC.dll, version: 5.1.3.9643, time stamp: 0x57a470dc
Exception code: 0xc0000005
Fault offset: 0x00000000000a5ec7
Faulting process id: 0x2f58
Faulting application start time: 0x01d1f01c82740a05
Faulting application path: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe
Faulting module path: C:\Program Files\Oracle\VirtualBox\VBoxC.dll
Report Id: bfa0b9a3-ad0c-48e3-83fd-4470bbe27487
Faulting package full name: 
Faulting package-relative application ID:

Should I open a new forum post or ticket?

EDIT: VBoxManage does print some output before crashing.

[Jacob Klein]

Yes inaj, if 5.1.2 isn't working for you, please open a Ticket.

[socratis]

Yes inaj, if 5.1.2 isn't working for you, please open a Ticket.

Since this is the first time that Win10 14393.10 appears, I would wait for at least one more confirmation. Tickets are easy to open but hard to close, in the sense that people tend to forget all about them after their issue has been resolved and the tickets are left open, in limbo.

And at the end, this is the role of the forums here; to triage the issues before they are turned into bug reports and overburden the developers.

[inaj]

Yes inaj, if 5.1.2 isn't working for you, please open a Ticket.

Since this is the first time that Win10 14393.10 appears, I would wait for at least one more confirmation. Tickets are easy to open but hard to close, in the sense that people tend to forget all about them after their issue has been resolved and the tickets are left open, in limbo.

And at the end, this is the role of the forums here; to triage the issues before they are turned into bug reports and overburden the developers.

Sure.

Here are the explicit steps to reproduce (if anyone misses them):
- Install VBox 5.1.2 on Win 10 14393.10 x64
- Start a guest (At least Win7 and boot2docker tested)
- Run the command:

Code: Select all

"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" showvminfo TheRunningMachine

- Check the event log of Windows, because you can't tell the program crashed from the command line

EDIT: --machinereadable is not needed
EDIT2:

14xxx OK

Hey, would you mind testing the vboxmanage command as well? Thanks!

[Jacob Klein]

inaj:

Please report the issue that you found, in a new thread, that is IN "VirtualBox on Windows Hosts", but is NOT in "VirtualBox on Windows pre-releases", since this issue is happening on the latest VirtualBox on the latest publicly-released version of Windows 10.

This particular thread is about VirtualBox failing to start, due to problems with its Windows process hardening logic, which have been resolved so far as we know.

Also, to help you out, I have reproduced your problem, using these steps:
- Host: Windows 10 x64, Version 1607, OS Build 14393.10
- Get a VM from here: https://developer.microsoft.com/en-us/m ... tools/vms/
- Use "Import Appliance" to import it
- Start the VM
- Open "Command Prompt (Admin)"
- Type: "C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" showvminfo "VMName"
- The Command Prompt will appear to be successful
- Open Event Viewer
- In "Windows Logs -> Application", the "0xc0000005" error will be shown

I tested 2 versions:

Oracle VirtualBox v5.1.2 Build 108956

Code: Select all

Faulting application name: VBoxManage.exe, version: 5.1.2.8956, time stamp: 0x5790f061
Faulting module name: VBoxC.dll, version: 5.1.2.8956, time stamp: 0x5790f057
Exception code: 0xc0000005
Fault offset: 0x00000000000a6a07

Oracle VirtualBox v5.1.3 Test Build 109643

Code: Select all

Faulting application name: VBoxManage.exe, version: 5.1.3.9643, time stamp: 0x57a470e5
Faulting module name: VBoxC.dll, version: 5.1.3.9643, time stamp: 0x57a470dc
Exception code: 0xc0000005
Fault offset: 0x00000000000a5ec7

Thanks,
Jacob Klein

[inaj]

Please report the issue that you found, in a new thread, that is IN "VirtualBox on Windows Hosts", but is NOT in "VirtualBox on Windows pre-releases", since this issue is happening on the latest VirtualBox on the latest publicly-released version of Windows 10.

Yeah, thought the discussion might be related and thus I decided to ask here first. Anyway there's a new topic.

I tested 2 versions:

Thanks!

[Jacob Klein]

Getting slow, rseiler...
14901 is working, with 5.0.27 at least :-p

Perhaps we should just let this thread relax, and then just start a new one if we have another legitimate problem.
PS: Still wanting (and waiting for) a 4.3.x public release that contains the generic fix.. They said they may release it.

[rseiler]

An interesting item today in the release notes for 14926:

"Oracle VM VirtualBox will crash on launch after upgrading to this build."

But it doesn't, at least with 5.1.6.

[Jacob Klein]

I'll soon be testing the new Insider build, against both the 5.0.27 Test Build, and the 4.3.40 Release Build.
I still use both of them, for long-running BOINC tasks

If I have problems, especially with 4.3.40 (which will no-longer receive updates), then I'll have to resort to booting out of my "Windows 10 Insider" partition, and into my "Windows 10 Release" partition.
It's good to have a plan B, ready to go.

[wacher]

An interesting item today in the release notes for 14926:

"Oracle VM VirtualBox will crash on launch after upgrading to this build."

But it doesn't, at least with 5.1.6.

it does here, unfortunately Just right after the upgrade process at first boot.

[rseiler]

it does here, unfortunately Just right after the upgrade process at first boot.

Do you mean when installing the Insider build *in* VB? I was talking about the Insider build as Host.