What Is a DCH Driver?
DCH stands for Declarative, Componentized, Hardware Support App. Microsoft introduced this packaging standard alongside Windows 10 version 1803 to modernise how driver software is distributed, installed, and maintained across the Windows ecosystem. The goal was to separate the hardware-specific code from the user-interface components that manufacturers had historically bundled together.
In the legacy, or "Standard," model, a graphics driver installer such as a typical NVIDIA or AMD package would contain everything in one archive: the kernel-mode driver itself, the DirectX components, HDMI audio support, and the entire control panel application. That control panel might be 200–400 MB of code that ships with every install regardless of whether the user ever opens it. This monolithic approach made driver packages large, slowed down Windows Update delivery, and created significant surface area for version conflicts.
How DCH Changes the Structure
Under the DCH model, a driver package is broken into distinct components. The base driver — the code that actually communicates with the hardware at a kernel level — is delivered as a small, declarative INF-based package. Declarative means the driver cannot run arbitrary setup code during installation; it must describe its requirements using standard Windows INF directives rather than executing a custom installer. This restriction is deliberate: it makes the driver more predictable, easier to audit, and harder to abuse as an installation vector for unwanted software.
The user-interface layer — NVIDIA Control Panel, AMD Software: Adrenalin Edition, Intel Graphics Command Center, Realtek HD Audio Manager — is separated out entirely and delivered as a Hardware Support App (HSA) through the Microsoft Store. Windows automatically installs the matching HSA when the base driver is detected, provided the system has Store access. On enterprise or air-gapped machines where Store access is blocked, the HSA can also be side-loaded using DISM.
The componentised architecture also means manufacturers can update the control panel application independently of the kernel driver. A bug fix in NVIDIA Control Panel's overlay UI does not require shipping a new signed kernel driver, which reduces the certification overhead and lets cosmetic fixes reach users faster.
Why You Cannot Mix DCH and Standard Drivers
The two driver types share no installation path. A DCH base driver places and registers components differently in the Windows Driver Store than a Standard package. An attempted cross-family replacement can cause the installer to abort, skip kernel components, or leave INF registration and binary versions out of alignment.
This is the root cause of a persistent class of support questions: a user downloads the latest NVIDIA Studio Driver from the NVIDIA website, runs the installer, and sees "This graphics driver could not find compatible graphics hardware." The downloaded package is a Standard driver, but the system already has a DCH driver registered in the Driver Store. The two formats are mutually exclusive on a live installation.
Visible Differences Between Package Types
Device Manager exposes package files and provider metadata, while Installed Apps shows separately delivered interfaces. A DCH graphics configuration commonly combines an INF-generated directory under `C:\Windows\System32\DriverStore\FileRepository` with a Microsoft Store Hardware Support App. A legacy package commonly places its control panel under the vendor's Program Files directory.
For Intel graphics, the presence of Intel Graphics Command Center as a Store app is a clear DCH indicator. For AMD, the Adrenalin Software installer since late 2022 ships only DCH packages for supported hardware.
Transitions Between Driver Types
Changing package families is not an ordinary in-place version update. Existing INF registrations, extension packages, applications, and services can continue to describe the previous model. Display Driver Uninstaller (DDU) is a third-party removal utility that targets this retained graphics state, but its broad deletion behavior sits outside normal Windows servicing.
Windows Update can stage an applicable package again after device enumeration. This behavior reflects Plug and Play ranking and update policy rather than a preference stored by DDU.
Compatibility Caveats
Not all hardware generations have both DCH and Standard packages available. Most NVIDIA consumer GPUs from the Pascal generation (GTX 10-series) onward have DCH packages; older Kepler cards (GTX 600/700 series) are on legacy Standard drivers that will not receive DCH updates. AMD DCH packages are available for RDNA and later architectures. Intel DCH drivers cover 8th-generation Core (Coffee Lake) integrated graphics and newer discrete Arc GPUs.
On Windows 10 LTSC (Long-Term Servicing Channel) editions, the Microsoft Store is absent by default. DCH drivers will install correctly because the base driver does not depend on the Store, but the Hardware Support App will not appear automatically. This is expected behaviour, not an installation failure.