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
Help to understand what happens when you update the application with a background agent...
I have application for WP8 with background agent. User install
app from store, run app and run background agent.
In new version of app I'm modify code of background agent, publish
new version to store.
User upgrade app from store, but not run main application.
What happens in this case?
On the device, there is a new version of the application, but not until the background agent was restarted from the new version of the main application, in remembrance remains running and running an old copy of the background agent?
That is, the application renewed, but still works a background agent from the old version of the application?
Found in testing.
After the application is updated the next time the agent starts a new instance of the agent of the background of the new version of the application.
I would like to move my WP8 development to a virtual machine. I know that the emulator won't run on top of a VM, so I'm wondering if I can deploy & debug directly to the device (via regular old USB). RemoteFX allegedly performs "USB redirection" which I assume is supposed to magically connect the phone up to my RDP session, and thus enable deployment. I was able to establish a RemoteFX connection with my VM, however when I try to deploy to my phone Visual Studio (within the VM) claims it cannot find a phone. (yes, I verified my phone is connected to my local machine)
tl;dr Does anyone know how to deploy to a physical Windows Phone from within a VM?
I see that this is the first link that appears in google search for this problem. I am going to present you the solution from what it is there is Nokia development articles. Please go through link.
The only important thing is to enable Intel VT-x option.
I am in the finishing staging of creating my first Window Phone 8 application. I am using MVVMCross as the MVVM framework for the application. The application is running great in debug mode on both the simulator and my connected phone. The issue I am having is the application will not run on my phone unless it's attached via debugging. When I click on the application on the phone it simply flashes but never launches the application.
Some additional information after using Crittercism to catch the exception:
0 at Cirrious.CrossCore.Mvx.ResolveTService
1 at Mobile.Contacts.Phone.App.b__0()
After further review I realized that I had the following setup code inside
if (System.Diagnostics.Debugger.IsAttached)
var setup = new Setup(RootFrame);
setup.Initialize();
I develop small web base ASP applications that basically store and display data from a backend MsAccess database.
The application websites are developed and tested on my local machine (the finished work eventually gets published to a company web server).
To run the development web server on my XP machine I did not load any additional software. I believe that I was running IIS 5 ? and this setup was running 100%.
I just loaded a Visual Web Developer – Express Edition to help my development and this after two hours of installation time it appears that it gave me an upgrade to my IIS (to version 7) without notifying me if I wanted to load that.
Now all the development .asp pages on my machine no longer run.
Note: the initial pages appear but anytime I hit a “submit” button I get the error:
destination page can not be found or is no longer available
Is this a IIS 7 configuration issue?
Where do I go to change the configuration ? what needs to be changed to get a .asp page to “post”?
Can I Uninstall the IIS seven and get back to the older version if IIS ?
on IIS7 ASP is disabled by default. you need to activate that in the IIS7 config. I belive it is an ISAPI Module.
Which version of Windows XP are you running? If you have anything below Proffessional, you probably got upgraded to II6 and not II7 - there is no II7 for lesser versions.
Moving on to what to do if you have II7. (I'm running Vista, but I believe these configuration tools look roughly the same).
Open the IIS Manager from Administration Tools (under Start/Programs)
Expand your web server (the node with your local computer name), then expand Sites and select the site you want to activate ASP for.
Under "IIS" there is a setting called "ASP". On the right hand side of the configuration tool there is a bar with labeled "Actions" - I believe you need to find the Start option under Manage Web Site.
IIS is part of the OS. So unless you upgrade your OS, it will remain the old version.
If you are using Windows XP 32-bit, then IIS 5.1 is there.
If you are using Windows XP 64-bit, then IIS 6. is there.
One point is that Visual Web Developer is for ASP.NET development mainly. So if you are developing classic ASP, it does not help much.
If now all your classic ASP pages fails, can you test with a simple hello world page? If you can see that page without a problem, then actually IIS serves ASP without a problem.