I had lots of issues with getting wp8.1 emulator working with visual studio 2013 update 4, although it worked fine with a physical device.
Challenge is that emulator creates virtual machines and then it is a network connection over to the virtual machine.
Looking at the hyper-v manager, I could see that the virtual machine had been created ok, and VSExpress 2013 was starting it ok (and it stopped and restarted each time I hit debug in VSExpress).
My problem was that we use F-secure as a firewall and it was blocking communication.
My fix: activated airplane mode, disabled firewalls then tried again.
2 minutes in, everything was ok – vm had been created (I was deleting them and the virtual switch before starting each run) and connection had been made.
Second time took 5 seconds to run.
I then switched firewall back on, airplane mode off. Even internet worked.
The only thing it did not seem to survive was an overnight sleep state – but that’s ok.
Note, if I use windows firewall, this already ships with the right port rules – but I could not see anything to do with VS or xde, so must be the generic hyper-v ones.
Really difficult for me to see which are the origin ports, as these are dynamically generated. But I can see that on the emulator it is port 135.
Along the way, I came across many useful sources of info…
Simple fix might be to plug in the physical LAN cable – don’t ask, just the way hyper-v virtual switches work… (something to do with sharing same MAC).
Troubleshooting the Windows Phone 8 Emulator
(WP8) Emulator (XDE) Troubleshooting Tips
Windows phone emulator not working (visual studio update 3)?
One possible reason for the behavior you are observing is corrupt Hyper-V settings. To correct that, please follow these steps:
1. Close Visual Studio.
2. Open the Hyper-V Manager.
3. Delete all Emulator virtual machines.
4. From the Virtual Switch Manager, delete all Windows Phone Emulator-related switches.
5. Start Visual Studio and try deploying to the Emulator.
When I did that I then got the error: “you do not have permission to modify internal hyper-v network adapter settings, which are required to run the emulator”
Hit retry – but then it paused on the “Windows Phone OS is starting”.
I then tried other format emulators – did not work.
I then tried launching from the command line – works, but then you do not get the connection between the two:
“c:\Program Files (x86)\Microsoft XDE\8.1\xde.exe” /name “Emulator 8.1 U1 1080P 6 inch.myusername” /displayName “Manual” /video “1080×1920”
My actual command line when executed from visual studio:
“C:\Program Files (x86)\Microsoft XDE\8.1\XDE.exe” /name “Emulator 8.1 U1 1080P 6 inch.myusername” /displayName “Emulator 8.1 U1 1080P 6 inch” /vhd “C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v8.1\Emulation\Images\flash.update1.vhd” /video “1080×1920” /memsize 2048 /diagonalSize 6 /language 409 /bootlanguage 409 /creatediffdisk “C:\Users\myusername\AppData\Local\Microsoft\XDE\8.1\dd.1080×1920.2048.60.gdr1.vhd” /snapshot /fastShutdown
Possible solutions for WP8 SDK Emulator issues – WP8 Hyper-V emulator cannot see the wireless network adapter
I was running on a domain where I am not the admin of the domain (that’s why I think I had lots of problems with hyper-v user privileges. Even adding the domain user in via mmc did not help (note: need to be connected to the domain to do that – otherwise you can only add local users).
I’ve been trying out some combinations of virtualism.
First, the easiest to use is Oracle’s VirtualBox is the easiest to use and is pretty robust. Networking and file sharing is a doddle – unlike some of the other solutions.
Then I use vmplayer, as it is our company standard on our win7 laptops. Really great feauture here is shared folders, but remember to install the extensions before they work properly. (If you cannot see the folders, look in networks).
Finally I use Hyper-V on my win8 laptops. Pass-thru networking and “shared folders” are pretty hard to set up. However by double clicking on the vhdx file, it creates a drive on the host that you can use (so sort of shared folders).
Some other notes:
1. Hyper-V does not exist on win7
2. Hyper-V on vmplayer win8 does not allow you to create/import VMs (you need to be on top of a physical processor), so you just get a connect to option