Windows 10 Build 14942+ - VirtualBox fails to start

[Jacob Klein]

Note:
The problems in this thread, were fixed by:
- Oracle VirtualBox v5.1.7 Test Build 111203
- Oracle VirtualBox v5.0.27 Test Build 111204











=========================================================
Windows 10 Build 14942+ - VirtualBox fails to start

On Windows 10 Build 14942, Virtualbox immediately crashes, creating a WerFault.exe process.
Full details were obtained from looking in the Event Viewer after the crash, and are listed below.

Oracle, can you please fix this, for 5.0.x and 5.1.x?

Insiders: Please upvote my Feedback item, by copy/pasting the following into your explorer or browser, then clicking UpVote. Thanks.
feedback-hub:?contextid=156&feedbackid=f5e3e596-6f04-46ed-a695-bb670463a3d8&form=1&src=2

Thanks,
Jacob Klein

=========================================================
Oracle VirtualBox v5.1.7 Test Build 111038:

Faulting application name: VirtualBox.exe, version: 5.1.7.11038, time stamp: 0x57ecf6d4
Faulting module name: VirtualBox.exe, version: 5.1.7.11038, time stamp: 0x57ecf6d4
Exception code: 0xc0000005
Fault offset: 0x00000000000139bd
Report Id: 5342e466-4817-49bb-a3f8-4586067dfb6f

=========================================================
Oracle VirtualBox v5.0.27 Test Build 111143

Faulting application name: VirtualBox.exe, version: 5.0.27.11143, time stamp: 0x57f64bc1
Faulting module name: VirtualBox.exe, version: 5.0.27.11143, time stamp: 0x57f64bc1
Exception code: 0xc0000005
Fault offset: 0x00000000000139ed
Report Id: 581ed904-3220-459e-bae6-dd6bcb7c06ea

=========================================================
Oracle VirtualBox v4.3.40 Build 110317

Faulting application name: VirtualBox.exe, version: 0.0.0.0, time stamp: 0x57baf3c5
Faulting module name: VirtualBox.exe, version: 0.0.0.0, time stamp: 0x57baf3c5
Exception code: 0xc0000005
Fault offset: 0x0000000000016dfd
Report Id: cc859d9a-2787-4d1d-805b-964c3751c517

[rseiler]

Yes, same error content here with 5.1.6.10634.

No VB logs are written, no error in the UI since there never is a UI.

[rayman]

Bump... same exact problem reported by the OP. I am seeing the same fault in Event view. Went to 5.1.7.11038 hoping the problem was resolved already (from past reports) and no luck. Same problem. Just dies immediately.

[Monsepuseladden]

Same problem here. On Windows insider build 14942.
After starting Virtual Box, nothing happens.

[jontangent]

Same here.
1. Tried Repair install, Reinstall, Uninstall -> reboot -> clean Install -> reboot. no joy.
2. Reverted to previous Win 10 Pro Insider Preview build 14936, and verified thatV Box 5.1.6-110634 works fine, as before.
3. Uninstalled VBox 5.16 on 14936 build, cleaned registry, rebooted.
4. Reinstalled 14942 build. Reinstalled VBox 5.16. Same issue. VBoxManage.exe also faults.. details below.

The VBox Network Host-Only Network Adapter is installed and enabled, the drivers appear to be the correct version. If any VBox services should be installed and/or running/started, I can't see them.

Log Name: Application
Source: Application Error
Date: 10/9/2016 10:55:11 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: wrk-wn701
Description:
Faulting application name: VirtualBox.exe, version: 5.1.6.10634, time stamp: 0x57d6d53c
Faulting module name: VirtualBox.exe, version: 5.1.6.10634, time stamp: 0x57d6d53c
Exception code: 0xc0000005
Fault offset: 0x00000000000139bd
Faulting process id: 0x1c28
Faulting application start time: 0x01d2224583decf9b
Faulting application path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Faulting module path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Report Id: df69da17-9fd2-4d5e-8976-c71f1eef3405
Faulting package full name:
Faulting package-relative application ID:

-------------------------------------------------------

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

[popfrog]

The latest test build 111168 still does not work on 14942~~~

[rseiler]

Thanks for checking that.

I noticed there are some comments accumulating here:
https://www.virtualbox.org/ticket/16051

[aniskhan001]

Coming from a 14942 Build and I confirm the issue as well.

[michaln]

Please make sure Microsoft is aware of what they broke, too.

[users]

VirtualBox-5.1.7-111168-Win.exe can't start on the Windows 10 Build 14942. There are nothing in the logs.

[Jacob Klein]

Please make sure Microsoft is aware of what they broke, too.

Absolutely. In fact, here is the Feedback item I created, immediately after creating this thread. Copy/paste it into your Explorer or browser.
feedback-hub:?contextid=156&feedbackid=f5e3e596-6f04-46ed-a695-bb670463a3d8&form=1&src=2

Thanks,
Jacob

[rseiler]

Though I can think of zero instances where MS fixed this the last couple dozen times this happened, so expecting them to do so this time would be a mistake.

[Jacob Klein]

I expect Oracle to fix it. Oracle expects Microsoft to get flack for breaking it.

All expectations will be eventually met.

[timespinner]

Any chance this can be given a high priority?

[michaln]

Any chance this can be given a high priority?

No, unless you're an Oracle customer. Although even then you'd have a very hard time arguing that you're running a supported host OS.