Code 19 is a Windows Device Manager error meaning the driver service registered for a device is missing, misnamed, or pointing at configuration data Windows can no longer read — and the fastest confirmed fix is to uninstall the device in Device Manager, choose "Delete the driver software for this device," and let Windows rebuild the registry entries on restart. If that fails, the fault sits in the driver service record itself, which you repair with a clean reinstall of the device driver or, for phantom devices, by removing the hidden entry under a changed environment variable.

What Error Code 19 Actually Tells You

Code 19 is Microsoft's code for a corrupt or half-installed registry record, and it appears in the device's Properties dialog under the General tab in the "Device status" box. The exact text reads "Windows cannot start this hardware device because its configuration information in the registry is incomplete or damaged. (Code 19)." Microsoft's own Device Manager error code documentation lists Code 19 as a registry corruption class, meaning the hardware is usually detected fine but the instruction set Windows needs to start it is unusable.

What makes Code 19 different from Code 10 or Code 43 is scope. Code 10 ("This device cannot start") often comes from an IRQ or resource conflict, while Code 43 is typically the device reporting its own failure. Code 19 is almost always a software-side break: the service key under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services that the driver declared is absent, or its ImagePath value points to a file that no longer exists. Windows 10 and Windows 11 both report the identical wording, so troubleshooting steps transfer across versions without modification.

The error hits several device classes far more often than others. Optical drives (DVD/CD-ROM) top the list, followed by USB controllers, Bluetooth radios, printers added over USB, and virtual audio devices installed by conferencing software. A 2019-era Windows update cycle produced a well-documented wave of Code 19 on optical drives, and Microsoft's optical drive troubleshooting guidance still leads with the registry-filter fix that wave popularized. Understanding that pattern saves time: if your failing device is a CD/DVD drive, start with the UpperFilters and LowerFilters values.

One practical boundary before you touch anything. Code 19 does not mean the hardware failed physically, and it is not a virus signature. Reinstalling Windows is not the first, second, or third fix. Almost every confirmed case resolves at the driver-service level, and the remaining cases are phantom registry entries left behind by uninstalled software. The rest of this article handles both, with the exact dialog names and registry paths Windows uses.

Before You Start: System Restore, Backups, and the Rollback Option

Create a restore point before editing anything, because two of the fixes below modify the registry directly. Open Start, type "Create a restore point," select the System Protection tab, click Create, and name it something you'll recognize, like "before code 19 fix." System Protection must already be enabled on the C: drive or the Create button stays greyed out — enable it first in the same dialog if it is. Windows generally caps restore points by allocating a percentage of disk space specified in that dialog, so a fresh point can push out an old one.

If the device worked recently, the driver rollback is faster than anything else. Open Device Manager, right-click the affected device, choose Properties, and check the Driver tab for an active "Roll Back Driver" button. That button is greyed out when Windows has no previous driver package stored, which is common after a disk cleanup that removed old driver packages. Rollback undoes a single driver update, so it only helps when the Code 19 appeared within one update cycle.

Note the exact device name and its category before you remove anything. Right-click the device and choose Properties, then read the "Location" line on the General tab for devices that show one, or the parent device on the Details tab under "Parent." That name is your search string later if the device reappears with the same error. For USB and Bluetooth devices, unplugging the hardware first prevents Windows from instantly re-detecting and reinstalling it mid-fix.

Two Windows features can regenerate the record automatically, and both are worth knowing now. Windows Update's optional driver updates sometimes republish a corrected service entry for an affected device, and the "Add legacy hardware" wizard under Action can re-trigger device enumeration. Neither is a guaranteed fix, but checking for optional updates is a five-minute step that occasionally closes the case without registry work at all.

Step 1: Uninstall the Device and Delete Its Driver Software

This action sequence is the first fix for every Code 19 case, and the checkbox matters more than the uninstall itself. A plain uninstall removes the device node; checking "Delete the driver software for this device" also removes the driver package and its service registration, which is the part that's actually broken.

1: Press Windows + X and choose Device Manager, or type "Device Manager" into Start. 2: Expand the category holding the failing device — for a Code 19 optical drive that's "DVD/CD-ROM drives." 3: Right-click the device and choose Uninstall device. 4: In the confirmation dialog, tick "Delete the driver software for this device" if the checkbox appears. It appears for most third-party drivers and often not for in-box Microsoft ones. 5: Click Uninstall and wait for the device to disappear from the list. 6: In the menu bar, click Action, then "Scan for hardware changes." 7: Restart Windows even if the device appears to work after step 6, then check its status in Device Manager.

If the device returns with Code 19 after the restart, the service record was not fully removed or Windows reinstalled the same corrupted package. That result points to the deeper fixes below, and it also tells you the problem is reproducible rather than a one-off glitch. If the device vanishes entirely and doesn't reappear on scan, the hardware detection itself has failed — check the cable, port, or slot before treating it as a software problem.

A failure case worth flagging: on some laptops the optical drive sits behind a removable-bay controller, and deleting the controller's driver along with the drive can leave the bay unpowered until the controller driver is reinstalled. Restrict yourself to the exact device node named in the error. If you're unsure which node that is, uninstall one at a time and recheck status between attempts.

Step 2: Clear the UpperFilters and LowerFilters Registry Values

This is the specific fix for Code 19 on CD/DVD drives, and Microsoft's optical drive troubleshooting article names the two values directly. Third-party burning or virtual-disc software registers filter drivers in those values, and a leftover entry pointing at an uninstalled filter produces exactly this error.

1: Press Windows + R, type regedit, and press Enter, confirming the UAC prompt. 2: Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class{4d36e965-e325-11ce-bfc1-08002be10318} — that GUID is the CD/DVD-ROM class key. 3: In the right pane, right-click UpperFilters, choose Delete, and confirm. Repeat for LowerFilters if present. 4: Close Registry Editor and restart Windows. 5: Reopen Device Manager and check the drive's status.

Export the key before deleting by right-clicking the GUID folder and choosing Export — that gives you a .reg file to double-click if the deletion makes things worse. The filter values are sometimes legitimately needed by antivirus or backup software, so if the drive starts working but a program complains about missing filters, reinstall that program to re-register its filter cleanly. Never add filter values back by hand unless a vendor's documentation gives you the exact string.

The GUID above applies only to optical drives. USB controllers live under {36fc9e60-c465-11cf-8056-444553540000}, and keyboards under {4d36e96b-e325-11ce-bfc1-08002be10318} — class GUIDs are published in Microsoft's "System-Defined Device Setup Classes" reference, and using the wrong one edits an unrelated device family. Filter values exist for a handful of classes only; if the value isn't there, its absence is not your problem and deleting nothing is the correct outcome.

Step 3: Reinstall the Driver Package From the Manufacturer

When Code 19 survives a device uninstall and return, replace the driver package rather than repairing it. Download the current driver for your exact model from the manufacturer's support site — Intel, AMD, Realtek, Broadcom, and printer vendors all publish model-specific packages — and run the installer rather than letting Windows pick a driver. Windows Update's generic package occasionally reinstalls the same broken service record.

Uninstall the old package from Settings, then Apps, then Installed apps before running the new installer. Driver packages sometimes appear there under names like "Realtek Audio Driver" or "Intel Wireless Bluetooth," and the uninstaller removes the service registration that a Device Manager uninstall leaves behind. Restart when prompted, install the fresh package, and restart again before checking Device Manager. Two restarts sounds excessive until you've watched a driver registration fail to take until the second boot.

Version-specific caution applies here. On Windows 11, some vendors ship separate packages for 22H2 and 23H2 and later builds, and installing the older branch can register a service the current build rejects — read the support page's OS column rather than grabbing the top download. On Windows 10, the last fully supported feature update is 22H2, and manufacturers have frozen driver branches at that target; a package marked for Windows 11 installed on Windows 10 may fail its digital signature check silently during setup. Check the package's stated OS support before running it.

If the manufacturer no longer hosts a driver for your model — common for printers and scanners past their support window — the Windows in-box driver is your fallback. Uninstall the device with the driver-deletion checkbox, restart, and let Windows install its generic driver without any vendor installer. Features may be reduced, but Code 19 typically clears because the in-box service record is intact.

Step 4: Remove Phantom Devices That Hold the Broken Record

Phantom devices are the edge case most guides skip: a device that's physically gone still has a registry entry, and its damaged service record blocks a new device that reuses the same enumeration path. This shows up after swapping a USB device between ports or reinstalling a printer under a new name. Removing the hidden node usually clears Code 19 on the replacement device.

1: Open Command Prompt as administrator and run set devmgr_show_nonpresent_devices=1 in that window. 2: In the same window, run start devmgmt.msc so Device Manager inherits the variable. 3: In Device Manager, click View, then "Show hidden devices." 4: Expand the relevant category — phantom entries appear greyed out. 5: Right-click the greyed entry matching your device's old name and choose Uninstall device. 6: Restart and recheck the live device's status.

The environment variable lasts only for that Command Prompt session, so the greyed entries vanish from view when you open Device Manager normally later. That's expected, not a failure. Don't mass-delete every greyed entry; storage controllers and network adapters can appear phantom for legitimate reasons, and removing the wrong one can detach a working device.

Step 5: The Registry Permission and Service Key Checks

Two further registry conditions produce Code 19 and neither is fixed by reinstalling drivers. The first is a permissions problem: the class key's subkey for your device instance has an ACL that denies SYSTEM read access, so Windows can see the record but not parse it. The second is a service key whose ImagePath points at a driver file that no longer exists on disk.

For permissions, open Registry Editor, navigate to the device's instance key under the class GUID, right-click the numeric subkey (names look like 0000, 0001), choose Permissions, and confirm SYSTEM has Full Control or at least Read. If SYSTEM is missing entirely, adding it back with Read permission is the correction; take a key export first. This situation is uncommon but appears after aggressive "privacy" or "debloat" scripts that strip registry ACLs wholesale.

For the service key, open HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services and find the service name your device's driver declares — the Details tab of the device's Properties shows "Service" as a property. Expand that key and read ImagePath. If it names a .sys file under C:\Windows\System32\drivers that doesn't exist, the driver file is gone and reinstalling the package is the fix, not editing the path. If ImagePath is missing entirely, the service is malformed and the driver reinstall replaces it.

Don't attempt to hand-write a service key from a working machine. Service keys carry Start type, ErrorControl, Group, and dependency values that vary by device class, and copying them between machines produces new errors rather than fixing Code 19. Manufacturer installers and Windows' own driver store are the supported sources.

Safe Mode and Clean Boot: Isolating a Conflicting Driver

If Code 19 returns every time the device is reinstalled, a third-party driver is likely re-corrupting the record at boot. Safe Mode loads only Microsoft-signed core drivers, so the test is simple: boot into Safe Mode and check the device's status. If Code 19 is absent in Safe Mode, the conflict is with a startup-loaded third-party driver or service.

Boot to Safe Mode from Settings, System, Recovery, "Restart now" under Advanced startup, then Troubleshoot, Advanced options, Startup Settings, Restart, and press 4 for Safe Mode. Check Device Manager there. A device that reports "working properly" in Safe Mode but fails in normal boot points to a filter driver or a startup service, and the fix is to disable startup items selectively rather than chase the device.

Clean Boot narrows the culprit. Run msconfig, open the Services tab, tick "Hide all Microsoft services," click "Disable all," and restart. If Code 19 clears, re-enable half the services, restart, and bisect until the offending service appears. Third-party antivirus, disk-imaging tools, and virtual-drive software are the usual suspects because they install filter drivers in exactly the places Code 19 complains about.

Preventing Code 19 From Coming Back

Most Code 19 recurrences trace to three habits. First, removing hardware without using "Safely Remove Hardware" or "Eject" leaves service records and mount points half-written, and phantom entries accumulate. Second, "PC cleaner" utilities that scrub the registry can delete driver service keys that look orphaned but are referenced by filter values. Third, installing virtual-disc or backup software that adds filter drivers and then uninstalling it imperfectly leaves UpperFilters entries pointing nowhere.

Keep the driver store healthy by using the manufacturer's uninstallers when removing hardware drivers rather than deleting folders under C:\Windows\System32\DriverStore. The DriverStore is protected and its packages are referenced by INF files; deleting files directly breaks the references and produces Code 19 on the next device that needed the same package. If disk space is the motive, use Disk Cleanup's "Device driver packages" option, which removes only superseded packages safely.

For systems with System Restore enabled, a restore point created before any driver update is your cheapest recovery route. Windows creates one automatically before most driver installations through Windows Update, but manual installers often skip it — create one yourself before running any vendor driver setup. And keep a note of which device classes your machine depends on filters for, so a future filter-value cleanup doesn't remove a value antivirus or backup software still needs.

FAQ

Does Code 19 mean my hardware is broken?

No — Code 19 is a registry and driver-service error, and Microsoft's error code list places it in the registry corruption category, so the physical device is usually fine. Confirmed cases overwhelmingly resolve through a device uninstall with the driver-deletion option or a driver package reinstall. Physical failure produces different codes like Code 43 or Code 10. If the device is completely absent from Device Manager and a scan for hardware changes doesn't bring it back, then investigate the cable, port, or slot.

Why does Code 19 keep coming back after I uninstall the device?

The most common cause is a third-party filter driver or startup service rewriting the broken record at boot, which is why the Safe Mode test matters. If the device reports healthy in Safe Mode but fails in normal boot, use Clean Boot to bisect startup services. A less common cause is an installer that keeps restoring an older driver package from a cached folder; delete that cached installer and download the current package from the manufacturer's site.

Can Code 19 appear on a printer that was working yesterday?

Yes — printer drivers register a service plus a port monitor, and a Windows Update driver revision or an interrupted install can leave the service entry malformed overnight. The printer's spooler service keeps running, but the device node fails to start with Code 19. Remove the printer from Settings, then Printers and scanners, restart the Print Spooler service, and reinstall the manufacturer's package. Hiding the device record first prevents Windows from reinstalling the old one automatically.

Is editing the registry dangerous for fixing Code 19?

Only if you edit beyond the named values. Deleting UpperFilters and LowerFilters in the CD/DVD class key is the documented, low-risk change; hand-writing service keys or copying them from another PC is not. Export every key before touching it, so a double-click on the .reg file restores the original. If you're uncomfortable with Registry Editor, the device uninstall and driver reinstall handle most cases without it.

How long does a Code 19 fix usually take?

The device uninstall route takes about five minutes plus one restart; a driver package reinstall from the manufacturer adds 10 to 20 minutes for the download and two restarts. Registry filter-value deletion and the phantom-device sweep each take under 10 minutes. If you're past 45 minutes without resolution, stop and capture the device's Service property and ImagePath value before continuing — that record tells a repair technician exactly where the break is.

Do I need to reinstall Windows to fix Code 19?

No. Reinstalling Windows discards working drivers and settings for a fault that lives in a handful of registry records, and it's the last resort rather than the first step. The full sequence — uninstall with driver deletion, filter-value cleanup, manufacturer reinstall, phantom-device removal, permission and service-key checks — covers every confirmed Code 19 cause documented by Microsoft and device vendors. A Windows in-place upgrade repair (which keeps apps and files) is a reasonable final software step before any clean install.