Windows 10 Build 14291+ - VirtualBox fails to start

[Jacob Klein]

======================================================================================
EDIT
======================================================================================
Oracle has fixed the problem identified in this thread. Details are:

The VirtualBox problems on: Windows 10 Build 14291
... were solved by:
- Oracle VirtualBox v5.0.17 Test Build 106359
- Oracle VirtualBox v4.3.37 Test Build 106347

The VirtualBox problems on: Windows 10 Build 14328
... were solved by:
- Oracle VirtualBox v5.0.19 Test Build 106880
- Oracle VirtualBox v4.3.39 Test Build 106879

For reference, if you want to try a Test Build to see if it fixes your issue, they are here:
https://www.virtualbox.org/wiki/Testbuilds

======================================================================================
Original message:
======================================================================================
Oracle:
On Windows 10 Insider Build 14291, VirtualBox fails to start. Launching it, results immediately with a crash, and a "WerFault.exe" process interception. Details are below, including important Event Viewer data. Please identify the problem, and fix it if the fault is yours, as time permits.

Windows 10 Insiders:
If you're having the problem, you could UpVote my feedback item so that the problem becomes more visible to Microsoft. Paste the following into any window, to get to my feedback item:
feedback-hub:?contextid=156&feedbackid=81357525-4f41-4507-9f4d-35f1ca987e52&form=1&src=2

Thanks,
Jacob Klein

Failure verified with all current versions:
- Oracle VirtualBox v5.0.17 Test Build 106005
- Oracle VirtualBox v5.0.16 Build 105871
- Oracle VirtualBox v4.3.37 Test Build 105748

Event Viewer says:

- Oracle VirtualBox v5.0.17 Test Build 106005
Faulting application name: VirtualBox.exe, version: 5.0.17.6005, time stamp: 0x56e7d755
Faulting module name: VirtualBox.exe, version: 5.0.17.6005, time stamp: 0x56e7d755
Exception code: 0xc0000005
Fault offset: 0x000000000001a432

- Oracle VirtualBox v5.0.16 Build 105871
Faulting application name: VirtualBox.exe, version: 5.0.16.5871, time stamp: 0x56d9b7eb
Faulting module name: VirtualBox.exe, version: 5.0.16.5871, time stamp: 0x56d9b7eb
Exception code: 0xc0000005
Fault offset: 0x000000000001a432

- Oracle VirtualBox v4.3.37 Test Build 105748
Faulting application name: VirtualBox.exe, version: 0.0.0.0, time stamp: 0x56d06abe
Faulting module name: VirtualBox.exe, version: 0.0.0.0, time stamp: 0x56d06abe
Exception code: 0xc0000005
Fault offset: 0x0000000000019f12

[popfrog]

Yes.
The latest test build 106005 still failed to start on 14291.rs1

[SRETIG]

I'm having this issue as well. What is the title of your Windows Feedback post? I am not able to upvote it via the link you provided.

[Jacob Klein]

I'm having this issue as well. What is the title of your Windows Feedback post? I am not able to upvote it via the link you provided.

The Feedback is titled:
Oracle VirtualBox immediately crashes on Windows 10 Insider Build 14291

What happens, when you open File Explorer, and paste the following into the address bar, and press Enter?
feedback-hub:?contextid=156&feedbackid=81357525-4f41-4507-9f4d-35f1ca987e52&form=1&src=2

[Craig Carboni]

[url]feedback-hub:?contextid=156&feedbackid=963a0109-f58d-47f0-a6f9-6e160f8f1472&form=1&src=2[/url]

and attempted as by using Run as administrator

COMMAND LINE attempt

Code: Select all

C:\Program Files\Oracle\VirtualBox>vboxmanage startvm "debian1.example.com"
Waiting for VM "debian1.example.com" to power on...
VBoxManage.exe: error: The virtual machine 'debian1.example.com' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine

[mfelker]

Fails to start here as well. I can post to Windows 10 Forum but that will do nothing. VMware 11.1.3 still works great.

[Jacob Klein]

Thanks for the verification, mfelker and others.
I guess we wait patiently for Oracle's response, at this point!

Reminder about workarounds:
- Use a non-Insider version of Windows 10 (which is what I do - I've set up dual-boot, and can boot into my "Windows 10 Release" partition when I need VirtualBox).
- Use a version of VirtualBox that doesn't have the Windows Process Hardening, like 4.3.12 or earlier (which is ancient, 5/16/2014, and has several other bugs).

[Yirkha]

Hi, there is a ticket for that - VirtualBox code needs to be updated:
#15245 "VirtualBox fails to start on Windows 10 14286"

[Jacob Klein]

Last I heard, filing official tickets for Virtualbox problems that only exist on Windows Insider builds... was not recommended by Oracle. That's why I did not create a ticket. And it's also why this subforum was created in the first place.

[Yirkha]

Thank you for your comment, Jacob.

I have always taken the forum primarily as a platform to collect anecdotal evidence from end users and filter non-actionable duplicate spam from getting into the bug tracker.

For a well-written bug report about a single confirmed required code change, which includes the necessary technical details and due research, a ticket seemed like a more appropriate, more trackable and cleaner choice.

I apologize if creating a ticket in such a case is indeed discouraged by Oracle.

[Jacob Klein]

I'm not completely sure what the policy is, but I am positive that these forums here were created to keep the "Unsupported Windows 10 Insider" VirtualBox problems (which go in this "VirtualBox on Windows pre-releases" subforum), separated from the "Supported Windows 10 Release" VirtualBox problems (which get reported in the regular "VirtualBox on Windows Hosts" forum). Before this subforum, my threads would get locked.

Regarding tickets, I believe I've seen tickets get closed because the problem existed only on Insider. Conversely, I've seen tickets get fixed/completed, even when the problem existed only on Insider.

As such, in the end, I believe this "Windows pre-releases" subforum is the first best place to report and track problems and workarounds. Devs come in here once in a while, and throw us some bones, which is AWESOME! And.. frankly, I'm still very happy that Oracle created this subforum just for us!

Side question: Is your ticket, the same issue as post 1 in this thread?

[popfrog]

I don't think it is a real "new" problem.
Virtualbox always failed to start when Microsoft released a new windows 10 insider preview version.
And I think VirtualBox developers have noticed and started to sovle the problem. So no need to create a new ticket.
Just Wait for a new VBox test build. I believe it will fix the proble again.

[Tommy Skillethead]

Yep! Same here. All was well on previous insider build that i was on and the current build of VBox took care of an issue that caused it to crash on the previous two or three builds of Windows. Hopefully this will be seen here as posting on the Windows insider site seems to yield no fruit!

[eltoddo]

So there's no work-around this time around?

I think I'm leaving the preview program after this one. I'm growing tired of the endless free feedback we give Microsoft via the preview program with not so much as a thank you in return. Instead we get builds that just break things that were working just fine. Oracle on the other hand has been quick to post fixes to the issues. Fingers crossed this is another quick one.

[Jacob Klein]

I posted workarounds, in the 7th post of this thread.

In general, these problems have been Oracle's to fix. And they haven't always been very responsive. Keep in mind, you're using untested Insider software, so the "treat" is you are first to see the issues! And Oracle VirtualBox's process hardening will likely continue to be an ongoing issue as new Insider builds come out. If you're not prepared to deal with that, then you should switch to the Production ring.

Regards,
Jacob