Skip to content

DEVICE MANAGER ERROR · CM_PROB_DISABLED_SERVICE

Code 32: A Driver (Service) for This Device Has Been Disabled

Every driver runs as a service with a start type, and this one is set to Disabled, so Windows will not load it. As the message says, another driver may be doing the job, in which case nothing is missing.

WHAT WINDOWS SHOWS

A driver (service) for this device has been disabled. An alternate driver may be providing this functionality. (Code 32)

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

TECHNICAL SUMMARY

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

What causes Code 32

  • The start type of the driver's service is set to Disabled in the registry (Microsoft Learn and Microsoft Support).

How to fix Code 32, 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. Find the driver's service and its start type

    On Windows 11, version 21H2 or later, pnputil /enum-devices /problem 32 /services names the service. Then sc qc <service> shows its START_TYPE; note it exactly.

    To undo: Nothing to undo: these commands only read.

  3. If the driver is really needed, change the start type

    Microsoft's resolution: if the driver really is required, change the start type. Drivers normally start at boot, system or on demand; use the start type the driver's documentation or a working PC gives, for example sc config <service> start= demand from an administrator prompt, then restart.

    To undo: sc config <service> start= disabled puts back the value you noted, or apply the restore point.

  4. Or reinstall the device (Microsoft Support's 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.

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

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

What Tweaky Driver does with Code 32

Needs attention

Tweaky Driver lists a Code 32 device under Diagnostics > Devices as Needs attention, with its code. It does not change service start types and offers no driver for a device in this state.

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

Common questions

Should I always re-enable a driver that shows Code 32?

No. The message itself says an alternate driver may be providing the same function. Microsoft's guidance is to change the start type only if the driver really is required.

How do I find which service Code 32 refers to?

Run pnputil /enum-devices /problem 32 /services (Windows 11, version 21H2 or later), then sc qc with that service name to see its start type.

Why would a driver service be disabled?

The start type is a registry value, so anything with administrator rights can set it: an uninstaller, a tuning tool or a person. Microsoft Support's fix of reinstalling the device writes a fresh configuration.