In this call, the operating system also provides pointers to callback functions that the driver can call during the lifetime of the current Miracast context. When this function is called, the Miracast user-mode driver allocates all the software resources it needs to start a Miracast connected session. When the operating system is ready to prepare for a Miracast connected session, it calls the Miracast user-mode driver's CreateMiracastContext function. For example, a 64-bit version of the driver is used on a 64-bit processor.
This driver binary must not use an existing Direct3D user-mode display driver DLL.īecause the Miracast user-mode driver is loaded into the UMDF0 process, no separate Windows on Windows (WOW) version of this driver is needed. The DLL should have an export function named QueryMiracastDriverInterface that the operating system can call. HKR, MiracastDriverName, %REG_SZ%, Miracast.dll Add the name of the driver in device software settings in the INF file as MiracastDriverName: This driver is loaded in a dedicated session 0 process. To enable Miracast wireless displays on windows 8.1, you need to create a standalone, unique DLL that implements a Miracast user-mode driver. Microsoft might remove support for custom Miracast stacks in a future version of Windows. The relevant WHLK documentation at .WirelessDisplayĭriver developers should no longer implement a custom Miracast stack. For information about the Microsoft Miracast stack and the requirements of drivers and hardware to support Miracast displays starting in Windows 10, see the following documentation:īuilding best-in-class Wireless projection solutions with Windows 10 Starting in Windows 10 (WDDM 2.0), the operating system ships with a built-in Miracast stack that can work on any GPU.