UMDF Version History
This topic lists versions of User-Mode Driver Framework (UMDF), the corresponding versions of the Windows operating system, and the changes made in each release.
The following table shows the release history of the UMDF library:
|UMDF version||Release method||Included in this version of Windows||Drivers using it can run on|
|2.29||Not released in WDK||Windows 10, version 1903 (March 2019 Update, 19H1)||Windows 10, version 1903 and later|
|2.27||Windows 10, version 1809 WDK||Windows 10, version 1809 (October 2018 Update, Redstone 5)||Windows 10, version 1809 and later|
|2.25||Windows 10, version 1803 WDK||Windows 10, version 1803 (April 2018 Update, Redstone 4)||Windows 10, version 1803 and later|
|2.23||Windows 10, version 1709 WDK||Windows 10, version 1709 (Fall Creators Update, Redstone 3)||Windows 10, version 1709 and later|
|2.21||Windows 10, version 1703 WDK||Windows 10, version 1703 (Creators Update, Redstone 2)||Windows 10, version 1703 and later|
|2.19||Windows 10, version 1607 WDK||Windows 10, version 1607 (Anniversary Update, Redstone 1)||Windows 10, version 1607, Windows Server 2016 and later|
|2.17||Windows 10, version 1511 WDK||Windows 10, version 1511 (November Update, Threshold 2)||Windows 10, version 1511, Windows Server 2016 and later|
|2.15||Windows 10 WDK||Windows 10, version 1507 (Threshold 1)||Windows 10, version 1507, Windows Server 2016 and later|
|2.0||Windows Driver Kit (WDK) 8.1||Windows 8.1||Windows 8.1 and later|
|1.11||Windows Driver Kit (WDK) 8||Windows 8||Windows Vista and later|
|1.9||Windows 7 WDK||Windows 7||Windows XP and later|
|1.7||Windows Server 2008 WDK||Windows Vista with Service Pack 1 (SP1), Windows Server 2008||Windows XP and later|
|1.5||Windows Vista WDK||Windows Vista||Windows XP and later|
You can use the Windows Driver Kit (WDK) with Microsoft Visual Studio 2017 to build drivers that run on Windows 7 and later.
For help determining what version of WDF to use, see Which framework version should I use?.
For information about the new features for UMDF drivers in Windows 10, see What's New for WDF Drivers.
UMDF Version 2.29
Unchanged from version 2.27.
UMDF Version 2.27
- Added new API WdfDriverRetrieveDriverDataDirectoryString
UMDF Version 2.25
UMDF Version 2.23
- Companion functionality added for internal use only. For the new DDIs, see Summary of WDF Callbacks and Methods.
UMDF Version 2.21
- WdfObjectDereferenceActual: Type of File parameter changed from PCHAR to PCCH.
- WdfObjectReferenceActual: Type of File parameter changed from PCHAR to PCCH.
UMDF Version 2.19
There are no changes or additions for UMDF Version 2.19.
UMDF Version 2.17
This version adds UMDF support for the following existing interfaces:
For more information, see Dispatching IRPs to I/O Queues.
UMDF Version 2.15
Here is the list of updated DDIs for version 2.15:
The new WdfDeviceOpenDevicemapKey method allows a driver to access subkeys and values under HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP.
A UMDF driver can call WdfIoTargetWdmGetTargetFileHandle to obtain a file handle to the next-lower kernel-mode driver in its stack. The driver can write data to that handle, bypassing the framework's abstractions for sending I/O to the local I/O target.
A UMDF driver can request that the underlying bus driver re-enumerate it. See WdfDeviceSetFailed.
Setting the UmdfDirectHardwareAccess directive is no longer always necessary for devices that have connection resources. See Specifying WDF Directives in INF Files.
UMDF Version 2.0
In addition to the shared functionality described in Getting Started with UMDF, UMDF version 2.0 adds:
Support for timers that do not wake the system if they expire when the system is in a low-power state. For more information, see Using Timers.
Added CanWakeDevice member to WDF_INTERRUPT_CONFIG structure to support interrupts that can be used to bring a device from a low-power Dx state back to its fully on D0 state. For more information, see Using an Interrupt to Wake a Device.
Single-component, single-state (F0) power management for UMDF drivers. For more information, see WdfDeviceAssignS0IdleSettings.
Several debugger extension commands in Wdfkd.dll can now be used for UMDF 2.0 drivers as well. The extension library also contains the following new extension commands designed specifically for debugging UMDF 2.0 drivers:
For a list of extension commands and framework applicability, see Debugger Extensions.
The framework's event logger, or In-flight Recorder (IFR) has been updated to work for UMDF 2.0 drivers.
Other WDF debugger extensions have been updated to work with UMDF 2.0 drivers. For a full list of extension commands, including information about which ones apply to which framework, see Debugger Extensions for WDF Drivers.
Added WdfIoTargetOpenLocalTargetByFile to WDF_IO_TARGET_OPEN_TYPE to allow UMDF drivers to send driver-created requests to lower targets that require an associated file object. For more information, see the Remarks of WDF_IO_TARGET_OPEN_TYPE.
The following UMDF-only routines:
- WdfFileObjectGetInitiatorProcessId (added to KMDF 1.21)
- WdfRequestGetRequestorProcessId (added to KMDF 1.21)
The following KMDF/UMDF methods described in Accessing the Unified Device Property Model:
For more information, see Accessing the Unified Device Property Model.
Support for the following USB configuration types in WdfUsbTargetDeviceSelectConfigType:
Support for querying the following capability types in WdfUsbTargetDeviceQueryUsbCapability:
UMDF Version 1.11
Version 1.11 adds the following driver-supplied callback interfaces and event callback functions:
Version 1.11 adds the following framework-supplied interfaces:
Version 1.11 adds the following capabilities to UMDF-based drivers:
Added UmdfHostProcessSharing, UmdfDirectHardwareAccess, UmdfRegisterAccessMode, UmdfFileObjectPolicy, and UmdfFsContextUsePolicy directives, described in Specifying WDF Directives in INF Files
Unified property store support, described in Using the Registry in UMDF-based Drivers
IoGetDeviceObjectPointer is integrated to work with UMDF. In prior versions, this routine closes the handle to the device object after taking a reference on the device’s handle. This behavior was incompatible with UMDF’s expectation that the cleanup request on the device object won’t occur until after all the I/O is complete.
Enhanced support for Supporting Idle Power-Down in UMDF-based Drivers. The framework can now put the device in the D3cold power state when the idle timeout period expires. The framework can also cause the device to return to its working (D0) state when the system returns to its working (S0) state.
UMDF Version 1.9
Version 1.9 adds the following driver-supplied callback interfaces:
Version 1.9 adds the following framework-supplied interfaces:
These interfaces add the following capabilities to UMDF-based drivers: