Windows Phone 8 emulator can't connect to the internet

Question

I have Windows 8 installed inside of an emulator, and the new WP8 SDK installed on it. My problem is that the emulator can\'t connect to the internet. I don\'t have any prox

Answer 1

After installing Windows Phone Emulator on my Yoga laptop, I immediately had the following problems:

• emulator apps cannot reach the internet
• host computer internet connection is terribly slow and almost unusable

I was discouraged and thought I would have to do some drastic and desperate acts to fix things, but got lucky with the following steps which completely solved my problems (for now). The steps are verbose (intended for the readers' benefit), but are actually very simple in practice.

....0: Unplugged ethernet cable (to remove it from the equation) but stayed connected to WiFi. Problems still remain but at least there is less complexity now.

....1: In Control Panel / Network Connections / Change Adapter Settings, deleted Network Bridge (required for Step 2 to work).

....2: Opened Hyper-V Manager, right-clicked on the emulator VM item and selected Virtual Switch Manager. Selected "Windows Phone Emulator Internal Switch" and changed the radio button from Internal to External (this was only possible after deleting the Network Bridge (Step 1)).

At this point, the emulator can now connect to the internet (and Control Panel shows WPEIS finally 'has internet access'); however deployment of WP build binary from VS to emulator fails - it just hangs when I try to build-and-deploy from Visual Studio (so a new problem has surfaced (temporarily)).

....3: Returned to HyperV Manager, went back to Emulator VM's Virtual Switch Manager and reverted Windows Phone Emulator Internal Switch from External back to Internal.

I can now successfully build-and-deploy WP build from Visual Studio to emulator. And emulator retains its networking ability. Also the host machine's network connection also returned to healthy.

I hope this helps someone. Good luck!

Answer 2

I went through many of the suggested solutions, also with no luck. What finally worked for me was to fix a vmware warning about guest OS trying to set promiscuous mode for ethernet adapter (http://kb.vmware.com/kb/287).