6 Appendix A: Product Behavior

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include updates to those products.

  • Windows 10 v1703 operating system

  •  Windows Server 2019 operating system 

  • Windows Server 2022 operating system

The terms "earlier" and "later", when used with a product version, refer to either all preceding versions or all subsequent versions, respectively. The term "through" refers to the inclusive range of versions. Applicable Microsoft products are listed chronologically in this section.

Exceptions, if any, are noted in this section. If an update version, service pack or Knowledge Base (KB) number appears with a product name, the behavior changed in that update. The new behavior also applies to subsequent updates unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms "SHOULD" or "SHOULD NOT" implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term "MAY" implies that the product does not follow the prescription.

<1> Section 2.2.8.5:  The Windows Sink implementation adds a single IP Address attribute with an IPv4 address.

<2> Section 3.1.3:  The Windows 10 v1703 through Windows 10 v1803 operating system Sink implementation does not support stream encryption, therefore it will not set the StreamSecuritySupported bit in the Capability attribute (section 2.2.8.1).

<3> Section 3.1.3:  The Windows 10 v1703 through Windows 10 v1803 does not support PIN entry, therefore it will not set the PinSupported bit in the Capability attribute (section 2.2.8.1). The Windows 10 v1809 operating system and later and Windows Server 2019 and later Sink implementation allows the PinSupported bit to be configurable.

<4> Section 3.1.5.2:  The Windows Sink implementation rejects new connections except on the Surface Hub SKU, where the new connection replaces the existing one.

<5> Section 3.2.5.1:  The IP Address attribute (section 2.2.8.5) is not supported in Windows 10 v1709 operating system and earlier implementations.

<6> Section 3.2.5.1:  The Windows implementation uses a period of 1.5 second for the Discovery timer.

<7> Section 3.2.5.1:  The Windows implementation attempts both DNS and mDNS in parallel and uses the first one to respond; however, when connected to a virtual private network (VPN), mDNS is preferred, so if the Windows implementation gets DNS results, it still waits for mDNS to complete or time out.

<8> Section 3.2.5.3:  The Windows implementation uses a period of 5 seconds for the Control Channel Connection timer.

<9> Section 3.2.5.3:  The Windows implementation of the Source chooses the first IP address in the set.

<10> Section 3.2.5.4: On Windows 10 v1703 through Windows 10 v1803 the Source implementation does not support stream encryption.

<11> Section 3.2.5.4: On Windows 10 v1703 through Windows 10 v1803 the Source implementation does not support PIN entry.

<12> Section 3.2.7.1:  The Windows Source implementation will normally fall back to standard Miracast if the connection establishment fails. However, a Group Policy setting may be configured to disallow standard Miracast over Wi-Fi Direct. In that case, if the connection establishment fails, the entire connection attempt fails.

<13> Section 5:  The Windows implementation does not attempt a Miracast over Infrastructure connection over a wireless network, if the wireless network it is connected to does not employ link layer security (WPA2).