If the projecting device is running Windows, it should be Windows 8.1 or newer for full Miracast support. It is also possible that the connect issue can be the result of a problem on the connecting device. Generally speaking, you will want to use channels that do not show heavy utilization from the network scan. You will need to restart Surface Hub after each change. You can manually select the Miracast channel in Settings. For troubleshooting purposes, disconnect Surface Hub from any Wi-Fi networks (but keep Wi-Fi enabled), so you can control the channel used for Miracast. When Surface Hub is connected to a Wi-Fi network it will use the same channel settings as the Wi-Fi access point for its Miracast access point. If Surface Hub's Miracast network shows up on the scan, but you cannot not see it as an available device, you can try to adjust the Miracast channel used by Surface Hub. If you ran a network scan, you should see Surface Hub Miracast listed as an access point. Connect issuesĮnsure both Wi-Fi and Miracast are both enabled in Settings on Surface Hub. Running a network scanning tool will show you the available networks and channel usage in the environment. In either case, it is a good idea to get a general picture of wireless network activity in the Surface Hub's location. There are generally two types of issues with Miracast to Surface Hub: connection and performance.

If Surface Hub is connected to a Wi-Fi network, the access point, it will use the same channel as the connected network, otherwise it will use the Miracast channel from Settings. After that initial handshake, the projecting device sends traffic to the monitor using the wireless channel settings on the monitor.The first step is an initial connection using 2.4GHz.Miracast AGO is a two-step connection process: In traditional Miracast, the projecting device will connect the access point set up by the Miracast-enabled monitor, and then the monitor will send traffic back to the projecting device using the network channel of the projecting device. However, in most cases, these devices are not using Miracast AGO and do not handle wireless projection the same way that Surface Hub does. A common troubleshooting step when projecting wirelessly to Surface Hub fails is to test projecting to another wireless monitor or adapter. Surface Hub uses a slightly different version of Miracast known as Miracast Autonomous Group Owner (AGO). Most wireless monitors and adapters available today use the original implementation of Miracast. Surface Hub supports wireless projection through the Miracast protocol.

Miracast windows 10 step by step