Skip to content

DEVICE MANAGER ERROR · CM_PROB_REGISTRY

Code 19: Configuration Information in the Registry Is Damaged

The registry entries that tell Windows which driver to load for the device are damaged or point at something that is not there, so Windows cannot start it.

WHAT WINDOWS SHOWS

Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)

Wording from Microsoft's documentation for CM_PROB_REGISTRY. Device Manager shows it on the General tab of the device's Properties.

TECHNICAL SUMMARY

Code19
Windows nameCM_PROB_REGISTRY
Where you see itDevice Manager > the device's Properties > General > Device status
In Tweaky DriverNeeds attention

What causes Code 19

  • More than one service is defined for the device.
  • Windows could not open the service key, or could not read the driver name from it.
  • Microsoft's developer note adds a common case: a filter driver registered for the device, or for its whole device class, names a service that does not exist.

How to fix Code 19, safest step first

The steps follow Microsoft's recommended resolution for this code, in its order, with a reversible step first. Each one says how to put back what it changed.

  1. Before you change anything: note the driver and make a restore point

    Open the device's Properties > Driver tab and write down the driver provider, date and version. Then select Start, type Create a restore point, open it, and on the System Protection tab choose Create. Microsoft notes that System Protection is not turned on by default; if Create is greyed out, choose Configure and turn it on for the system drive first.

    To undo: A restore point changes nothing by itself. To go back later, run System Restore and pick it: Microsoft says it reverts system files, the registry and installed programs, and leaves your personal files alone.

  2. Uninstall and reinstall the driver (Microsoft's first fix)

    In Device Manager, right-click the device and choose Uninstall device, confirm, then choose Action > Scan for hardware changes (or restart). Windows detects the device again and installs a driver for it. Keep the manufacturer's driver package to hand first: Windows may ask for it if it has no driver of its own.

    To undo: If Windows puts back a driver you did not want, use Roll Back Driver when it is offered, or install the driver you kept. The restore point from the first step brings back the whole driver configuration.

  3. Go back to a working registry with System Restore

    Microsoft's second fix is to return the registry to its last working configuration. On Windows 10 and 11 that means System Restore with a restore point made before the problem began (the Last Known Good Configuration option Microsoft also mentions belongs to older Windows versions).

    To undo: Apply a restore point made just before you ran System Restore, if one exists.

Check it yourself

  1. List every device with this code (Command Prompt or PowerShell)

    Available from Windows 10, version 1903. Each device is listed with its instance ID and the problem code with its name, CM_PROB_REGISTRY. No administrator rights needed; nothing is changed.

    pnputil /enum-devices /problem 19
    cmd

  2. Or with PowerShell

    Device Manager shows the same code on the General tab of the device's Properties, in the Device status box.

    Get-PnpDevice | Where-Object { [int]$_.ConfigManagerErrorCode -eq 19 } |
  Format-Table Status, Class, FriendlyName, Problem
    PowerShell

What Tweaky Driver does with Code 19

Needs attention

Tweaky Driver lists a Code 19 device under Diagnostics > Devices as Needs attention, with its code. It offers no driver for it and does not edit the registry: removing a filter entry by hand is a job for the reinstall or System Restore steps above.

Tweaky Driver, the driver checker that shows its sources — free for Windows 10 and 11.

Common questions

What causes Code 19?

Microsoft lists more than one service defined for the device, a service key that cannot be opened, or a driver name that cannot be read from it. A frequent case is a filter driver entry that names a service which no longer exists.

Can I fix Code 19 without editing the registry?

Yes. Microsoft's fixes are to uninstall and reinstall the driver, or to roll the registry back to a working configuration with System Restore. Both avoid hand-editing.

Why does my keyboard show Code 19?

The code means the same thing on any device. Keyboards, mice and cameras often get extra filter drivers from vendor software, and Microsoft's common case for Code 19 is a filter entry that names a service which does not exist, so check whether software for that device was recently removed before reinstalling the device.