The “Windows cannot start this hardware device” error (Code 19, 31, or 39) appears in Device Manager when a driver is missing, corrupted, or blocked by the registry. The fix is usually to update, reinstall, or roll back the driver, or to clear the corrupted registry entries that store the device’s configuration.
What Causes This Error
Windows assigns each hardware device a set of registry keys that describe its configuration, including which driver to load and what resources (IRQ, I/O ports, memory ranges) it can use. When those keys become corrupted, or when the driver file itself is missing or incompatible, Windows refuses to start the device and reports the error.
The most common triggers are:
- A driver update that was interrupted or installed incorrectly
- Antivirus or disk cleanup software deleting driver files
- Removing a device while it was still in use
- A Windows update that changed how the driver loads
- Registry corruption from a crash or forced shutdown
Error Code 19 specifically points to a corrupted registry entry. Code 31 means Windows could not load the driver at all, and Code 39 often indicates the driver file is missing or damaged.
Step-by-Step Fixes
Work through these in order. Most users resolve the issue at step 2 or 3.
- Restart the computer. A simple reboot clears temporary driver states and often resolves transient errors.
- Update the driver. Open Device Manager (right-click the Start button), find the device with the yellow exclamation mark, right-click it, and choose Update driver > Search automatically for drivers. If Windows finds nothing, go to the manufacturer’s website and download the latest driver for your exact model and Windows version.
- Uninstall and reinstall the driver. In Device Manager, right-click the device, choose Uninstall device, and check the box that says Delete the driver software for this device if it appears. Then restart the PC. Windows will reinstall a generic driver on boot.
- Roll back the driver. If the error started after a recent driver update, go to the device’s Properties > Driver tab and click Roll Back Driver. This reverts to the previous working version.
- Run the Hardware and Devices troubleshooter. In Windows Settings, search for “troubleshoot” and run the Hardware and Devices tool. It scans for common problems and applies fixes automatically.
- Clear the corrupted registry entries. This is the specific fix for Error Code 19. Open the Registry Editor (type regedit in the Start menu), navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class, and find the subkey that matches your device category (for example,{4d36e972-e325-11ce-bfc1-08002be10318}for network adapters). Look for a value namedUpperFiltersorLowerFilters. If either exists, right-click it and delete it. Close the editor and restart. Windows will rebuild the correct entries.
If none of these work, the hardware itself may be failing. Test the device on another computer if possible.
How to Identify the Problem Device
Device Manager groups hardware by category. Expand each category and look for a device with a yellow triangle and black exclamation mark. Right-click it and select Properties. The General tab shows the exact error code and a message like “Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged.”
The Details tab lists the hardware ID, which you can search online to confirm what the device is and find the correct driver. For example, a USB controller might show PCI\VEN_8086&DEV_9C31, where VEN_8086 is Intel and DEV_9C31 is the specific chip.
Why Registry Corruption Happens
Windows stores device configuration in the registry because it is faster to read than a file and centralizes all system settings. The Class key groups devices by type, and each device has a subkey with parameters like DriverDesc, MatchingDeviceId, and the filter drivers that process data before the main driver.
Filter drivers are the usual culprit for Code 19. Programs like older antivirus tools, virtual CD/DVD emulators, and some printer software add UpperFilters or LowerFilters values. If the software is uninstalled improperly or crashes, those values remain but point to drivers that no longer exist. Windows then fails to start the device because it cannot load the missing filter.
Common Mistakes to Avoid
- Deleting the wrong registry key. Only delete
UpperFiltersandLowerFiltersvalues, never the entire Class subkey or theConfigFlagsvalue. Deleting the whole subkey removes all drivers for that device type. - Downloading drivers from unofficial sites. Use the manufacturer’s website or Windows Update. Third-party driver download sites often bundle malware or provide outdated files.
- Skipping the restart. Many driver changes only take effect after a full reboot. A shutdown and power-on is more thorough than restart in some cases.
- Ignoring Windows Update. Sometimes the fix is a cumulative update that patches the driver framework. Check Settings > Windows Update and install pending updates.
When to Use System Restore
If you know the error started after a specific change—a driver install, a Windows update, or new software—System Restore can revert the registry and driver files to an earlier state. Search for “Create a restore point” in the Start menu, click System Restore, and choose a restore point from before the problem began. This does not affect personal files, but it will undo any programs or drivers installed after that date.
System Restore is a good middle step before more drastic measures like a full reset. It is especially useful when the registry editing step seems risky or when multiple devices have the same error.
Frequently Asked Questions
Will I lose data if I delete registry entries?
No. Deleting UpperFilters or LowerFilters only removes filter driver references. Your documents, photos, and installed programs are untouched. Windows rebuilds the missing values on the next boot.
What if the error is on my graphics card?
Graphics cards use the same registry structure. Try rolling back the driver first, then uninstall and reinstall using the manufacturer’s clean install option (DDU is a common tool, but you can also use the standard uninstaller). If the card shows Code 43 instead, that usually indicates a hardware fault rather than a driver issue.
Can I ignore this error?
You can ignore it if the device is something you do not use, like a legacy modem or an unused card reader. The rest of the system will work normally. However, if the device is your network adapter, Wi-Fi card, or USB controller, ignoring it means losing that functionality.
Why does the error return after I fix it?
A recurring error usually means the driver is incompatible with your Windows version, or another program is re-adding the filter values. Check for software that installs kernel-level drivers (antivirus, virtual drives, screen recorders) and update or remove it. Also verify you have the latest Windows feature update installed.
Is it safe to use Device Manager to uninstall a driver?
Yes. Uninstalling a driver does not delete the hardware or your data. Windows will either reinstall a generic driver automatically or prompt you to install one. It is one of the safest troubleshooting steps available.
What if the device does not appear in Device Manager at all?
Open Device Manager, click View > Show hidden devices, then look under Non-Plug and Play Drivers. If it is still missing, the hardware may be physically disconnected, disabled in BIOS/UEFI, or completely dead. Check the BIOS settings for onboard devices like audio or network controllers.