What's new in driver development
This section provides information about the new features and updates to Windows driver development in Windows 10.
The following is a list of new feature highlights for driver development in Windows 10.
- Windows 10, version 1903 WDK supports Visual Studio 2019
- Windows Hardware Dev Center dashboard
- Open publishing
- Debugging Tools for Windows
- Device and Driver Installation
- Driver Verifier
- Windows Driver Frameworks
- Universal Windows drivers
- Windows Compatible hardware development boards
- Power Management Framework
- System-Supplied Driver Interfaces
- WPP Software Tracing
The following table shows the feature updates in Windows 10, by driver technology and version.
|Buses and Ports|
|Human Interface Device (HID)|
|Near Field Communication|
|Pulse Width Modulation|
|System-Supplied Driver Interfaces|
What's new in driver development for Windows 10
This section provides highlights of new features for driver development in Windows 10.
WDK supports Visual Studio 2019
The Windows Driver Kit (WDK) for Windows 10, version 1903, has been updated to support Visual Studio 2019 as previously announced. This release of the WDK is not compatible with Visual Studio 2017 however, developers can continue working with Visual Studio 2017 using the previous releases of the WDK, (releases 1709 thru 1809 found here). To learn about what is new with Visual Studio 2019 please review the information here.
The following are a few items of notable changes in Visual Studio 2019 that Windows driver developers will see.
WDK GUI Driver Menu moved
In Visual Studio 2019 the WDK Driver menu has been moved to live under the Extension menu as seen below.
The WDK Driver menu in Visual Studio 2017 is located in the top menu options as seen below.
Driver Templates discoverability
In Visual Studio 2019 the WDK Driver templates will be discoverable under Project Type, Drivers. The Driver Project Type will appear in the first official update release of Visual Studio 2019. Until then the Driver templates can be discovered by searching for them in the search menu.
The WDK Driver templates were previously found in Visual Studio 2017 under New Projects> Visual C++> Windows Driver as seen below.
Windows Hardware Dev Center dashboard
In Windows 10, version 1809, we added new and improved functionality in the way of Hardware APIs for developers, IHVs, and OEMs to track and submit driver packages to the Windows hardware dashboard.
Use the shipping label REST APIs to create and manage shipping labels, the method by which you distribute your drivers.
Use the asynchronous custom report methods to access reporting data for driver errors and OEM hardware errors. You can define reporting templates based on your needs, set a schedule and you will have data delivered to you at regular intervals.
We're making the docs more community-driven. On many pages of the Windows driver documentation, you can suggest changes directly. Look for the Contribute button in the upper right corner of a page. It looks like this:
When you click Contribute, you'll arrive at the Markdown source file for that topic in a GitHub repository. You can click Edit and suggest changes right here.
For more details, see CONTRIBUTING.md in the repo. And thanks for taking the time to improve the docs!
Debugging Tools for Windows
This section describes the changes in the debugging tools for Windows.
Debugging in Windows 10, version 1903
New stop codes were added to allow better tracking on unique failure types in the Windows operating system. In addition a number of existing bug check topics were expanded and updated. For more information, see Bug Check Code Reference.
Updates to KDNET topics to improve ease of use, for example in new Setting Up KDNET Network Kernel Debugging Automatically
Updates to IP V6 KDNET support.
Debugging in Windows 10, version 1809
IPv6 - We are adding support for IPv6 to KDNET. To make room for the larger headers required for IPv6, we decreased the payload size of packets. As a result, we’re declaring a new version of the KDNET protocol, so that host PCs running the latest version of the debugger can be used to debug target PCs that only support IPv4. There is a version of WinDbg Preview available at https://aka.ms/windbgpreview that supports IPv6. Follow the Debugging Tools for Windows blog for updates on KDNET IPv6 support and see Setting Up KDNET Network Kernel Debugging Manually for more details.
Debugging in Windows 10, version 1803
WinDbg Preview Time Travel Debugging (TTD) hands on lab - This lab introduces Time Travel Debugging (TTD), using a small sample program with a code flaw. TTD is used to debug, identify and root cause the issue.
Debugging in Windows 10, version 1709
The following is a list of new content sets for the Debugger in Windows 10, version 1709:
- Debugging Using WinDbg Preview - A preview into the next generation debugger.
- Time Travel Debugging - Overview - Record and replay an execution of your process.
Debugging in Windows 10, version 1703
The following table shows changes for the Debugger in Windows 10, version 1703:
|New topics||Updated topics|
|40 undocumented stop codes in the Bug Check Code Reference||Updates to the Configuring tools.ini topic with additional options in the tools.ini file for the command line debuggers|
|!ioctldecode command||New command capabilities in the dx (Display Debugger Object Model Extension) command|
Debugging in Windows 10, version 1607
In Windows 10, version 1607, changes to the Debugger include a new topic about Debugging a UWP app using WinDbg, and updates to the 30 most-viewed developer bug check topics in Bug Check Code Reference.
Debugging in Windows 10, version 1507
The following is a list of new commands for the Windows Debugger in Windows 10, version 1507:
- dx (Display NatVis Expression) - A new debugger command which displays object information using the NatVis extension model.
- .settings - A new command that sets, modifies, displays, loads and saves settings in the Debugger.Settings namespace.
Device and Driver Installation
In Windows 10, version 1809, the following content was added:
The following was updated:
Driver verifier includes new driver validation rules for the following technologies:
- New Rules for Audio Drivers
- New Rules for AVStream Drivers
- Four new Rules for KMDF Drivers
- Three new Rules for NDIS Drivers
- New Nullcheck rules Added in version 1703
Windows Driver Frameworks (WDF)
WDF in Windows 10, version 1903
In Windows 10, version 1903, the Windows Driver Framework (WDF) includes Kernel-Mode Driver Framework (KMDF) version 1.29 and User-Mode Driver Framework (UMDF) version 2.29.
For info on what's included in these framework versions, see What's New for WDF Drivers in Windows 10. To see what was added in previous versions of WDF, see KMDF Version History and UMDF Version History.
Universal Windows drivers
This section describes new and updated features for Universal Windows drivers in Windows 10.
Universal Drivers in Windows 10, version 1809
Starting in Windows 10, version 1809, Windows supports flexible linking, which enables you to use a single binary to target OneCore and Desktop SKUs. To enable flexible linking, use the following new SDK API:
This existing topic has been enhanced to describe how to use flexible linking to comply with the U requirement of the DCHU driver design principles:
Universal Drivers in Windows 10, version 1803
See the latest recommendations for universal drivers in Getting started with universal drivers.
Universal Drivers in Windows 10, version 1709
The following is a list of new features to Universal Drivers in Windows 10, version 1709:
- Updating Device Firmware using Windows Update - Describes how to update a removable or in-chassis device's firmware by using the Windows Update (WU) service.
- Reg2inf - The Driver Package INF Registry Conversion Tool (reg2inf.exe) converts a registry key and its values or a COM .dll implementing a DLL RegisterServer routine, into a set of INF AddReg directives. These directives are included in the driver package INF file.
The following is a list of updates to Universal Drivers in Windows 10, version 1709:
- The Universal Drivers Scenario has a new COM component example
- INF AddComponent Directive
- Using an Extension INF file
- Using a Component INF file
Universal Drivers in Windows 10
Starting in Windows 10, you can write a single driver that works on OneCoreUAP-based editions of Windows, such as Windows 10 for desktop editions (Home, Pro, Enterprise, and Education), Windows 10 Mobile, and Windows 10 IoT Core (IoT Core). Such a driver is called a Universal Windows driver. A Universal Windows driver calls a subset of the interfaces that are available to a Windows driver. For information about how to build, install, deploy, and debug a Universal Windows driver for Windows 10, see Getting Started with Universal Windows drivers.
When you build a Universal Windows driver using Microsoft Visual Studio 2015, Visual Studio automatically checks if the APIs that your driver calls are valid for a Universal Windows driver. You can also use the ApiValidator.exe as a standalone tool to perform this task. The ApiValidator.exe tool is part of the Windows Driver Kit (WDK) for Windows 10. For info, see Validating Universal Windows drivers.
Universal Windows drivers also require a special kind of INF file called a universal INF. A universal INF can use a subset of the directives and sections available to a legacy INF file. To learn more, see Using a Universal INF File. To see which sections and directives apply, see INF File Sections and Directives.
When you're ready, use the InfVerif tool to test your driver's INF file. In addition to reporting INF syntax problems, the tool reports if the INF file will work with a Universal Windows driver.
You can also find information about which APIs you can call from a Universal Windows driver. This information is located in the Requirements block at the bottom of driver reference pages.
For example, you'll see a listing similar to this one that tells you if a given DDI is Universal.
For more info, see Target platform on driver reference pages.
Windows compatible hardware development boards
Windows is now supported on more affordable boards such as the Raspberry Pi 2. Become a part of our early adopter community and load Windows on that board. For more information, see Windows compatible hardware development boards.
Power Management Framework
The power management framework (PoFx) enables a driver to define one or more sets of individually adjustable performance states for individual components within a device. The driver can use performance states to throttle a component's workload to provide just enough performance for its current needs. For more information, see Component-Level Performance State Management.
Windows 10, version 1903 includes support for the Directed Power Management Framework (DFx). Related reference documentation includes the following:
- PO_FX_DIRECTED_POWER_DOWN_CALLBACK callback function
- PO_FX_DIRECTED_POWER_UP_CALLBACK callback function
- PoFxCompleteDirectedPowerDown function
For information about testing for DFx, please see the following pages:
WPP Software Tracing
WPP Software Tracing introduces a new feature: Inflight Trace Recorder. If the driver enables WPP tracing and WPP Recorder, trace logging is turned on automatically and you can easily view messages without starting or stopping trace sessions. For more fine tuned control over the log, WPP Recorder allows a KMDF driver to create and manage custom buffers.
- WPP Recorder for logging traces
- WppRecorderLogCreate (KMDF only)
What's new in Windows 10, version 1903 (latest)
This section describes new features and updates for driver development in Windows 10, version 1903 (Windows 10 April 2019 Update).
The following is a list of new and updated Audio features in Windows 10, version 1903:
New reference topics on the Audio OEM Adapter used for Voice Activation in the new eventdetectoroemadapter.h header.
New Far Field Audio information:
New jack description information in USB Audio 2.0 Drivers.
New Camera driver documentation and features added in Windows 10, version 1903 include:
- New IR Torch extended property control to set an IR camera's infrared torch power level and duty cycle.
- New KSCATEGORY_NETWORK_CAMERA device.
- New and updated USB Video Class (UVC) 1.5 extension documentation for the following control selectors:
Updates to Display driver development in Windows 10, version 1903 include the following:
Collect Diagnostic Info Allows the OS to collect a private data from drivers for graphics adapters which consist of both rendering and display functions. See DXGKDDI_COLLECTDIAGNOSTICINFO.
Background Processing Allows user mode drivers to express desired threading behavior, and the runtime to control/monitor it. User mode drivers would spin up background threads and assign the threads as low a priority as possible, and rely on the NT scheduler to ensure these threads don’t disrupt the critical-path threads, generally with success. See PFND3D12DDI_QUEUEPROCESSINGWORK_CB_0062.
In the NetAdapter WDF class extension (NetAdapterCx), Net ring buffers have been replaced by Net rings, which have a new interface for sending and receiving network data using net ring iterators. The following is a list of new topics:
- Introduction to net rings
- Sending network data with net rings with a new animation that illustrates how to send data
- Receiving network data with net rings with a new animation that illustrates how to receive data
- Canceling network data with net rings
New headers that support this feature include the following:
The following is a list of NetAdapterCx content updates:
Default adapter objects have been removed in favor of a single adapter object type. The following topics have been updated accordingly:
Hardware offload and packet extension DDIs have been reorganized into new headers:
Fundamental networking data structures, packets and fragments, have been updated and put into new headers:
Overhauled Transmit and receive queues topic to include callback samples and major operations for packet queues.
Mobile operator scenarios
New Mobile Plans content for mobile operators to sell plans to customers directly on Windows 10 devices, through the Mobile Plans app:
The following features were added to Mobile broadband in Windows 10, version 1903:
- New SIM card (UICC) file/application system access feature
- New Cellular Time Information (NITZ) feature.
- New modem logging with DSS feature.
- New 5G data class support feature.
New Print driver documentation and features added in Windows 10, version 1903 include:
New USB print IOCTLs:
New fpRegeneratePrintDeviceCapabilities PRINTPROVIDER structure member and updated documentation.
New features in sensor driver development in Windows 10, version 1903 include a MALT (Microsoft Ambient Light Tool) tool for testing and calibrating screen brightness.
There were also updates to the Ambient Color OEM whitepaper.
The following Storage features were added in Windows 10, version 1903:
- New Storport APIs for logging device failure and hardware protocol errors in ETW events and to query for platform D3 desired behavior
- New API to set the properties of a storage device or adapter
- For file systems, new DDIs were added to support retrieving extended attributes (EA) information upon create completion, allowing mini-filters to alter the ECP payload to change what higher filters see
Windows Hardware Error Architecture (WHEA)
Windows 10, version 1903 includes a simplified interface to WHEA. For more info, see the following pages:
New Wi-fi driver development documentation and features include:
- New Fine Timing Measurement (FTM) feature
- New WPA3-SAE Authentication feature
- New Multiband Operation (MBO) support to improve roaming performance in enterprise scenarios
- New beacon report offloading support
- For OID commands, NDIS status indications, and TLVs for these new features, see WDI doc change history
The following topics were updated for Windows 10, version 1903:
- WDI_AUTH_ALGORITHM - added support for WPA3-SAE authentication
- OID_WDI_TASK_P2P_SEND_REQUEST_ACTION_FRAME and OID_WDI_TASK_P2P_SEND_RESPONSE_ACTION_FRAME - added additional validation of outgoing Point to Point (P2P) action frames
What's new in Windows 10, version 1809
This section describes new features and updates for driver development in Windows 10, version 1809 (Windows 10 October 2018 Update).
HCI_VS_MSFT_Read_Supported_Features has been updated to include a new flag for secure simple pairing process. See, Microsoft-defined Bluetooth HCI commands and events.
Updates to Display driver development in Windows 10, version 1809 include the following:
Raytracing New Direct3D DDI's were created in parallel of Direct3D API's, in order to support hardware-accelerated raytracing. Example DDIs include: PFND3D12DDI_BUILD_RAYTRACING_ACCELERATION_STRUCTURE_0054, PFND3D12DDI_COPY_RAYTRACING_ACCELERATION_STRUCTURE_0054. For more info about raytracing, see Announcing Microsoft DirectX Raytracing.
Universal Driver Requirements WDDM 2.5 drivers will need to ensure their DirectX11 UMD, DirectX12 UMD, KMDs, and any other DLL loaded by these components, adhere to the Universal API.
SRV-Only Tiled Resource Tier 3 In Windows 10, version 1809, Tiled Resource Tier 3 capabilities can be supported less-orthogonally by GPUs. Direct3D12 now supports sparse volume textures without requiring unordered-access and render-target operations. SRV-Only Tiled Resource Tier 3 is a conceptual tier that fits between Tier 2 and Tier 3. Hardware support is optional, just like orthogonal Tiled Resource Tier 3 support currently is. But, supporting SRV-Only Tiled Resource Tier 3 is a super-set tier that requires support for Tiled Resource Tier 2.
Drivers that already advertise support for orthogonal Tiled Resource Tier 3 merely have to update their drivers to support the latest “options caps” DDI structure version. The runtime will advertise SRV-Only Tiled Resource Tier 3 support to applications for any hardware that already supports orthogonal Tiled Resource Tier 3.
Render Pass The Render Pass feature was added to:
- Allow new APIs to be run on existing drivers.
- Allow user mode drivers to choose optimal rendering path without heavy CPU penalty.
Meta-commands A Meta-command is Direct3D12 object that represents an IHV-accelerated algorithm. It’s an opaque reference to a command generator implemented by the driver. Meta-command updates include Descriptor Table Binding and Texture binding. See D3D12DDI_META_COMMAND_PARAMETER_TYPE and D3D12DDIARG_META_COMMAND_PARAMETER_DESC.
Enable Compute Algorithms to use Texture Resources (swizzled memory)
- Enable Graphics Pipeline Algorithms
HDR Brightness Compensation A new SDR brightness boost was introduced to raise the reference white of SDR content to the user-desired value, allowing SDR content to be reproduced to a typical 200-240 nits, which is equivalent to what users have expected for SDR displays. SDR brightness boost affects overall Brightness3 behavior in two ways:
This boost is applied pre-blend only on SDR content. HDR content is not affected. Meanwhile, for most laptop/brightness3 scenarios, users expect all content (SDR and HDR) to be adjusted.
When the Brightness3 stack in the OS determines the desired nits value, it is not aware of the already applied SDR boost.
The driver must then apply a compensation to the desired nits value coming from Brightness3 DDIs for HDR. Since Graphics drivers (and downstream TCON etc.) will be modifying the pixel values of the content to get desired nits value, there should also be a compensation applied to the HDR content metadata as provided by the applications via D3DDDI_HDR_METADATA_HDR10 or OS defaults via DxgkDdiSetTargetAdjustedColorimetry. Since Graphics driver (TCONs) are responsible for modifying the pixel data, it is the driver’s responsibility to compensate the HDR content metadata.
HDR Pixel Format Support This kernel mode device driver interface (DDI) change is part of WDDM 2.5 to expose new capabilities to be reported by driver/device, providing information regarding the HDR functionality supported by the driver/device.
Currently, OS determines if the driver/device supports HDR based on the HighColorSpace bit of the DXGK_MONITORLINKINFO_CAPABILITIES structure as read from DdiUpdateMonitorLinkInfo. The HighColorSpace bit gives a combination of driver/link/monitor capability to run in HDR mode.
The HDR capabilities reporting by the driver now includes a Driver/Device level capabilities, which will let OS know if the Driver/Device supports true HDR (i.e. FP16HDR), or only supports a limited form of HDR (i.e. ARGB10HDR), as defined below:
FP16HDR: Driver/device can take FP16 pixel format surfaces with scRGB/CCCS colorspace and apply PQ/2084 encoding and BT.2020 primaries during scanout pipeline to convert output signal to HDR10.
ARGB10HDR: Driver/device can take ARGB10 pixel format surfaces which are already PQ/2084 encoded and scan out HDR10 signal. Driver/device can’t handle FP16HDR as defined above or cannot handle the extended numeric range of scRGB FP16.
Graphics drivers can only report support for either FP16HDR or ARGB10HDR as they are not really superset/subset configurations and OS will fail the Start Adapter if both are reported as supported at the same time. See DXGK_MONITORLINKINFO_CAPABILITIES and _DXGK_DISPLAY_DRIVERCAPS_EXTENSION.
SDR White Level A kernel mode device driver interface change includes adding new parameters to existing DDIs to let the Graphics drivers know the “SDR white level” value that is being applied by the OS compositor for all the SDR content, for a display which is running in HDR mode. See _DXGK_COLORIMETRY.
Several new APIs have been added in the core kernel:
- RtlQueryRegistryValueWithFallback function: Querying the registry value entry by using a fallback handle in absence of a primary handle.
- PsGetSiloContainerId function and PsGetThreadServerSilo function
- New information classes added to: _FILE_INFORMATION_CLASS
- Extended version of NtCreateSection added NtCreateSectionEx function to indicate that this is actually an AWE section.
- New Ex macros grant direct access to actual push lock APIs exported by Ntoskernel.
- KzLowerIrql and KzRaiseIrql were moved to a supported extern forceinline for kernel components targeting Windows 8 and later versions, instead of relying on the forwarders to instantiate a special case of the inline functions.
- Flattening Portal Bridge (FPB) for PCI is now supported. For more information, see the Official Specification. The new APIs (PCI_FPB*) are declared in Ntddk.h.
New INF files for NetAdapterCx client drivers topic.
Transmit and receive queues have been consolidated into one object type called a packet queue, to simplify the API surface. A new section called Polling model has been added to the Transmit and receive queues topic.
Hardware offloads have been added to NetAdapterCx, which also automates the registration of associated packet extensions for client drivers.
Network interfaces are now decoupled from the driver's WDF device object. The EvtNetAdapterSetCapabilities callback function was removed to support this. NetAdapterCx client drivers can now have multiple network interfaces, including a default one.
Topics updated to support network interface/device object decoupling include the following:
DDIs supporting NetAdapterCx Receive side scaling (RSS) have been simplified.
Packet context token helper macros have been removed.
Receive side scaling version 2 (RSSv2) has been updated to version 1.01.
- New OID and DDIs to support multiple packet data protocol (MPDP) interfaces for MBB devices.
- New Device-based Reset and Recovery feature for more robust reset recovery for MBB devices and drivers.
Mobile Broadband WDF class extension (MBBCx)
MBBCx power management methods have been simplified.
Though preview content for MBBCx was available in Windows 10, version 1803, MBBCx now ships in the Windows 10, version 1809 version of the WDK.
The AutoConnectOrder setting is now supported in desktop COSA.
Support for auto Brightness feature:
The PKEY_SensorData_IsValid data field has been added to support auto brightness in sensors.
See Light sensor data fields for more info.
New feature for USB Type-C driver developers:
If your hardware is UCSI compliant and requires communication over a non-ACPI transport, you can utilize the new class extension — (UcmUcsiCx.sys). This implements the UCSI specification in a transport agnostic way. With minimal amount of code, your driver, which is a client to UcmUcsiCx, can communicate with the USB Type-C hardware over non-ACPI transport. This topic describes the services provided by the UCSI class extension and the expected behavior of the client driver.
New feature for USB Type-C driver developers that allows you to monitor the activities of USB Type-C connectors and/or get involved in policy decisions on USB Type-C connectors.
For example, control their device’s charging based on thermal conditions, so that the device won’t be overheated.
New versions of the class extensions available for emulated USB devices (UDE) -- 1.1 and USB host controller (Ucx) 1.5:
Emulated devices now support better reset recovery through function (FLDR) and platform (PLDR) resets. The client driver can now inform the system that the device needs a reset and the type of reset: function or platform.
The host controller can also opt for FLDR and PLDR resets through:
The WLAN device driver interface (WDI) spec has been updated to version 1.1.7.
- Added support for the latest 802.11ax PHY type for WDI drivers.
- Added support for unsolicited device service indications.
What's new in Windows 10, version 1803
This section describes new features and updates for driver development in Windows 10, version 1803 (Windows 10 April 2018 Update).
Windows 10, version 1803 includes updates to ACPI DDIs to support platform capabilities and physical device location.
The voice activation topic was updated to include additional information on APO requirements.
Windows 10, version 1803 introduces support for Swift Pair. Users no longer need to navigate the Settings App and find their peripheral to pair. Windows can now do this for them by popping a notification when a new peripheral is nearby and ready. There are two sets of requirements to ensure your peripheral works with Swift Pair. One set is for the peripheral’s behavior, and another for the structure and values in a Microsoft defined vendor advertisement section. For more information, see:
Windows 10, version 1803 supports Bluetooth version 5.0. For information about profile support, see Bluetooth Version and Profile Support in Windows 10.
Updates to Camera driver development include:
- DShow (DirectShow) Bridge implementation guidance for UVC devices - Implementation guidance for configuring DShow Bridge for cameras and devices that comply with the USB Video Class (UVC) specification. The platform uses Microsoft OS Descriptors from the USB bus standard to configure DShow Bridge. The Extended Properties OS Descriptors are an extension of USB standard descriptors and are used by USB devices to return Windows specific device properties that are not enabled through standard specifications.
- 360 camera video capture - Provides support for 360 camera preview, capture, and record with existing MediaCapture APIs. This enables the platform to expose spherical frame sources (for example, equirectangular frames ), enabling apps to detect and handle 360 video camera streams as well as to provide a 360 capture experience.
The following are updates to Display driver development in Windows 10, version 1803:
Indirect Display UMDF class extension - The Indirect Display driver can pass the SRM to the rendering GPU and have a mechanism to query the SRM version being used.
IOMMU hardware-based GPU isolation support - Increases security by restricting GPU access to system memory.
GPU paravirtualization support - Enables display drivers to provide rendering capabilities to Hyper-V virtualized environments.
Brightness - A new brightness interface to support multiple displays that can be set to calibrated nit-based brightness levels.
D3D11 bitstream encryption - Additional GUIDS and parameters to D3D11 to support exposing CENC, CENS, CBC1, and CBCS with 8 or 16 byte initialization vectors.
D3D11 and D3D12 video decode histogram - A luminance histogram allows the media team to leverage fixed function hardware for histogram to improve tone mapping quality for HDR/EDR scenarios. Fixed function hardware is useful when GPU is already saturated in these scenarios and to enable parallel processing. This feature is optional and should only be implemented if fixed function hardware is available. This feature should not be implemented with 3D or Compute.
D3D12 video decode now supports Decode Tier II, indicating driver supports Array of Textures that enable applications to amortize allocation cost and reduce peak memory usage during resolution change.
Tiled resource tier and LDA atomics - A new cross node sharing tier to add support for atomic shader instructions working across linked adapter (LDA) nodes. This improves ISVs ability to implement multiple GPU rendering techniques like split frame rendering (SFR) and clearly advances the capabilities over what is possible in D3D11.
GPU dithering support - Drivers can report the ability to perform dithering on the wire signal for a given timing mode. This allows the OS to explicitly request dithering in scenarios where a higher effective bit depth is needed than is physically available on the monitor link, for example for HDR10 over HDMI 2.0.
Post-processing color enhancement override - Adds the ability for the OS to request that the driver temporarily disable any post-processing that enhances or alters display colors. This is to support scenarios where specific applications want to enforce colorimetrically accurate color behavior on the display, and safely coexist with OEM or IHV-proprietary display color enhancements.
Direct3D12 and Video - New API and DDI to provide access to the following capabilities:
- Hardware accelerated video decoding
- Content Protection
- Video processing
DisplayID - A new DDI, designed to allow the VESA’s DisplayID descriptor to be queried from a display controlled by a graphics adapter and shall support DisplayID v1.3 and DisplayID v2.0. The DDI is an extension of existing DxgkDdiQueryAdapterInfo DDI and shall be supported by all drivers with DXGKDDI_INTERFACE_VERSION >= DXGKDDI_INTERFACE_VERSION_WDDM2_3, including kernel mode display only drivers and indirect display drivers.
GPU performance data - Extensions to DdiQueryAdapterInfo will expose information such as temperature, fan speed, clock speeds for engines and memory, memory bandwidth, power draw, and voltages
Miscellaneous - A new SupportContextlessPresent driver cap to help IHV onboard new driver.
Improvements to External/Removable GPU support in the OS. As a first step to add better support, Dxgkrnl needs to determine if a GPU is “detachable”, i.e. hot-pluggable. For RS4 we would like to leverage the driver’s knowledge about this instead of building our own infrastructure. For this purpose, we are adding a “Detachable” bit to DXGK_ DRIVERCAPS struct. Driver will set this bit during adapter initialization if the adapter is hot-pluggable.
Display Diagnostics - Kernel mode device driver interface (DDI) changes to allow the driver for a display controller to report diagnostic events to the OS. This provides a channel through which the driver can log events which would otherwise be invisible to the OS as the events are not a response to an OS request or something the OS needs to react to.
Shared graphics power components - Allows non-graphics drivers to participate in the power management of a graphics device. A non-graphics driver will use a driver interface to manage one or more of these shared power components in coordination with the graphics driver.
Shared texture improvements - Includes increasing the types of textures that can be shared across processes and D3D devices. This design enables the frame server OS component to support monochrome with minimal memory copying.
This section describes the new and updated features for Windows kernel driver development in Windows 10, version 1803.
A set of new APIs has been added to the kit to enable third parties to create their own KDNET extensibility modules or KdSerial transport layers. For sample code, see “Kernel Transport Samples” (ddk\samples\kdserial and ddk\samples\kdnet) in the Debuggers folder.
Support was added to provide drivers with a sanctioned location (that the operating system knows about) where they can store file state. With this approach, the system can associate files in that location with a device or driver.
There are distinct locations to store file states specific to the internals of a driver and specific to a device. For drivers that have file state, you can decide if the state written to disk is:
Driver state (IoGetDriverDirectory): global to the driver that might be controlling multiple devices), or
Device state (IoGetDeviceDirectory): specific to the driver-controlled single device and other devices might have different values for similar state.
Function drivers (FDO) can now negotiate additional power when their respective PCIe devices are in a D3Cold state. This includes:
- Auxiliary power requirement D3COLD_REQUEST_AUX_POWER.
- Core power rail D3COLD_REQUEST_CORE_POWER_RAIL.
- Requirement for a fixed delay time between the message is received at the PCI Express Downstream Port and the time the platform asserts PERST# to the slot during the corresponding endpoint’s or PCI Express Upstream Port’s transition to D3cold while the system is in an ACPI operational state. See D3COLD_REQUEST_PERST_DELAY.
NT services and kernel-mode and user-mode drivers can raise a custom trigger for a device by using the RtlRaiseCustomSystemEventTrigger function. A custom trigger, owned by the driver developer, notifies system event broker to start an associated background task with it, which is identified by a custom trigger identifier.
You can now register for active session change notification and get a callback when the notification is fired. As part of this notification, some data is also shared with the caller. This associated data is delivered via the PO_SPR_ACTIVE_SESSION_DATA structure.
This section outlines new features and improvements for Windows Networking driver development in Windows 10, version 1803.
NDIS and NetAdapterCx
Updates to NDIS include:
- Receive side scaling V2 has been updated with further details about steering parameters
- The Synchronous OID interface now supports NDIS light weight filter drivers
The following topics are new for the Network Adapter WDF class extension (NetAdapterCx):
- Introduction to NetAdapterCx 1.2
- Packet descriptors and extensions
- Network data buffer management
- NetAdapterCx receive side scaling (RSS)
Additionally, new topics are available for a preview-only feature, the Mobile Broadband class extension (MBBCx), which uses the NetAdapterCx model for mobile broadband connectivity.
In mobile broadband, a new topic detailing MB low level UICC access is available.
New Hotspot and AppID settings are now a part of desktop COSA. Mobile operators are strongly encouraged to transition from broadband app experience apps with Sysdev metadata packages to MO UWP Apps and the COSA database.
New ACPI _DSD methods have been added to support these Modern Standby and PCI hot plug scenarios:
- Directed Deepest Runtime Idle Power State (DDRIPS) support on PCIe Root Ports
- Identifying PCIe Root Ports supporting hot plug in D3
- Identifying externally exposed PCIe Root Ports
For information, see ACPI Interface: Device Specific Data (_DSD) for PCIe Root Ports.
The SENSOR_CONNECTION_TYPES enumeration was added to clarify connection type properties.
New APIs were added to simulate detach for shared connectors. If a USB device is attached to a host or has shared connector while the stack is being removed while the device is attached to a host or has shared connectors, you can simulate a detach event. At this point all attach/detach notification mechanisms are disabled. For more information, see UfxDeviceNotifyFinalExit function.
Updates to Wi-fi driver development include a new TLV for the Nic Auto Power Saver (NAPS) advanced power management feature and updates to the platform level device recovery service (PLDR).
What's new in Windows 10, version 1709
This section describes new features and updates for driver development in Windows 10, version 1709.
The following is a list of updates to Windows Audio driver development in Windows 10, version 1709:
- New Configure and query audio device modules
- Extensive updates to voice activation
- More details on chained and keyword only activation
- A new glossary of terms
- Additional information on training and recognition, such as pin and audio format information
- An updated keyword system overview
- Updated information on wake on voice
The following is a list of new Advanced Configuration and Power Interface (ACPI) DDIs to support input/output buffers.
There are new signing requirements for Windows Biometric Drivers. For more information, see Signing WBDI Drivers.
The following is a list of new features for Windows Display driver development in Windows 10, version 1709.
- Display ColorSpace Transform DDIs provide additional control over color space transforms applied in the post-composition display pipeline.
- The D3D12 Copy Queue Timestamp Queries feature will allow applications to issue timestamp queries on COPY command lists/queues. These timestamps are specified to function identically to timestamps on other engines.
- Enhanced Video integration into Direct3D12 Runtime through:
- Hardware accelerated video decoding
- Content protection
- Video processing
In Windows 10, version 1709, there is support for hardware-agnostic support of notification components such as LEDs and vibration mechanisms. For more information, see:
In Windows 10, version 1709, several new routines to the Windows Kernel for drivers have been added.
ExGetFirmwareType and ExIsSoftBoot – Executive library support routines.
PsSetLoadImageNotifyRoutineEx – An extended image notify routine for all executable images, including images that have a different architecture from the native architecture of the operating system.
PoFxSetTargetDripsDevicePowerState – A PoFx routine to notify the power manager of the device's target device power state for DRIPS.
The following is a list of new options for the ZwSetInformationThread routine, that are related to process policies:
The following is a list of new RTL functions for using correlation vector to reference events and the generated logs for diagnostic purposes.
The following is a list of new features for Windows Mobile Broadband and Mobile Operator Scenarios for driver development in Windows 10, version 1709:
- UICC reset and modem reset
- Protocol Configuration Operations (PCO)
- Base stations information query
- eSIM and MBIM ReadyState guidance
This section outlines new features and improvements for Windows Networking driver development in Windows 10, version 1709.
The following is a list of new and updated features for NDIS:
- Introduction to NetAdapterCx 1.1, which includes new NewAdapterCx features:
- More packet context options
- Finer link state control
- Improved receive buffer management and performance
- General performance improvements
- New Synchronous OID request interface in NDIS 6.80
- New Receive Side Scaling Version 2 (RSSv2) in NDIS 6.80
- Introduction to NDIS 6.80
- Porting NDIS 6.x drivers to NDIS 6.80
There are new programming interfaces for writing a Physical Function driver for devices that conform to the PCI Express Single-Root I/O Virtualization (SR-IOV) specification. The interfaces are declared in Pcivirt.h. For more information, see PCI virtualization.
Pulse Width Modulation (PWM) Controllers
In Windows 10, version 1709, to provide access to a Pulse width modulation (PWM) controller that is part of the SoC and memory-mapped to the SoC address space, you need to write a kernel-mode driver. For more information, see PWM driver for an on-SoC PWM module.
To parse and validate pin paths and extract the pin number, kernel mode drivers should use PwmParsePinPath.
An app can send requests to the controller driver by sending PWM IOCTLs requests.
Storage and File Systems
In File Systems and Storage, the ufs.h header was added in Windows 10, version 1709 to provide additional support to Universal Flash Storage.
Posix updates include new functions delete and rename.
The following is a list of headers that were updated in Windows 10, version 1709:
This section describes the new features for USB in Windows 10, version 1709.
Media Agnostic USB (MA-USB) protocol
The USB driver stack can send USB packets over non-USB physical mediums such as Wi-Fi by using the Media Agnostic USB (MA-USB) protocol. To implement this feature, new programming interfaces have been released. The new DDIs allow the driver to determine the delays associated with the _URB_GET_ISOCH_PIPE_TRANSFER_PATH_DELAYS. That information can be retrieved by building a new URB request. For information about this new feature, see the following topics:
- USB client drivers for Media-Agnostic (MA-USB)
- USB Request Blocks (URBs)
To support MA-USB, the host controller driver must provide the transport characteristics by implementing specific callback functions. The following table shows the callback functions and structures that support MA-USB.
Synchronized system QPC with USB frame and microframes
There are new programming interfaces that retrieve the system query performance counter (QPC) value synchronized with the frame and microframe.
This information is retrieved only when the caller enables the feature in the host controller. To enable the feature, a host controller driver must implement the following callback functions.
An application can use these APIs to enable/disable the feature and retrieve the information:
Other drivers can send these IOCTL requests to enable/disable the feature and retrieve the information:
Here are the supporting structures for synchronized system OPC with USB frame and microframes:
The IOCTL_UCMTCPCI_PORT_CONTROLLER_DISPLAYPORT_DISPLAY_OUT_STATUS_CHANGED request is a new request in USB Type-C Port Controller Interface framework extension. This request notifies the client driver that the display out status of the DisplayPort connection has changed.
Here are the structures that support the IOCTL_UCMTCPCI_PORT_CONTROLLER_DISPLAYPORT_DISPLAY_OUT_STATUS_CHANGED request:
What's new in Windows 10, version 1703
This section describes new and improved features for driver development in Windows 10, version 1703.
The following is a list of new topics for Audio driver development in Windows 10, version 1703:
- Implementing Audio Module Communication - Describes the support for communication from Universal Windows Platform (UWP) apps to kernel mode audio device drivers.
- New DDIs and properties reference topics to support APO Module Communications discovery:
- KSPROPSETID_AudioModule - A new KS Property Set that defines three properties specific to audio modules.
- KSPROPERTY_AUDIOMODULE_COMMAND property - Allows Audio Module clients to send custom commands to query and set parameters on Audio Modules.
- IPortClsNotifications - New Port Class Notifications that provide notification helpers to miniports, to support audio module communication.
The following is a list of updates to Bluetooth in Windows 10 version 1703:
- Hands-Free Profile (HFP) 1.6 specification with Wideband speech on Windows 10 for desktop editions.
- Support for Call Control APIs on Windows 10 for desktop editions.
- Support for GATT Server, Bluetooth LE Peripheral and non-paired support for Bluetooth LE. See our developer post for more details.
The following is a list of updates to Camera driver development in Windows 10, version 1703:
- USB Video Class (UVC) driver implementation guide
- Microsoft extensions to USB Video Class 1.5 specification
- Device transform manager (DTM) events
- IMFDeviceTransform interface
- KSCategory_Xxx Device Interface Classes
Windows Kernel-Mode Process and Thread Manager - Starting in Windows 10 version 1703, the Windows Subsystem for Linux (WSL) enables a user to run native Linux ELF64 binaries on Windows, alongside other Windows applications. For more information about WSL architecture and the user-mode and kernel-mode components that are required to run the binaries, see the posts on the Windows Subsystem for Linux blog.
Updates to Mobile Broadband (MB) include improved LTE attach features, support for Multi-SIM Operations, support for provisioning contexts into the modem, support for the Specific Absorption Rate platform, and support for network blacklisting.
- Planning your COSA/APN database submission
- Submitting the COSA/APN database update
- Testing your COSA/APN database submission
Updates to Networking driver development in Windows 10, version 1703 includes a new type of socket called Stream Sockets, which support Linux networking applications on Windows. See Winsock Kernel for more info. New functions and structures include WskConnectEx, WskListen, WSK_CLIENT_STREAM_DISPATCH, and WSK_PROVIDER_STREAM_DISPATCH
The following is a list of new topics for POS in Windows 10, version 1703:
- Bluetooth barcode scanner UUIDs
- BarcodeSymbologyDecodeLenthType enumeration
- BarcodeSymbologyAttributesData structure
There is a new Gs1DWCode symbology to the BarcodeSymbology enumeration.
Windows 10 version 1703 provides a new class extension (UcmTcpciCx.sys) that supports the Universal Serial Bus Type-C Port Controller Interface Specification. A USB Type-C connector driver does not need to maintain any internal PD/Type-C state. The complexity of managing the USB Type-C connector and USB Power Delivery (PD) state machines is handled by the system. You only need to write a client driver that communicates hardware events to the system through the class extension. For more information, see USB Type-C Controller Interface driver class extensions reference.
What's new in Windows 10, version 1607
This section describes new features and improvements for driver development in Windows 10, version 1607.
The following is a list of new topics for Audio driver development in Windows 10, version 1607.
- Windows Audio Architecture
- Structures and properties to better support the Cortana experience:
- PKEY_AudioEndpoint_Default_VolumeInDb – An INF key that provides the user a better experience when appropriate gain or attenuation is applied to the audio signal.
Camera driver development in Windows 10, version 1607 includes new and updated topics to support Windows Hello and face authentication:
- Windows Hello camera driver bring up guide
- Extended camera controls
Location driver development in Windows 10, version 1607 includes the following new GNSS Breadcrumb DDIs:
In Windows 10, version 1607, there are new and updated topics for WLAN Device Driver Interface (WDI) version 1.0.21. For details, see WDI doc change history.
What's new in Windows 10, version 1507
This section describes new and updated features for driver development in Windows 10.
In Windows 10, new Microsoft-defined Bluetooth HCI extensions have been added.
Buses and Ports
Driver programming interfaces and in-box drivers for Simple Peripheral Bus (SPB) such as I2C and SPI, and GPIO are part of OneCoreUAP-based editions of Windows. Those drivers will run on both Windows 10 for desktop editions and Windows 10 Mobile, as well as other Windows 10 versions.
The camera driver DDIs have converged into a Universal Windows driver model, including new camera DDIs. Additional features include:
- Digital video stabilization
- Variable frame rate
- Face detection
- Video high dynamic range (HDR)
- Optical stabilization
- Scene analysis: photo HDR, flash no flash, ultra low light
- Capture stats: metadata framework/attributes, histograms
- Smooth zoom
- Hardware optimization hints
- Camera profiles
Cellular architecture and implementation for Windows 10 has been updated.
The display driver model from Windows 8.1 and Windows Phone have converged into a unified model for Windows 10.
A new memory model is implemented that gives each GPU a per-process virtual address space. Direct addressing of video memory is still supported by WDDMv2 for graphics hardware that requires it, but that is considered a legacy case. IHVs are expected to develop new hardware that supports virtual addressing. Significant changes have been made to the DDI to enable this new memory model.
Human Interface Device (HID)
The new Virtual HID Framework (VHF) eliminates the need for writing a kernel-mode transport minidriver. The framework comprises a Microsoft-provided static library (Vhfkm.lib) that exposes programming elements used by your driver. It also includes a Microsoft-provided in-box driver (Vhf.sys) that enumerates one or more child devices and proceeds to build a virtual Human Interface Device (HID) tree.
The Global Navigation Satellite System (GNSS) driver DDIs have converged to a GNSS Universal Windows driver model (UMDF 2.0).
Near Field Communication (NFC)
The NFC DDIs have a new converged driver model to support mobile and desktop solutions.
NFC Class Extension: A new NFC class extension driver is available. The NFC class extension driver implements all of the Windows-defined DDIs to interact with the NFC controller, secure elements, and remote RF endpoints.
The new PacketDirect Provider Interface (PDPI) is available as an extension to the existing NDIS miniport driver model. The PDPI provides an I/O model that allows applications to manage their own buffers, poll processors, and directly manage sending and receiving packets over a miniport adapter. The combination of these capabilities allow the application to completely control its own contexts leading to a much higher packet-per-second (pps) ratio.
The print driver is updated with v4 Print driver improvements and changes to support wireless printing from mobile devices, as well as the following:
- V4 Driver Manifest – Provides information on changes to the v4 print driver manifest to support the PWG Raster rendering filter, including updated DriverConfig and DriverRender directives, and an updated example manifest.
- WS-Discovery Mobile Printing Support – Describes the WS-Discovery requirements to enable mobile printing from Windows 10 Mobile devices to Windows 10 Mobile compatible printers.
- IXpsRasterizationFactory2 interface – Supports printer content conversion from XPS to PWG Raster using the XPS Rasterization Service. PWG Raster supports non-square DPIs.
- Print Pipeline Property Bag – New PrintDeviceCapabilities property to enable XPS rendering filters to retrieve the new PrintDeviceCapabilities XML files from the Print filter pipeline property bag.
- GetWithArgument Request and Response Schemas – Provides support for mobile printing with a formal definition and example for the GetWithArgument request and response bidirectional communications schemas.
- IBidiSpl::SendRecv method – Adds support for mobile printing with the GetWithArgument bidirectional schema value.
In Windows 10, there is a new class extension module, Wudfsmcclassext.dll, which handles complex driver operations. Smart card hardware-specific tasks are handled by your client driver. There are new programming interfaces that your client driver can use to send information about the card to the class extension so that it can process requests. Those driver programming interfaces are part of OneCoreUAP-based editions of Windows.
In Windows 10, new protocol-specific interfaces have been added to allow apps to talk with storage devices using their native device protocol. These updates include:
- Storage protocol pass through – The updated storage pass through IOCTL interface supports newer protocols including non-volatile memory express (NVMe).
- Expanded storage query interfaces – The expanded storage query interface allows applications to query protocol-dependent information.
System-Supplied Driver Interfaces
The GUID_DEVICE_RESET_INTERFACE_STANDARD interface defines a standard way for function drivers to attempt to reset and recover a malfunctioning device.
Here are the new features for USB in Windows 10. For more information, see Windows 10: What's new for USB.
- Native support for USB Type-C as defined in the USB 3.1 specification. If you are building a system with USB Type-C connectors, you can use the in-box USB Type-C Connector System Software Interface (UCSI) driver or write a USB Type-C connector driver..
- The dual role feature allows a mobile device, such as a phone, a phablet or a tablet, to designate itself as being a device or a host. See USB Dual Role Driver Stack Architecture for more information.
- Support for writing a driver for USB emulated devices by using the Microsoft-provided USB device emulation class extension (UdeCx).
- Support for writing a driver for a host controller that is not xHCI specification-compliant or a virtual host controller. To write such a driver, see Developing Windows drivers for USB host controllers.
- Support writing function controller driver by using USB function class extension (UFX). See Developing Windows drivers for USB function controllers.
WDI (WLAN Device Driver Interface) is a new WLAN Universal Windows driver model that converges the WLAN drivers on Windows 10 for desktop editions and Windows 10 Mobile.
The following table describes Windows driver development features that have been removed in Windows 10.
|Driver technology||Feature||Deprecated in|
|GNSS/Location||Geolocation driver sample for Windows 8.1 and related documentation||Windows 10, version 1709|
|Mobile Operator Scenarios (Networking)||AllowStandardUserPinUnlock||Windows 10, version 1709|
|Scan/Image||WSD (Web Services for Devices) Challenger functionality and related documentation||Windows 10, version 1709|
|Mobile Operators||Mobile broadband app experience apps with Sysdev metadata packages are deprecated in favor of MO UWP APPS and COSA.||Windows 10, version 1803|