I've been trying to get the emulator to work for days. Previously I tried the Windows Phone 8.1 Emulator as well as the Windows 8.1 Simulator and both were stuck at loading the OS.
Earlier today I installed the new Windows 10 Tools and thought I should give it another try with the new Windows 10 Emulator... And no, still the same result.
What's strange is that, the Hyper-V Manager seems to be doing OK. I can see the app displays correctly on the little Preview window (see the box on the left side of the picture below).
Also, breakpoints are hit, the project seems to be running OK.
As many answers have already suggested, I tried letting it running for an hour, but still nothing came up.
Things that I've also tried include uninstalling all the Virtual Machines as well as repairing the WP 8.1 Emulator, nothing has worked so far.
Please help, this has driven me completely insane. :(
Update
Not sure if this would help, but if I change the Windows Phone Emulator Internal Switch to use Private network instead of Internal, I will get a couple of warnings saying Unable to determine the Host IP address and then the Emulator will show up with the Emergency Call screen. Not much I can do from there as the three buttons on the bottom are not functioning at all.
I understand that changing the connection type is not the right way to do it, but this at least tells me that the Emulator can work, it's just a matter of how.
I believe you have two Windows Phone Internal Switch connections and one seems to be unplugged while the other is running. Disable the one that is unplugged and leave the latter. This worked for me after 2days of tinkering. God speed.
Try the following.
Open the Hyper-V Manager
In the Actions pane, click Hyper-V Settings
In the Server pane, select Physical GPUs
Uncheck, Use this GPU with RemoteFX
Click OK to save/close.
Attempt to start the Windows Phone emulator VM from within Hyper-V Manager or Visual Studio.
I solved this problem by simply adding XDE.EXE as an exception to my Windows Firewall.
Just today
Many times it is not stuck. It just does take too long to start. I have an 8 core processor and it took like 5 minutes to launch, I tought it was stuck but it did launch.
Not sure if this would help, but if I change the Windows Phone
Emulator Internal Switch to use Private network instead of Internal, I
will get a couple of warnings saying Unable to determine the Host IP
address and then the Emulator will show up with the Emergency Call
screen. Not much I can do from there as the three buttons on the
bottom are not functioning at all.
when you set it to private network, Windows can't interact with your WP Emulator. Open Network Adapter, and try disable and try start emulator again, then enable again this adapter if it is not work *
I contacted the Visual Studio Team a couple of weeks ago and looks like they have fixed this issue in the latest update. And here is how I finally got it all working.
Update your Windows 10 TP to the latest version (currently 10074).
Install the latest Visual Studio 2015 (currently RC).
Install Windows 10 developer tools preview from here (I got
some weird errors with Error code: -2147023294. Ignore them, go
straight to the next step).
Install the standalone Windows SDK for Windows 10 Insider
Preview from here.
Install the Pre-release Microsoft Emulator for Windows 10 Mobile
from here.
That's all! After all these are done, both my Simulator and Emulator are loading up fine.
In my case, deleting the internal switch from Hyper-V virtual switch manager helps, whenever you run your app using emulator as the target, it'll add a new internal switch by itself and the emulator will run normally (no longer stuck on loading screen)
The problem is, I have to do it every single time I restart my PC
The workaround steps to install the Windows SDK and Emulator are no longer needed.
We have released a fix as of 7PM PDT 30 April 2015 for the setup error
Windows 10 SDK 10.0.10069 : The installer failed.
User cancelled installation. Error code: -2147023294"
New setups should no longer encounter this issue.
For existing installations, and for more information, see this forum post:
https://social.msdn.microsoft.com/Forums/en-US/17bc9d5e-2ea7-4149-bb75-23997db8bd25/
This worked for me:
Go to Windows Defender.
Add exclusion following path: "C:\Users\UserName\AppData\Local\Microsoft\XDE\YourEmulatorVersion"
YourEmulatorVersion - for example 10.0.14393.9
2 days, tried all that is posted here but nothing worked! Finally, since it is a lot easier nowadays to (re)install windows without loosing your files (3 hours including updates), I just resorted to that. Same thing happened, but then I saw the alert that I had not yet activated my VS to run in developer mode :) Did that, and voila, the emulator now works.
If this might be helpful: my problem started when I installed Android Studio and disabled Hyper-V from Android. Enabling it back for VS just couldn't get me to run it again. But I hear there is a way to run both Android & VS emulators using VS emulator for Android. I will try to see how that works later...
I know the question is old, but none of the above answers worked for me so I write down my two cents:
Go to Hyper-V console and remove all emulators
Go to Devices Management, under network adapters tree node, delete all virtual switches
Run an emulator from Visual Studio and see the magic happen
I build an easy App in visual studio 2013, creating it through the windows phone project. The main thing is that it's supposed to fetch data from a API of my choice and write to an XML- document. It worked code-wise but depending on what network I was using(Wireless), It gave me either and error or it worked. It worked if I compiled with my phone as the network supplier, but not on my wireless at home or the schools network.
The error I recived everytime was "the thread has exited with code 259"
I googled for some solutions, and I guessed (Not really sure it was the answer I was looking for) that the error was due because of the phone emulator "takes" my PC's IP adress or network.
They told me to just remove my phone emulator on Hyper-V manager and then just re-start my emulation and it should work.
After this was done, all hell broke lose, cause now, visual studio can't even connect to the emulator.It creates a new phone emulator in hyper-v, but can't connect to it. When I try to compile the app I created it says "Trying to connect to "WVGA 512MB" or if I choose another "WVGA 720". It does this for about 3-5 min and then it says "An error occured. Would you like to continue?"
Now I have no idea what to do. I've googled for almost 2 days and I am at lost. I've un-installed, re-installed, repaired all my visual studio but nothing helps. I am using visual studio premium 2013 if that helps..
I guess this is due to the network issues, as you said the emulator takes the default PC's IP address. But normally after removing the emulator from the Hyper-V Manager and when you try to restart it, it should work.
If none of them works try removing all the Virtual Switches from your Virtual Switch Manager which is within the Hyper-V Manager. Then create a new Internal type of a Virtual Switch and restart your machine. Then try launching the emulator.
For more look into these:
Windows Phone 8 emulator can't connect to the internet
Windows Phone 8 emulator error - Something happened while creating a switch
(WP8) Emulator (XDE) Troubleshooting Tips
My VS 2013 setup has been humming along fine for months now. Today I tried to update to Visual Studio 2013 Update 2 RC. Just like last time when I updated to Update 1, setup failed badly with a huge list of packages marked with the "Incorrect Hash Value" error. Unfortunately MS does not have an ISO yet for Update 2 so I can't take that route to complete the update like I did last time. Now I can't run apps on the Windows Phone emulator or on the phone (device) anymore.
I believe that the failed update caused my current deployment problems since the problem surfaced right afterwards. It could be due to some other NuGet package or Extension, but the update is the most likely cause due to the timing of events.
I did extensive reading on SO and tried all the noted solutions. None of them worked:
cleaned and rebuilt the test Windows Phone 8 project (multiple times)
restarted VS2013
rebooted
Exited VS 2013 and restarted it with the Emulator left open (for the Emulator test)
repaired the Windows Phone Emulator install
repaired the VS2013 install
Nothing works. After the IDE installs the app on to the emulator, I still an error dialog box saying:
"The application could not be launched for debugging. Ensure that the target device screen is unlocked and that the application is installed."
And in the VS2013 IDE status line I see the message: "Launching TaskHost.exe failed".
Does anyone know how to fix this? Note, I tried several WP8 projects that I know worked successfully before and none of them can deploy successfully anymore to either the Emulator or the Device.
I see this was asked a month ago, but I had this issue as well. If I left the Emulator running and tried launching it again, I would have TaskHost fail with a different error.
The following was what made it work for me.
Under the following:
Solution(Right-click) > Properties > Configuration Properties > Configuration
Ensure that your main project is set to 'Deploy.'
Have many reason to error.! So, If you doing with database such as SQLLite file or SQL compact file for your project WP, you should check it is used anywhere. Or choose Embed source copy in visual. That's my fail.And i fixed ok!
Did you try from the menus?
BUILD > Rebuild Solution
That worked for me just now.
I just installed Visual Studio 2013 on my machine (which runs Windows 8.1 Enterprise Build 9600). I checked to include the Windows Phone 8 SDK option during install.
Once complete, I launched VS and tried a new Windows Phone App project.
Created and built fine. However. when I tried to run on the emulator, I get the error:
Xap packaging failed. Cannot access a closed Stream.
... and ...
Could not find file 'c:\users\wade\documents\visual studio 2013\Projects\DataBoundApp1\DataBoundApp1\obj\Debug\XapCacheFile.xml'. Please rebuild the solution and try again.
Tried a clean and rebuild but still occurs. Also happens with the data bound app project.
So, I tried installing some of the SDK updates found here: http://developer.windowsphone.com/en-us/downloadsdk. All installed without a problem; however, when I tried again I got the same error.
Note: the emulator starts and runs just fine. The problem is creating the phone package and deploying to the emulator.
I'm not sure how to fix. Anyone have this issue?
UPDATE:
I have tried reinstalling the Windows Phone 8.0 SDK and all the updates. I should note that I also have VS 2012 installed and I also cannot create a Windows Phone 8 app in VS2012.
Here's an image of the WP8 stuff installed:
I resolved this issue by downloading the full Windows Phone 8.0 SDK ISO and installing (followed by a repair on the two updates).
I wish I could better explain how my machine got into this state. My suspicion is it's because I already had VS2012 installed on the machine and VS got into a confused state.
Total time spent? 4-5 hours.
I actually got this error (image below) sometimes (not always), which means my hardware is fine (?).
Everytime I got this error I tried a walk around by starting the VM inside HyperV Manager (After upgrading to Windows 8.1, unable to run Windows Phone emulator without memory error).
But now, even when I started it, it still didn't work (image below).
The errors occurred when I started using Application Deployment to test a xap file in WVGA (not WVGA 512 MB) emulator, the emulator didn't start and after that whatever version of Emulator I tried, the same error appeared.
I tried deleting all the VMs in VM Manager and then started VS and run the emulator again but it still didn't work. I also restarted windows but the problem remained unsolved. I'm using VS2012 and Windows 8.1.
The primary reason behind this is that your machine doesn't have enough available memory for the VM to launch.
Here is a KB article that was recently posted to get around this by setting a registry key that limits the amount of memory available to the host machine.
http://support.microsoft.com/kb/2911380/en-us
I have used the above fix and it worked for me.
This message is telling you that you have insufficient memory on your PC to start this virtual machine.
Try closing down other applications (such as Visual Studio, any Office apps etc), then starting the emulator in Hyper-V manager. Then you can restart Visual Studio etc.
I've noticed this seems to happen to me more often under Windows 8.1 than I remember happening under Windows 8 on a 4GB RAM laptop.