DEVICE MANAGER ERROR · CM_PROB_FAILED_START
Code 10: This Device Cannot Start
Windows tried to start the device and one of the drivers for it refused. Most devices have several drivers stacked on top of each other, and the code does not say which one failed, so it points at the driver rather than proving the hardware is broken.
WHAT WINDOWS SHOWS
This device cannot start. (Code 10)
Try upgrading the device drivers for this device.
Microsoft notes that a driver or enumerator can supply its own text in a "FailReasonString" registry value; when it does, Device Manager shows that text instead of the generic message above.
Wording from Microsoft's documentation for CM_PROB_FAILED_START. Device Manager shows it on the General tab of the device's Properties.
TECHNICAL SUMMARY
| Code | 10 |
|---|---|
| Windows name | CM_PROB_FAILED_START |
| Where you see it | Device Manager > the device's Properties > General > Device status |
| In Tweaky Driver | Needs attention |
What causes Code 10
- One of the drivers in the device's driver stack failed the start request Windows sent it (Microsoft Learn).
- With many drivers in the stack it can be hard to tell which one failed; Microsoft points developers at the device's ProblemStatus property, which records the error the start request returned.
- When one of the drivers is a user-mode (UMDF) driver, the host process that runs it may have stopped; Microsoft lists that as a case for the driver's owner to investigate.
How to fix Code 10, 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.
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.
If it started after a driver update, roll the driver back
In Device Manager, right-click the device, choose Properties, open the Driver tab and select Roll Back Driver, then give a reason and confirm. Microsoft notes that you need administrator rights, and that going back to the previous driver often fixes a problem that appeared after an update. The button is greyed out when Windows kept no earlier driver for the device.
To undo: Rolling back is the undo for the update. To return to the newer driver, install it again with Update driver or from the manufacturer's package.
Update the driver (Microsoft's recommended fix)
In Device Manager, right-click the device, choose Update driver and let Windows search, or point it at a driver you downloaded from the hardware manufacturer. Microsoft's own tip is that Windows Update is the usual way drivers arrive.
To undo: Open the device's Properties > Driver tab and choose Roll Back Driver, or apply the restore point.
Get a driver from the hardware manufacturer
Download the current driver for your exact model from the manufacturer's support page and install it. Microsoft's note for this code is that you may be asked for the driver's location, and the manufacturer's site is where to get it.
To undo: Roll Back Driver on the Driver tab returns to the driver you had, or apply the restore point.
Check it yourself
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_FAILED_START. No administrator rights needed; nothing is changed.
cmdpnputil /enum-devices /problem 10Or with PowerShell
Device Manager shows the same code on the General tab of the device's Properties, in the Device status box.
PowerShellGet-PnpDevice | Where-Object { [int]$_.ConfigManagerErrorCode -eq 10 } | Format-Table Status, Class, FriendlyName, Problem
What Tweaky Driver does with Code 10
Needs attentionTweaky Driver lists a Code 10 device under Diagnostics > Devices as Needs attention, with the note that a newer driver may help but the code alone does not identify the cause. Code 10 is one of the two codes it can offer a repair for: when Windows Update has a driver for that exact device that can be installed here, the scan shows it as a possible repair. The install exports the current driver, creates and checks a restore point, installs through Windows Update and reads the device again; it calls the device working only when Windows reports no problem. If Windows Update has no installable driver, it says no repair is offered. Microsoft Update Catalog and manufacturer packages are not offered to a device in this state.
Tweaky Driver, the driver checker that shows its sources — free for Windows 10 and 11.
Common questions
What does "This device cannot start (Code 10)" mean?
Windows sent the device's drivers the request to start and one of them failed it. The device may be fine; the driver stack around it did not come up.
Why does my Wi-Fi adapter or Bluetooth show Code 10?
The code is the same for every device class. Some drivers write their own reason into the message; otherwise you see the generic text. Roll back if it began after an update, then update the driver as Microsoft recommends, using the PC or adapter manufacturer's driver if Windows has none.
Should I uninstall the device for Code 10?
Microsoft's recommended fix for Code 10 is to update the driver. Uninstalling and reinstalling is the step Microsoft gives for related codes such as 43 and 39; it is safe to try, as long as you have the driver package or a restore point.
Can Tweaky Driver fix Code 10?
When Windows Update has an installable driver for that device, Tweaky Driver offers it as a possible repair, with a restore point first and a check of the device afterwards. It does not claim the device is fixed unless Windows stops reporting a problem.