Miscellaneous technical details and validation

Article
03/18/2021

Verifying that you are running a WDI driver

You can validate that a Wi-Fi driver is a WDI driver by typing the following at a CMD prompt:

NETSH WLAN SHOW WIRELESSCAPABILITIES

This returns a list of values in the output including:

> WDI Version (Windows)
> WDI Version (IHV)

If these values are all zeros, (e.g. 0.0.0.0) then this is not a WDI driver. If these values are non-zero, a WDI driver is present. This is an example of the return values from a WDI driver:

> WDI Version (Windows) : 0.1.0.21
> WDI Version (IHV) : 0.1.0.1

Verifying that your PC can support Miracast

You can validate the Wi-Fi and Graphics drivers declare support for Miracast by typing the following at a CMD prompt:

NETSH WLAN SHOW DRIVER

This returns a list of values in the output including:

> Wireless Display Supported: Yes (Graphics Driver: Yes, Wi-Fi Driver: Yes)

Verifying that WPS Information Elements (IEs) are being sent properly

You can validate that the Windows 10 device can properly parse the Miracast receiver's Manufacturer, Model and Model-number values by performing the following: Connect to the Miracast receiver, then go to Device Manager, and look under Software Devices. Here you will see the Miracast receiver name listed. Look at its Properties. On the Details tab look for the following 3 properties: PnP-X manufacturer, PnP-X model name, and PnP-X model number.

Validating a receiver's properties without connecting

From an Administrator-level CMD prompt launch P2PApplication.exe and perform the following commands:

sccm

verbose

cmd

You will be presented with output such as the following which details properties from nearby receivers:

>        001) MSDisplayAdapter_91             : WiFiDirect#9A:5F:D3:03:0D:91 (9A:5F:D3:03:0D:91) Miracast
>                          InfraCast Supported: False
>                                 Manufacturer: Microsoft
>                                   Model Name: MWDA
>
>
>        002) jzen                            : WiFiDirect#DC:FB:48:00:54:1B (DC:FB:48:00:54:1B) Miracast
>                          InfraCast Supported: True
>                                 Manufacturer: Microsoft
>                                   Model Name: Windows PC
>          InfraCast Stream Security Supported: True
>                      InfraCast PIN Supported: False
>                           InfraCast Hostname: jzen
>                     InfraCast IP Address(es): 10.137.188.135
>                                               2001:4898:d8:32:f5e5:2907:3a85:110f

Verifying that IP address allocation is occurring in EAPOL-key frames

To validate, use a wireless sniffer. The IP address request KDE and IP allocation KDE appear in the EAPOL-key exchange frames. Alternatively, there will also be an absence of the DHCP exchange.

Verifying that the PC's Wi-Fi driver supports Extended channel switch announcement (eCSA)

How to validate: You can validate that a WDI Wi-Fi driver supports eCSA by performing the following at a CMD prompt:

NETSH WLAN SHOW WIRELESSCAPABILITIES

You will see a list of values in the output including the following:

> Extended Channel Switch Announcement : Supported

Validating support for a hardware cursor

A Miracast sink vendor can use the hardware cursor validation tool and a small suite of cursors to validate their hardware cursor implementation. For additional info, see [MS-WDHCE]: Wi-Fi Display Protocol: Hardware Cursor Extension

Validating Window 10 Miracast extensions

Windows 10-based Miracast source and sink support all the above Miracast extensions. When creating a Windows 10-based Miracast source and sink you can validate that the extension is supported using an over the air sniffer. Section 3 of [MS-WFDPE]: Wi-Fi Display Protocol Extension provides an M3 request and response for each extension defined in this document.

Share via