Bug 32824 - Player won't start on Windows 10: E_FAIL 0x80004005
Summary: Player won't start on Windows 10: E_FAIL 0x80004005
Alias: None
Product: Xamarin Android Player
Classification: Xamarin
Component: Player ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2015-08-06 09:35 UTC by Thomas
Modified: 2015-10-01 06:55 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

log (2.79 KB, application/x-zip-compressed)
2015-08-06 09:40 UTC, Thomas

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Thomas 2015-08-06 09:35:59 UTC
I'm running two machines with Windows 10 Pro. On a 64-bit AMD machine, XAP 0.4.4 works fine after patching VirtualBox to 5.0.0 and manually adjusting the host-only network adapter as described in this thread: https://forums.xamarin.com/discussion/40398/windows-10-support

On a 32-bit Intel Core Duo machine this didn't work. The Player won't start up (see attached log).

If I start the virtual machine using the virtual box manager, this happens:


The virtual machine 'Nexus S (KitKat)' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\tm\AppData\Roaming\XamarinAndroidPlayer\VMStorageLibrary\Nexus S (KitKat)\Logs\VBoxStartup.log'.

Error code:E_FAIL (0x80004005)
Interface:IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}


I also notices system sounds indicating hardware removal.

Before trying XAP, I installed the current Intel HAXM drier.
Comment 1 Thomas 2015-08-06 09:40:22 UTC
Created attachment 12380 [details]

bugzilla ate my attachment on the initial report submission because I added no attachment description
Comment 2 Mark Simpson 2015-08-11 07:06:03 UTC
For some reason VBoxManage is returning 1 when starting the VM despite the stdout reporting success.
[15-08-06 13:06:11.32] C:\Program Files\Oracle\VirtualBox\VBoxManage.exe result: 
StandardOutput: Waiting for VM "Nexus S (KitKat)" to power on...
VM "Nexus S (KitKat)" has been successfully started.
ExitCode: 1
[15-08-06 13:06:11.32] VBoxManage command failed. This was the command:
'C:\Program Files\Oracle\VirtualBox\VBoxManage.exe "startvm" "Nexus S (KitKat)" "--type" "headless"'
StandardOutput: Waiting for VM "Nexus S (KitKat)" to power on...
VM "Nexus S (KitKat)" has been successfully started.
ExitCode: 1

Could you open VirtualBox's UI and watch the device as you try and start it from XAP to see if it flicks through any other states?

Also, please load the XAP Device Manager, right click on the lower black bar and select 'Generate Bug Report'. This will collate various logs and place them on your desktop in a zip file, could you upload that here? It will catch the VBox log files and may point toward what's going on here.

VirtualBox 5 isn't yet fully supported on Windows 10 this might be the reason that XAP can't start the VM. Their download page mentions this and has a link to test builds that may fix some of the problems. I can't recommended that you install test builds of VirtualBox 5, but if you do want to try then it *may* fix this.
Comment 3 Mark Simpson 2015-10-01 06:55:36 UTC
More recent builds of VirtualBox (5.0.4) are more compatible with Windows 10 and XAP 0.6.1 has changes to resolve this issue.

I'm going to close this as I believe it is fixed, please do reopen it if this is not the case.