Breadcrumbs

Unable to find displays when wireless casting on Windows / Samsung devices using Miracast (AirServer)

Issue: Cannot find screens when pressing Windows Key + K

When you are unable to discover AirServer using Miracast (used by Windows 10/11 and Samsung devices), there can be a number of possible causes. Note that Miracast makes use of Wi-Fi-Direct and does not rely on local network. It uses a dedicated Wi-Fi access point on the screen, so network configuration should not impact Miracast.

First check: screen renamed?

Has AirServer name on this screen been renamed possibly, then try removing the previous screen-name from Windows:

Windows 10:

  • Press Windows Key + K

  • Choose "Find other types of devices" at the bottom of the sidebar that appeared

  • Find the AirServer which does not work in the list of "Wireless displays & docks"

  • Click it and choose "Remove device"

  • Try to connect again by pressing Windows Key + K 

Windows 11:

  • Right-click “Start”-menu (four squares icon) and click “Settings”

  • Click “Bluetooth & devices” on the left menu and then ”Devices” button in the main area

  • Under “Wireless displays & docks”, select the screen you want to remove and click the three vertical dots

  • Click Remove and try again to connect to the display by clicking Windows Key + K 

Second check: compatible graphics & Wi-Fi hardware?

Miracast mirroring requires a Miracast-compatible graphics adapter/card and a Wi-Fi adapter/card. Check if your computer supports Miracast by following these steps:

  1. Open up a Command Prompt and type:

    PowerShell
    netsh wlan show driver

  2. Command prompt will show you whether or not your device supports Wireless Display (both Graphics and WiFi driver should be ‘yes’)

  3. If your computer does not have a Wi-Fi Adapter or a Wi-Fi adapter that is compatible with Miracast: Download and install/re-install the latest driver updates for your Wi-Fi adapter then restart the computer.

    A picture containing text, screenshot Description automatically generated

Third check: At least NDIS 6.3 driver is required 

  1. Open Powershell and type

PowerShell
Get-NetAdapter | Select Name, NdisVersion

  1. The output will show NDIS version for the Wi-Fi adapter

  2. If the command prompt displays the "The Wireless AutoConfig Service (wlansvc) is not running."-error, you can try to enable it. Instructions are found in this AirServer's support article.

    A blue screen with white text Description automatically generated with medium confidence

Fourth check: company’s IT Group Policy

If you are a corporate user, issue may be related to your company’s Group Policy:

  1. Go to Computer Configuration > Policies > Windows Settings >Security Settings > Wireless Network (IEEE 802.11) to find the Group Policies

  2. If it is named Don’t allow Wi-Fi Direct groups then this is the issue.

    1. Disabling this and re-applying it has fixed Miracast issues for some people. If it is still not working for you please find more related suggestions AirServer's support article.