Skip to content

DEVICE MANAGER ERROR · CM_PROB_DISABLED

Code 22: This Device Is Disabled

Someone, or something acting for them, disabled the device in Device Manager. Windows has a driver for it and simply is not using it. It is the one common code that is a choice rather than a fault.

WHAT WINDOWS SHOWS

This device is disabled. (Code 22)

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

TECHNICAL SUMMARY

Code22
Windows nameCM_PROB_DISABLED
Where you see itDevice Manager > the device's Properties > General > Device status
In Tweaky DriverDisabled

What causes Code 22

  • The device was disabled with Device Manager (Microsoft Learn and Microsoft Support).

How to fix Code 22, 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. Enable the device (Microsoft's recommended fix)

    In Device Manager, right-click the device and choose Enable device. From an administrator command prompt, pnputil /enable-device "<instance ID>" does the same; the instance ID is shown by pnputil /enum-devices /problem 22.

    To undo: Right-click the device and choose Disable device, or run pnputil /disable-device "<instance ID>".

  2. If it was disabled on purpose, leave it

    Devices are sometimes disabled deliberately: a second audio output, a built-in camera, a touch screen. Ask who set the PC up before turning one back on.

    To undo: Nothing to undo.

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_DISABLED. No administrator rights needed; nothing is changed.

    pnputil /enum-devices /problem 22
    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 22 } |
      Format-Table Status, Class, FriendlyName, Problem
    PowerShell

What Tweaky Driver does with Code 22

Disabled

Tweaky Driver shows a Code 22 device as Disabled, with the note that a driver update is not evidence that it should be enabled. It does not enable or disable devices, and it never offers driver updates for a disabled device. On the PC used for this page, `pnputil /enum-devices /problem 22` listed one disabled USB input device and gave its status as Disabled rather than printing a problem code line, while Windows' device list reported it with code 22.

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

Common questions

Is Code 22 an error?

Not in the usual sense. Microsoft's explanation is that the device was disabled in Device Manager; enabling it is the whole fix.

How do I enable a device with Code 22?

Right-click it in Device Manager and choose Enable device. To do it from a command prompt run as administrator, use pnputil /enable-device with the device's instance ID.

Why would a driver tool not update a disabled device?

Because an update would not tell you whether the device should be on. Tweaky Driver leaves Code 22 devices alone and shows them as Disabled, so turning one back on stays your decision.