Microsoft Wireless Display Adapter

Hi BPEARSO2,

All Miracast-compatible devices should work with the Microsoft Wireless Display Adapter (MWDA), including the Surface Go. What error do you get when you connect the Surface Go to your external display via the MWDA?

Additional steps regarding the setup can be found here. Try to install and run the Surface Diagnostic Toolkit (SDT) as well. This will further ensure that you have the best driver and firmware for the setup and look for other possible software issues that comes between the connection. Perform a forced shutdown after running the SDT by pressing the power button for about 10 seconds. Restart the Surface normally afterwards.

You can also install the Microsoft Wireless Display Adapter app to connect the devices easier.

Kindly update the post with the results. I'll be able to check on the situation if you do and I'll get back to you the soonest I can if further help is needed.

Regards.

Ruz, I appreciate your assistance. I downloaded and ran the Microsoft Surface Diagnostic Toolkit. The toolkit did not find anything wrong with my Surface Go.

When I attempt to connect my Surface Go to the Microsoft Wireless Display Adapter, a text message appears briefly on the external video display (the video display that is connected to the Wireless Display Adapter), The text message says "Connecting to SURFACEGO" but the connection is not successful. Both the Surface Go video screen and the external video screen that is connected to the Wireless Display Adapter go black for a moment and the wireless connection fails. I installed and ran the Wireless Display Adapter App on my Surface Go but the App does not help with the wireless connection.

I have a Windows 10 desktop computer. The desktop computer is able to connect to the Microsoft Wireless Display Adapter so there dose not appear to be anything wrong with the Wireless Display Adapter. I installed the Wireless Display Adapter app on my Windows desktop computer and used the Wireless Display Adapter App to update the firmware on the Wireless Display Adapter to version 2.0.8381. Unfortunately, the firmware update did not fix my inability to connect my Surface Go to the Wireless Display Adapter.

My guess is that there is an incompatibility between the Surface Go's, Intel HD Graphics 615 display adapter software driver and the Microsoft Wireless Display Adapter. I used the Windows Device Manager (on the Surface Go) to uninstall and reinstall the Intel HD Graphics 615 display adapter, but that did not help. This does not appear to be a wireless communication problem between the Surface Go and the Wireless Display Adapter.

Barb, thank you for you time and attention to my problem. I switched out of S Mode on my Microsoft Surface Go. I currently have Windows 10 Home, Version 1803, OS Build 17134.376 installed on the Surface Go.

The Surface Go has a rather non-standard screen resolution of 1800x1200 pixels. The Microsoft Wireless Display Adapter may not be compatible with this non-standard display resolution.

I tried resetting the Wireless Display Adapter by holding down the button on the Wireless Display Adapter for 10 seconds and waiting for the adapter to restart. This did not help. I have also tried connecting the Wireless Display Adapter to three different video displays/TV screens. I have the same connection problem on all three video displays.

Barb, changing the resolution of the video display on the Surface Go to 1280x720 did not help. I am still unable to connect to the Wireless Display Adapter. Here is the output from the command that you requested:

When I attempt to connect my Surface Go to the Microsoft Wireless Display Adapter, a text message appears briefly on the external video display (the video display that is connected to the Wireless Display Adapter), The text message says "Connecting to SURFACEGO" but the connection is not successful.

I think that represents a transition between SSID that we don't have clear documentation about.  FWIW what I do when this happens is use some PowerShell diagnostics to try to understand what is going on

Get-NetConnectionProfile  

should show you a  DIRECT-  SSID

Heh.  Now it has to prove to me I'm wrong.  I'm seeing the full DIRECT-xxx<Local Host>xxx  name even though I'm not connected to it.

However, this has reminded me that it is also essential to Remove any previous instance of the same "Display device" in Bluetooth and Other devices.  And make sure that both the Audio and Video sides get removed at the same time.  E.g. it may be OK to see signs of the MWDA in the Connect dialog (Win-k) but as long as you can't get a connection it would not be OK to have it still listed in there, probably because the first would be the DIRECT- thing (or who knows perhaps a new DIRECT-xxx<Local Host>xxx thing) while the other would be a DIRECT-yyy<Local Host>yyy thing.

In any case, the other PowerShell diagnostic I use is

Get-NetAdapter  -IncludeHidden  |  sort  MACAddress  |  ft  -AutoSize

I like that Sort stage in case it would highlight conflicts by MAC Address.  I occasionally see one but fortunately not by two connections that I would want to have active at the same time.   Note that the one you would be interested in will be a  Wi-Fi Direct one called Local Area Connection*.

There is also a Network troubleshooter that now at least recognizes that there is an adapter involved in this process but it doesn't seem to be clued in about what it is being used for.   (E.g. Local Area Connection* once was not listed.  So there has been some progress in this area but in my experience it always uselessly reports "No trouble found" but more importantly never changes the symptom.)   YMMV.

Good grief.  Cortana isn't letting me see the Network Adapter troubleshooter.  You may need to get to it via Control Panel Troubleshooting.  Here's a PowerShell pipeline to assist with that

Get-ControlPanelItem Tr* | Show-ControlPanelItem

FYI

Robert Aldwinckle

---

I appreciate the detailed recommendations and support that I have received from this forum. It appears there is not an easy solution to my wireless display adapter connection problem. I am going to give up on trying to get this working for now. The wireless display is not a critical computing function because I can use a hardwired video connection when necessary. Troubleshooting the problem has already consumed over two hours of my time so it is probably not worth pursuing any further.

Thank you