Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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 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.
That begins after I install a new disk with Windows 10 Anniversary, Visual Studio 2015 update 3 and the last stable Xamarin.
I did what many guys suggest : reinstall Android SDK, check Hyper V, initialize API, launch XdeCleanUp ..
Nothing to do, Xamarin does not run. The emulator stops.
I note some strange points.
1) in the folder .. \ Microsoft Xde, I have :
subs folders : Win 8.0, Win 8.1 , 10.0.10586.0 , 10.0.14393.0
So when it installs Windows 10 Anniversary (version 14393) it installs also XDE for Windows 8.0 and 8.1 and Windows 10 (the first version 10586).
What need for that ?
If I launch XdeCleanUp in 10.0.14393.0, there is no error.
If I launch XdeCleanUp in 10.0.10586.0, there is an error (code error 32775).
That is normal because I have not Windows 10 base but Windows 10 Anniversary.
2) If I launch the emulator (5.5 Marshmallow API 23), I have the following error :
“The Windows Phone Emulator wasn't able to set some properties on the virtual machine: Couldn't change memory of the virtual machine: Error code 32775”.
The same error that I have with XdeCleanUp.
And If I read the log, I have :
3> 31/10/2016 20:28:03 : [Critical] XDE Path: C:\Program Files (x86)\Microsoft XDE\10.0.10586.0\xde.exe
3> 31/10/2016 20:28:03 : [Critical] XDE Arguments: /sku Android /displayName "VS Emulator 5.5\" Marshmallow (6.0.0) XXXHDPI Phone" /memSize 3072 /diagonalSize 5.5 /video "2160x3840" /vhd "C:\Users\gestion\AppData\Local\Microsoft\VisualStudioEmulator\Android\Containers\Local\Devices\vhd\5.5_Marshmallow_(6.0.0)_XXXHDPI_Phone\image.vhd" /name "VS Emulator 5.5-inch Marshmallow (6.0.0) XXXHDPI Phone.gestion"
3> 31/10/2016 20:28:03 : [Critical] XDE Exit Code: CouldntFindOrCreateVm (9)
So, the emulator try to launch XDE from 10.0.10586 instead to use XDE from 10.0.14393.
I think the problem is here.
Read the post :
Created attachment 18307 [details]
the files created by emulator
Another point :
by reading the files created when we install an emulator, we can see :
"An operation system wasn’t found."
Look the attachement before
We will investigate it in order to understand what is happening and provide you a fix.
Thanks to report the issue.
Thanks so much for taking the time to submit this report!
I attempted to reproduce this issue based on the bug description with the latest Visual Studio 2017 Preview 2 version 15.4, and I was unable to hit the problem. If this issue is still occurring for you, please reopen this report and attach a reproduction, ideally starting with a new template project and then adding just the code necessary to demonstrate the issue.