Microsoft wireless display adapter not connecting to Surface Pro 3

Anonymous

I have a surface pro 3, all updates are complete, I have a new Microsoft wireless display adapter bought in the US, tried to use it on 2 different HDTV's today and I can't get the surface to connect to the adapter. I can see it paired, its on my surface as a device, I can see the adapter setup on the TV's HDMI channel, but when i try to connect the screen tries to connect, but then fails, no error not message, just says can not connect on the surface..

The name of the adapter on the TV and on the device list on the surface is MicrosoftDisplayAdapter_E8

I have tried it on a samsung and finlux TV, both only a few years old, and have powered USB so not sure what proble is

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous

Found the issue in my firewall, just need to figure out now how to apply a rule

0 comments

Answer accepted by question author

Anonymous

Here's how I fixed the problem without a system reset.

Go into Device Manager and from View make sure show hidden devices s selected.
There should now be an item that has an exclamation point. Remove it and all of the devices with the same name followed by #1 #2 etc if there are any. I'm sorry that I didn't make a note of what it was and I can't remember. But if this is your problem, it will be there. Make sure to uninstall all of the same named devices.
Restart. Do not rescan. I tried that and it didn't work. I had to restart to make it work.
After a restart I slide in from the right side and selected Devices from Charms. I selected project and the Add a Wireless Display was back. I tapped it and it found the MS Wireless Display Adapter. I connected and it worked fine.

0 comments

Answer accepted by question author

Anonymous

I'm sure this has been resolved already...however...I had the same issue with my Surface Pro 3 and would like to share what resolved the issue. It seems this is an inherent Microsoft issue that haunts them since Windows 98. I remember having graphic card issues back then and I quite simply deleted the graphics driver from the Device Manager. That's right deleted - then reboot.

The MS Display Adapter works beautifully with my BlackBerry Z30...two clicks and I was connected. Therefore, it's not the adapter. The fix is the following with Surface Pro 3:

Search for Device Manager > Double click Display Adapters > Right click Intel HD Graphics Family > Click Unistall > Check "Delete driver software for this device" > Click Ok > Reboot > Once fully rebooted, follow instructions to install MS Display Adapter (open right charms > Devices > Project > MS Display Adapter...) then bingo! You are now connected.

Worked like a charm! ;)

0 comments

Answer accepted by question author

Anonymous

"If you have a firewall, temporarily disable it. If you have AVG, open the program and click on "Firewall". Click on "change" to the right of the "Firewall Mode, Automatic". Select the bottom button that says "Disable Firewall (not recommended)" and click "apply". (This made me nervous, but AVG assured me that my virus scan was still active, and said that I could reactivate my firewall when finished with my display). I attempted to pair the devices and the projector works PERFECTLY. I can't speak to other firewalls, but my hunch is that by temporarily disabling them, the devices should connect. Hopefully this information is helpful. Please let me know if this works for you!"

The info on conflicts with firewalls and AV programs is including in the Wiki article on Trouble Shooting Miracast.http://answers.microsoft.com/en-us/windows/wiki/windows8_1-networking/trouble-shooting-miracast/51d24be3-8d15-4c29-8e13-767ec365fbd8

item #3.

0 comments

Answer accepted by question author

Anonymous

I've had the same issue: MWDA was detected by SP3, but when I tried to connect, the SP3 screen flickered and connection was lost...

I was doing this as a non-admin... After I logged in as administrator it worked. Now it also works on my non-admin account. Might be a coincidence, but I'm glad it works now ;-)

0 comments

175 additional answers

Anonymous

2015-05-23T22:03:10+00:00

I got the MWDA to work although not sure what if any of the following may have been the trick.

1. Looking at the Device Manager, there was a device driver problem (yellow splotch) with the IWD Bus Emulator (Control Panel --> Device Mgr --> System devices) but it was just asking for a restart (which I had probably done 20 times since the System Update). Restarted Pro 3 which resolved the IWD Bus Emulator problem.

2. Uninstalled and reinstalled the Microsoft Wireless Display Adapter App. After the system update, the icon for this app said exactly that App. After initially attempting the MWDA, the app's icon did change to Microsoft Wireless Display Adapter so even though I didn't use the app something seemed to have happened to the app after the system update. My Facebook app also cratered after the system update so I had uninstalled and reinstalled that app which resulted in the same actions for the MDWA app.

3. Turned on the WiFi for this last successful exercise but I can't believe this had anything to do with process but if the MWDA needed a update at the Surface Pro 3 end (it doesn't show in the Device Manager unless it is connected), I figured it best to have a path for any possible update -- for which there was none.

Recommendations: Check from stem to stern the Surface since for me the May system update brought along its commensurate series of problems. I would go through every device displayed in the Device Manager. A detailed review of the Apps might be in order also. The desktop had a number of issues (duplicate shortcuts for one) as did the Start screen (Facebook, Store and App which I finally figured was the MDWA app). Uninstalling and reinstalling took care of the problems associated with the apps.
Was this answer helpful?

0 comments No comments