12

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.

enter image description here

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.

enter image description here

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.

Community
  • 1
  • 1
Justin XL
  • 38,763
  • 7
  • 88
  • 133
  • Low chance it might help but... on my machine for the Windows Phone 8.1 Emulator, the actual problem was my AVG Antivirus which was running. Temporarily disabling it, helped the OS in the Emulator to start. – VasileF Mar 24 '15 at 13:26
  • @VasileF I don't have any antivirus ware installed, but thanks anyway! – Justin XL Mar 24 '15 at 14:05
  • I have had luck with cancelling the build then allowing the emulator to finish booting the OS ( couple of minutes). After this I am able to deploy to the emulator. It sounds like you've tried all the other troubleshooting steps. Do you remove and recreate the internal switch? – pumpkinszwan Mar 27 '15 at 05:06
  • It just keeps loading forever in my case. :( Yeah I have already tried countless times recreating the internal switch. What I've found is that my Windows Simulator also behaves the same, which tells me that my Hyper-V is possibly fine 'cause the Simulator is not using Hyper-V at all. There must be something else... – Justin XL Mar 27 '15 at 05:28
  • 2
    @JustinXL Did you manage to make it work? I have the same problem and I cannot make it work for a few weeks now... – Canol Gökel Apr 05 '15 at 18:50
  • @CanolGökel no, I still can't. :( btw, do you have the same problem when you run the Windows Simulator? And what machine are you using? – Justin XL Apr 05 '15 at 20:34
  • @JustinXL Looks like the Windows simulator gets stuck on welcome screen. I am using Asus S400CA with Intel i5 3317U processor, Windows 10 Build 10049. – Canol Gökel Apr 06 '15 at 19:01
  • @CanolGökel so we are having exactly the same issue. I am using a Dell XPS 13. – Justin XL Apr 06 '15 at 21:42
  • Do you have VirtualBox or any VM installed? – csharpwinphonexaml Apr 17 '15 at 06:20
  • @csharpwinphonexaml, no, it's a new machine. :( – Justin XL Apr 17 '15 at 06:22
  • If you connect to it from hyper-v console does it show the app? – csharpwinphonexaml Apr 17 '15 at 06:24
  • @csharpwinphonexaml, yes it does. I can even launch the Hyper V's Windows Phone Emulator (differs from the Visual Studio one of course). – Justin XL Apr 17 '15 at 06:26
  • Do you have any errors in the event log (Try launching "eventvwr" from Command Prompt and search in every event log for errors) – csharpwinphonexaml Apr 17 '15 at 06:30
  • @csharpwinphonexaml I did get a few errors like these. "'Emulator 8.1 WVGA 4 inch 512MB.justin': The Data Exchange integration service is either not enabled, not running or not initialized. (Virtual machine ID D8538902-6816-42FA-9AEA-A6BD44321BE6)"; " Microsoft.Windows.ShellExperienceHost !App for the Windows.Launch contract failed with error: The remote procedure call failed..". They are pretty random though. – Justin XL Apr 17 '15 at 06:36
  • @csharpwinphonexaml also not sure if these are related. "Unable to activate Windows Store app '017d29b2-f894-4012-ae74-235a0d1726c3_gdq1xgtdeqd84!App'. The HubApp81.Windows.exe process started, but the activation request failed with error 'Invalid qualifier value'.See help for advice on troubleshooting the issue."; "Unable to activate Windows Store app '017d29b2-f894-4012-ae74-235a0d1726c3_gdq1xgtdeqd84!App'. The activation request failed with error 'The wait operation timed out'.See help for advice on troubleshooting the issue." – Justin XL Apr 17 '15 at 06:37
  • Let us [continue this discussion in chat](http://chat.stackoverflow.com/rooms/75469/discussion-between-csharpwinphonexaml-and-justin-xl). – csharpwinphonexaml Apr 17 '15 at 06:39
  • Any news about the issue? – csharpwinphonexaml Apr 29 '15 at 14:06
  • 1
    @csharpwinphonexaml I just got it working! Finally! Will post an answer shortly. – Justin XL Apr 30 '15 at 10:43
  • Note: a shortage of disk-space will give the same symptom... – Benjol Aug 12 '16 at 06:29

11 Answers11

7

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.

Grimlock591
  • 71
  • 1
  • 2
  • thanks a lot, that worked for me! I also enabled the "Hyper-V" checkbox in the settings of the internal switch, not sure if that made a difference. – thumbmunkeys Feb 26 '16 at 12:19
  • 4
    @Grimlock591 Can you please explain how to do this? Thanks – Percy Apr 18 '16 at 08:20
2

Try the following.

  1. Open the Hyper-V Manager
  2. In the Actions pane, click Hyper-V Settings
  3. In the Server pane, select Physical GPUs
  4. Uncheck, Use this GPU with RemoteFX
  5. Click OK to save/close.

Attempt to start the Windows Phone emulator VM from within Hyper-V Manager or Visual Studio.

Darrick
  • 21
  • 3
  • I'm using VS2017 with Microsoft Emulator 10 and this was the answer for me. I was getting "The RemoteFX Manager process stopped working and has been restarted." in my event logs. I also had to restart Visual Studio for some reason, but it worked in the end. – George Howarth Sep 21 '17 at 16:47
2

I solved this problem by simply adding XDE.EXE as an exception to my Windows Firewall.

Just today

YIem
  • 31
  • 2
  • 1
    This fixed me up as well! One thing to note, for me anyway, there are multiple versions of the emulator installed. If you go to the C:\Program Files (x86)\Microsoft XDE folder, you'll see all the versions you have installed. – billb Sep 01 '17 at 17:51
1

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.

YouneS
  • 390
  • 4
  • 10
0

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 Putu Yoga Permana
  • 3,980
  • 29
  • 33
0

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.

  1. Update your Windows 10 TP to the latest version (currently 10074).
  2. Install the latest Visual Studio 2015 (currently RC).
  3. 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).
  4. Install the standalone Windows SDK for Windows 10 Insider Preview from here.
  5. 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.

Justin XL
  • 38,763
  • 7
  • 88
  • 133
0

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/

thumbmunkeys
  • 20,606
  • 8
  • 62
  • 110
Paul Chapman
  • 260
  • 2
  • 6
0

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

Yohan
  • 11
  • 1
  • 4
0

This worked for me:

  1. Go to Windows Defender.
  2. Add exclusion following path: "C:\Users\UserName\AppData\Local\Microsoft\XDE\YourEmulatorVersion"

YourEmulatorVersion - for example 10.0.14393.9

user7151260
  • 1
0

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...

Hannington Mambo
  • 998
  • 2
  • 13
  • 28
0

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
fillobotto
  • 3,698
  • 5
  • 34
  • 58