Windows Phone emulator won't start with a "Another Virtual Machine Manager is running." error - windows-phone-7

I'm using Visual Studio 2010 Express for Windows Phone (with SDK 7.1.1 update) and I'm trying to debug but when the emulator tries to launch, it gives me this error:
Another Virtual Machine Manager is running. Close the other Virtual
Machine Manager, wait for some duration, and relaunch the Emulator.
Anybody know what's going on? I'm running this on a physical machine (not on a VM)

Do you have the Intel (R) Hardware Accelerated Execution Manager (HAXM). that's installed with the latest Android SDK?
If you have installed this component is the Windows Phone 7 emulator will spit out that error, to resolve it you have to uninstall it and reboot.

Related

Windows Phone 8.1 Emulator launches only from Hyper-V Manager

My Visual Studio 2015 Enterprise doesn't launch the emulator, however I am able to run it manually from the Hyper-V Manager. When run it from the VS after ~7-8 mins I get the following error:
"Windows Phone Emulator is unable to connect to the Windows Phone operating system:
The phone did not respond to the connect request.
Some functionality might be disabled"
What might cause this problem? I am running Windows 8.1 on Fujitsu LIFEBOOK E744
My case is slightly different than suggested duplicate as my notebook is in a corporate network and I am not able to turn off firewall nor stop any network monitoring software.

VisualStudio 2013 Express phone emulator - device not found

Step1: Installed VisualStudio 2013 Express for Windows along with
Update 2.
Step2: Created a blank Windows Phone App.
Step3: Deployed the app to the Emulator 8.1 WVGA 4 inch 512MB.
The Emulator Displays with the message 'Windows Phone is Starting'. Times out after about 5 minutes with the following error messages:
Error: DEP6100: The following unexpected error occurred during
bootstrapping stage 'Connection to the device':
Error: DEP6200: Bootstrapping 'Emulator 8.1 WVGA 4 inch 512MB' failed.
Device cannot be found. App deployment failed. Please try again.
Hyper-V Manager shows the phone emulator running when the app is deployed to the
Phone Emulator.
Running my existing phone 8.0 apps with VisualStudio 2012 Professonal through the
phone emulator stopped working after installing VisualStudio 2013 Express with Update 2.
I get this error:
Windows Phone Emulator is unable to connect to the Windows Phone
operating system:
The phone did not respond to the connect request.
Some functionality might be disabled.
Tried running as administrator and repairing VisualStudio 2013 Express with no effect of this problem.
Anyone having similar issues ?
I solved this problem just now. Please take all windows update. Reboot, and check again for any remaining update. This was a bug earlier as well so microsoft fixed it in first update of windows 8.1
Then check any remaining extension update for your visual studio 2013. update there as well.
Try opening a sample app, it should work.
Regards
Kajal
I had same problem . first i fixed it with:
Updating windows
Uninstall / install Windows Phone SDK 8
Remove and add Hyper-v again ( maybe it is not necessary )
But problem came back and instead of previous solution i fixed the issue with :
going to windows firewall and then click on "restore defaults"
Open Hyper-V manager. Look at all the emulators that are running and turn them all off.
Then open visual studio and deploy your app.
This will start a fresh instance of Emulator.
I had the same problem with VisualStudio 2013 Professional and the latest Windows Phone 8.1 SDK and emulators (as of December 2014).
In my case I fixed it by changing the virtual switch 'WinPhoneEmulatorSwitch' in Hyper-V Manager from 'Internal network' to 'Private network'.
I found this solution at pekari.wordpress.com
I had your same problem and after many attempts resolved it this way:
Deactivate Hyper-V (and restart computer);
Go in the Device Manager and open the Network Adapters, here uninstall everything with the name "Hyper-V...", this will allow us to reactivate Hyper-V without any conflict;
Enable Hyper-V (and restart computer);
Finally launch the emulator (if it is the first time you launch it you will have to wait 5-10 minutes, so be patient and wait for it to load all apps it need).

Windows Phone Emulator error, Hyper-V components not running, Windows 8.1 hosted in VMWare Player

Environment:
Windows 7 Enterprise 64-bit as host o/s
Windows 8.1 Enterprise 64-bit hosted in VMWare Player (current version)
Visual Studio Express 2012 for Windows Phone (Update 4)
I get the following error when trying to run a very simple phone app. I know MS says a VM-within-a-VM environment isn't supported, but I know it can work. Has anyone had success with this? Any help is greatly appreciated.
Windows Phone Emulator
The Windows Phone Emulator wasn't able to ensure the virtual machine
was running:
Something happened while starting a virtual machine: 'Emulator WVGA
512 MB.' failed to start. (Virtual machine ID
CADD6546-129A-4683-9A2D-52EAE777E888)
The Virtual Machine Management Service failed to start the virtual
machine 'Emulator WVGA 512 MB.' because one of the
Hyper-V components is not running (Virtual machine ID
CADD6546-129A-4683-9A2D-52EAE777E888).
Prior to seeing the error, the emulator emits the on-screen messages:
Loading ...
The Windows Phone OS is starting ...
And then the error. Of all the Hyper-V services available, the Hyper-V Virtual Machine Management service is the only one which is running.
I've got Windows Phone 8 (and 8.1) emulators working in a VMware Player VM (running Windows 8, obviously) on a Windows 7 host.
You must first check the physical processor supports SLAT. If it does, you can set the "Virtualize Intel VT-x/EPT or AMD/RVI" in your VM's processor settings (Manage/Virtual Machine Settings/Processors). Then make sure the hypervisor.cpuid.v0 is set to "FALSE" in the vmx file for the VM. (exit VMware player before doing this). And you should be good to go.
See http://developer.nokia.com/community/wiki/Windows_Phone_8_SDK_on_a_Virtual_Machine_with_Working_Emulator for a step-by-step guide on how to do this when creating a new VM.

The Windows Phone Emulator wasn't able to set some properties on the virtual machine

I've installed Windows phone 8 SDK successfully and I have run the applications successfully on the emulators. Everything was fine.
Now I have updated my Microsoft Visual Studio 2012 for Windows Phone Version 2 to Version 4.
And I have downloaded and installed the Windows Phone SDK 8.0 Update 3 Emulators. Now I run the application in Emulator WVGA 512MB and the application running successfully.
Now when I try to run the application in Emulator Update 3 1080P, then I am getting the below error.
Please help me how to solve the above issue.
Thanks
WP 8 Emulator works on a virtual machine, so you should check virtual machine settings on Hyper-V. It seems that Emulator needs more memory and your computer has not enough.

Windows Phone 8 SDK Xde emulator runs really slow and Crashes

when you try and run the emulator it will load, then say windows phone OS is starting up, then sit there about 3-5 mins and fail.
Im Running Visual Studio Express 2012 for WP on Lenovo N586 64-bit I've upgraded to windows 8 pro
lemme run down the list of what Ive tried...all are listed here
yes hardware supports hyper-v virtualiztion amd a6-4400m
I'm slat Capable theres a program you can use to test this.
Hyper-v is Installed and running fine
running windows 8 pro I had to upgrade.
Im 64 bit
Im not running any other virtualization software
Ive run XDEcleanup.exe and ran VS2012 as administrator no luck
no im not running on a virtual machine.
and just for fun I've uninstalled the sdk and re installed it
any idea?
For what you're describing, its looks like the VS is trying to create the virtual switch, but failed. To resolve this, go to Hyper-V's Virtual Switch Manager, on the left side of the window, and be sure that you have one virtual switch for every network card you have, usually you must have 3: 1 for the wireless, 1 for the LAN and 1 for internal. If your don't have the wireless or the LAN, create them.

Resources