Windows Mobile Emulator 10.0.10240.0 not launching the OS - emulation

I have Windows 10 Pro installed (Hyper-V activated) and Visual Studio Enterprise 2015 (with "Universal Windows App Development Tools" and "Windows 8.1 and Windows Phone 8.0/8.1 Tools" installed) . I can launch succesfully all Windows Phone 8.1 Emulators but if I launch Windows Mobile Emulator 10 that is what happens:
The Phone Emulator opens properly with the write "Loading...".
After a while appears the write "OS is starting...".
Finally (after 5-10 minutes) the write disappear without launching the OS, the emulator just stays open with the black screen.
Visual Studio doesn't give any error so I really don't know what is the problem.
I also tried to launch the emulator directly from Hyper-V (right click on the emulator->Connect and then Action->Start) but the window just stays black. It seems I can't load the OS.
Any suggestion would be appreciated.

Open your HyperV, Open Visual Switch Manager .
Find VisualSwitch related to the Emulator ,click on it .
In Connection Type ,set connection to Private network ,Then press OK and restart your PC .After restart do the same and change Connection Type to Internal network and then restart.
Then it should work ,I guess!

Related

Visual Studio 2017 Installation breaks Windows 10 (on a MacBook Pro)

I have a fresh Windows 10 installation on my MacBook Pro (Late 2016) along with the newest Bootcamp drivers. Everything is working and shiny up until now.
When I install Visual Studio 2017 Enterprise it works up to a point where the reboot takes place. This takes really long, but windows is starting again, for about 7 minutes windows boots while showing the loading indicator. When I'm finally prompted for Login, the MacBooks keyboard and trackpad doesn't work anymore, as we'll as I don't have a wifi connection or audio (having the x sign in taskbar).
I tried the whole painfull process three times now while ending up with the same problem. Windows is broken, which means I can't reinstall the bootcamp drivers (crashes system), no system restore points can be restored (failing), I can't reset windows (breaks the boot process and results in a blank screen). I guess this is somehow related to an intercompatibility between bootcamp and Visual Studio 2017.
I'm not sure if this is related to any specific components of VisualStudio which I install. I'll try a minimal install next...
It was the same for me, Windows 10 was loading 5-8 minutes and no keyboard and touchpad support. After 3-5 re-installs(windows and VS2017), found that issue caused by Hyper-V virtualization. It is disabled by default, but as soon as you installed VS 2017 with at least one component which require Hyper-V, you will never be able to login to you windows on macbook pro.
Just DO NOT install any emulators:
Google Android emulator,
Intel hardware accelerated execution manager(HAXM),
Visual Studio emulator for Android,
Windows 10 Mobile Emulator
And Windows will work fine.

Run Android Emulator on Windows 10 with XenDesktop on VM on ESXiHost?

The standard computer lab setup at the school where I work is for the students to connect to a Windows 10 image running XenDesktop on an ESXi host via Citrix Receiver.
We'd like to add Android development to our virtual computer lab, but none of the emulators I've tested will run. Here's what I've tried and the results:
Android ADB that come with Android Studio: Not compatible with Hyper-V, so Hyper-V turned off and ADB hangs with message "Cannot get ADB Version" or similar
Microsoft Visual Studio Android Emulator: It hung when trying to start AVD with message "Starting OS" on AVD. After an hour, I tried to close it and AVD message changed to "Closing operating system" and hung there. I finally closed it with Task Manager.
GenYmotion: It hung when trying to start the AVD. The AVD was an empty window frame.
Has anyone attempted something like this?
The solution turned out to be relatively simple. Use the vSphere 6 Web Client to edit the VM settings, and on the CPU settings, enable "Expose Hardware assisted virtualization to guest OS" (the standalone vSphere client does not have this option). Then restart the VM, install HAXM on the VM, restart the guest OS, and then Android studio and emulator will allow x86 AVDs as usual.

Phone emulator in Visual Studio 2015 RC on Windows 10 preview build 10074 does not work

I had some problem in running some Phone of the emulators in VS2015 RC so I tried to install also the "Pre-release Microsoft Emulator for Windows 10 Mobile" and then also the external SDK ...
Now, even thought I uninstalled the external Windows 10 SDK and made a "repair" of VS2015 RC, no one of the phone emulators stars (it goes till the "OS is starting" phase and then remain in that state till, after many minutes, the emulator crashes and some time a popup says "The emulator is unable to get the sensor states from the device: Operation failed because connection is shut down", ... most of the times no error is reported).
I also tried to delete in the Hyper-V manager both the created emulators virtual machines and the related Virtual Switches related to Windows Phone Emulator Internal: these are recreated at the next run of the emulator from VS, but nothing changed ...
Any suggestion? How can I make at least some of the phone emulators work properly?
Regards
Enzo

App deployment failed, invalid pointer Windows 8 phone SDK

I am using windows phone sdk 8 and visual studio 2012 in windows 8 pro. When i run my application it give this error that application deployment failed and emulator gets shut down. What is solution for that please tell me. Thanks
1- Press (HOME+W) and search for "turn windows features on or off"
2- deactivate the hyperV of ur system
3- apply and ur system will restart
4- activate hyperV again

Window Phone 8 Emulator not starting from visual studio

I've just installed the WP8 SDK, but when I try loading a project I created from Visual Studio it just starts the XDE and displays:
Window Phone OS is starting up
But after about 4 minutes it shuts down.
However, when I start up of the emulator manually, it starts perfectly fine. Any idea what the problem could be ?
This happens when you upgrade your system (windows Update) and modify the drivers on your network configuration. Just use the repair function of the WP8 SDK installation disc.

Resources