Because a base driver package can be used across all systems that share a hardware part, Microsoft can test the base driver package broadly via Windows Insider flighting, rather than limiting distribution to specific machines. Then, a system builder, or original equipment manufacturer (OEM), provides any optional component packages.Īfter an IHV has certified the base driver package, it can be deployed on all OEM systems. Typically, a device manufacturer, or independent hardware vendor (IHV), writes the base driver. The optional component packages can contain customizations and additional settings. The base driver contains all the core functionality and shared code.
#PRINCIPLE APP FOR WINDOWS DOWNLOAD INSTALL#
They also install and run on other editions of Windows 10 and 11 that share a common set of interfaces.ĭCH-compliant driver binaries can use KMDF, UMDF 2, or the Windows Driver Model (WDM).ĭCH-compliant drivers consist of the following parts: Overviewĭriver packages that are DCH-compliant contain an INF file and binaries that install and run on Universal Windows Platform (UWP)-based editions of Windows. Please refer to the DCH-Compliant Driver Package Example page to see how a driver sample can apply DCH design principles. The acronym "DCH" refers to the principles listed above. For details, see Hardware Support App (HSA): Steps for driver developers and Hardware Support App (HSA): Steps for app developers.
#PRINCIPLE APP FOR WINDOWS DOWNLOAD UPDATE#
You must distribute and update an HSA through the Microsoft Store. The application can be a Universal Windows Platform (UWP) or Desktop Bridge app. An HSA is an optional device-specific app that's paired with a driver. Hardware Support App (H): Any user interface (UI) component associated with a Windows Driver must be packaged as a Hardware Support App (HSA) or preinstalled on the OEM device. As a result, the base driver, which provides only core device functionality, can be targeted, flighted, and serviced independently from the customizations.
Don't include co-installers or RegisterDll functions.Ĭomponentized (C): Edition-specific, OEM-specific, and optional customizations to the driver are separate from the base driver package. There are three design principles to consider for a Windows Driver to be DCH-compliant:ĭeclarative (D): Install the driver by using only declarative INF directives. This page describes design principles and best practices for Windows Drivers.