Short answer: Device Manager Code 10 means a hardware device failed to start, and the safest troubleshooting steps are to identify the device, check its driver, restart Windows, and investigate possible hardware problems.
What Does Device Manager Code 10 Mean?
Device Manager Code 10 is a Windows device-start failure. The corresponding Windows problem identifier is CM_PROB_FAILED_START.
The typical message is This device cannot start. (Code 10). Windows may also display a recommendation to update the device drivers.
Microsoft explains that Code 10 occurs when a device fails to start. At the driver level, one of the drivers in the device stack may fail the IRP_MN_START_DEVICE request.
The failure can involve a device driver, associated software components, firmware, or the physical device. Code 10 alone does not identify the exact cause.
A device can appear in Device Manager because Windows detects its presence even though the device cannot initialize successfully.
Code 10 is different from Code 28, which commonly indicates that no suitable driver was installed, and Code 43, which indicates that Windows stopped a device because a problem was reported.
Microsoft documents Code 10 at https://learn.microsoft.com/en-us/windows-hardware/drivers/install/cm-prob-failed-start.
Which Devices Can Show Code 10?
Code 10 can affect many types of hardware because it describes a device-start failure rather than a problem limited to one hardware category.
The affected device usually appears in Device Manager with a warning symbol, although the exact appearance depends on its current state and Windows configuration.
Symptoms depend on the hardware involved. A network adapter might lose connectivity, an audio device might stop producing sound, or a connected USB device might become unavailable.
A failing device does not necessarily indicate permanent hardware damage. Driver and configuration problems can produce similar symptoms.
The exact device name and error message should be recorded before attempting changes.
- Network adapters: Wi-Fi or Ethernet connectivity may be unavailable.
- Bluetooth adapters: Bluetooth devices may stop connecting.
- USB controllers and devices: Connected peripherals may fail to initialize.
- Audio devices: Sound input or output may become unavailable.
- Graphics adapters: Display functionality or hardware acceleration may be affected.
- Storage controllers: Connected drives or storage functionality may be affected.
- Cameras and other peripherals: Device-specific applications may fail to detect the hardware.
Step 1: Confirm the Error and Windows Version
Begin by checking the exact error message and identifying the affected hardware.
1. Press Win + R, type winver, and press Enter.
2. Record your Windows version and OS build from the About Windows dialog.
3. Press Win + X and select Device Manager. Alternatively, press Win + R, type devmgmt.msc, and press Enter.
4. Look for a device with a yellow warning symbol.
5. Expand the relevant device category and double-click the affected device.
6. Open the General tab and read the Device status field.
7. Confirm that the displayed message contains Code 10.
8. Record the exact device name, error message, and any additional information.
9. Open the Driver tab and record the driver provider, date, and version.
10. Open the Events tab, if available, and review recent events associated with the device.
Device Manager's General tab is the primary location for confirming the problem code. The Events tab may provide useful context but does not necessarily identify the underlying cause.
Windows 11 and Windows 10 both support Device Manager. The exact interface layout may vary between Windows releases.
Step 2: Restart Windows and Recheck the Device
A restart is a reasonable first troubleshooting step because it allows Windows to initialize devices and drivers again.
1. Save your work and close running applications.
2. Open Start > Power > Restart.
3. Allow Windows to complete the restart.
4. Open Device Manager again using devmgmt.msc.
5. Locate the affected device.
6. Open Properties > General and check whether Code 10 is still displayed.
If the device now reports that it is working properly, test its actual functionality before considering the issue resolved.
If Code 10 returns, continue with driver identification and troubleshooting.
Use Restart rather than assuming that shutting down and powering on has the same effect on every configuration. Windows Fast Startup can change shutdown behavior on supported systems.
Do not repeatedly restart a computer that is experiencing storage failures, overheating, or other serious hardware symptoms without investigating those problems.
Step 3: Identify the Device by Hardware ID
The hardware ID helps identify the device when Windows displays a generic name or when several similar devices are installed.
1. Open Device Manager.
2. Right-click the affected device and select Properties.
3. Open the Details tab.
4. Select Hardware Ids from the Property dropdown.
5. Copy the displayed identifiers.
6. Also inspect Device instance path in the same dropdown when you need to identify the exact device instance.
PCI devices commonly use identifiers containing VEN and DEV fields. USB devices commonly use VID and PID fields.
For example, a PCI hardware ID may begin with PCI\VEN_ followed by a manufacturer identifier and DEV_ followed by a device identifier.
These identifiers help match the hardware to an appropriate manufacturer driver. They do not establish that a specific driver package is safe or compatible by themselves.
Use the device manufacturer's official support information to confirm the hardware model.
Do not download drivers from unfamiliar websites solely because their pages contain a matching hardware ID.
Hardware IDs and device instance paths can contain unique device information. Avoid publishing complete identifiers unnecessarily when requesting public support.
Step 4: Check Windows Update for Driver Updates
Microsoft recommends Windows Update as a primary method for obtaining compatible driver updates.
1. On Windows 11, open Settings > Windows Update.
2. Select Check for updates.
3. Allow available updates to download and install.
4. If a restart is requested, complete it before continuing.
5. Open Settings > Windows Update > Advanced options.
6. Select Optional updates if that option is available.
7. Expand Driver updates and review any offered packages.
8. Install a relevant driver update only after checking that it applies to the affected device.
9. Restart Windows when requested.
10. Return to Device Manager > affected device > Properties > General and check the device status.
Optional driver updates are not always available. Their absence does not prove that the installed driver is correct or that no newer manufacturer driver exists.
On Windows 10, the comparable update interface is Settings > Update & Security > Windows Update.
The exact location and availability of optional updates depend on the Windows version, update configuration, and administrative policy.
Microsoft's driver update guidance is available at https://support.microsoft.com/en-us/windows/hardware/drivers/update-drivers-through-device-manager-in-windows.
Step 5: Update the Driver Through Device Manager
If Windows Update does not resolve Code 10, use Device Manager to check for an appropriate driver.
1. Press Win + X and select Device Manager.
2. Expand the category containing the affected device.
3. Right-click the device and select Update driver.
4. Choose Search automatically for drivers.
5. Follow the displayed instructions.
6. If Windows reports that the best available driver is already installed, record that result.
7. Restart Windows if requested.
8. Reopen the device's Properties > General tab and check the status.
The automatic search result does not guarantee that the driver is functioning correctly or that the latest compatible manufacturer package is installed.
If you already have a verified driver package from the manufacturer, Device Manager also provides Browse my computer for drivers.
When using the manual option, select the directory containing the extracted driver files and follow the installation instructions.
Do not select an arbitrary INF file simply because Windows accepts it. The driver must support the exact hardware and Windows configuration.
Never disable Windows driver signature enforcement or other security protections merely to install an unverified driver.
Step 6: Install the Official Manufacturer Driver
A manufacturer-provided driver may be appropriate when Windows does not offer a working driver or when the manufacturer documents a specific Code 10 issue.
1. Identify the computer or hardware model.
2. For a laptop or prebuilt computer, start with the computer manufacturer's official support website.
3. For a separately purchased component, check the component manufacturer's official support website.
4. Confirm the exact device model and supported Windows version.
5. Check whether the driver package supports your processor architecture and hardware revision.
6. Read the manufacturer's installation instructions and release notes.
7. Download the appropriate driver from the official source.
8. Follow the manufacturer's documented installation procedure.
9. Restart Windows when requested.
10. Verify the result under Device Manager > affected device > Properties > General.
Do not assume the newest available package is automatically the correct choice. Some computers require model-specific or manufacturer-customized drivers.
For network adapters, obtain the verified driver before removing an existing driver if losing network connectivity would prevent further downloads.
For storage controllers and other boot-critical devices, avoid changing drivers without a verified recovery procedure.
If the manufacturer documents a firmware update as necessary, follow its official instructions. Firmware changes involve additional risk and should not be performed without a specific reason.
Step 7: Roll Back a Recent Driver Update
If Code 10 appeared immediately after a driver update, returning to the previous installed version may help.
1. Open Device Manager.
2. Right-click the affected device and select Properties.
3. Open the Driver tab.
4. Select Roll Back Driver if the button is available.
5. Choose the reason requested by Windows.
6. Confirm the rollback.
7. Restart Windows if prompted.
8. Return to Properties > General and check whether the error remains.
The Roll Back Driver button is unavailable when Windows does not have an eligible previous driver version or rollback is unsupported for that device.
Do not attempt to force a rollback by manually deleting driver files from Windows system directories.
If the previous driver resolves the problem, record the working version before installing another update.
A successful rollback does not necessarily prove that the newer driver was universally defective. The issue may involve compatibility with the specific hardware or software configuration.
Step 8: Reinstall the Device Driver Carefully
If updating or rolling back the driver does not help, reinstalling the device can be a reasonable next troubleshooting step.
Before proceeding, identify the device and make sure you can restore a working driver if Windows cannot reinstall it automatically.
1. Save your work and close applications using the affected device.
2. Obtain the official replacement driver in advance when necessary.
3. Open Device Manager.
4. Right-click the affected device.
5. Select Uninstall device.
6. Review the confirmation dialog carefully.
7. Do not select an option to remove or delete the driver software unless you specifically intend to remove that package and have a verified replacement available.
8. Confirm Uninstall.
9. Restart Windows, or use Device Manager > Action > Scan for hardware changes when appropriate.
10. Allow Windows to detect the device and attempt driver installation.
11. Reinstall the verified manufacturer driver if Windows cannot locate a suitable package.
12. Check Device Manager > Properties > General for the resulting status.
The exact uninstall dialog and available options depend on the Windows version and device type.
Removing a device from Device Manager is not the same as physically disconnecting it or deleting its driver package from the Driver Store.
Some devices require additional vendor-specific software or installation steps. Follow the official documentation when applicable.
Do not casually uninstall boot-critical storage controllers, the only available network adapter, or other essential hardware on a computer that you cannot readily recover.
Step 9: Check Connections and Hardware
If Code 10 continues after appropriate driver troubleshooting, inspect the physical device and its connections.
The correct checks depend on whether the device is external, removable, or integrated into the computer.
For an external USB device, disconnect it safely, inspect the cable and connector, and try another known-working USB port when appropriate.
If the device requires external power, confirm that its power supply is connected and operating according to the manufacturer's instructions.
If a USB hub or docking station is involved, test a direct connection to the computer when the device supports one.
For removable peripherals, testing with another compatible computer can help distinguish device-specific problems from issues with the original computer.
If the same device fails on multiple compatible computers, a hardware problem becomes more plausible, but additional testing may still be needed.
For internal components, consult the computer manufacturer's documentation before opening the enclosure or reseating hardware.
Do not disconnect internal components while the computer is powered on.
For laptops and devices under warranty, contact the manufacturer before attempting hardware disassembly.
If a storage device is failing or contains important data, prioritize data preservation and qualified assistance rather than repeated experimental repairs.
- USB device: Inspect the cable, connector, and USB port.
- USB hub: Test a supported direct connection when possible.
- External device: Check any required external power supply.
- Bluetooth device: Verify the adapter and device status separately.
- Network adapter: Confirm hardware identity and preserve a recovery path for connectivity.
- Internal component: Follow the manufacturer's hardware service instructions.
- Storage device: Avoid troubleshooting actions that could threaten important data.
- Repeated failure across compatible computers: Consider professional hardware diagnosis.
Advanced Diagnosis with PnPUtil
Windows includes PnPUtil, a command-line utility that can display information about connected devices and driver packages.
PnPUtil is normally located at %windir%\System32\pnputil.exe.
To verify the Windows version, press Win + R, run winver, and inspect the displayed OS build.
Open Command Prompt as administrator for administrative troubleshooting.
Run pnputil /? to display the options supported by the installed Windows version.
On supported Windows versions, run pnputil /enum-devices /problem to list devices reporting problem codes.
To focus on Code 10, run pnputil /enum-devices /problem 10.
If you know the exact device instance path, run pnputil /enum-devices /instanceid "DEVICE_INSTANCE_PATH", replacing DEVICE_INSTANCE_PATH with the value copied from Device Manager > Properties > Details > Device instance path.
PnPUtil's device enumeration functionality was introduced in Windows 10 version 1903. Check pnputil /? for supported options on the current installation.
These enumeration commands are read-only and do not reinstall, disable, remove, or reset hardware.
Compare the reported problem code with Device Manager > Properties > General.
If the command returns no matching devices, confirm that the device still reports Code 10 and that the expected hardware is connected.
Avoid using PnPUtil commands that delete driver packages, disable devices, or restart devices unless you understand the affected hardware and have a specific recovery plan.
Microsoft documents the supported commands at https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/pnputil-command-syntax.
- pnputil /?: Displays the supported PnPUtil commands.
- pnputil /enum-devices /problem: Lists devices reporting problems.
- pnputil /enum-devices /problem 10: Filters for Device Manager Code 10.
- pnputil /enum-devices /instanceid "DEVICE_INSTANCE_PATH": Inspects a specific device instance.
- devmgmt.msc: Opens Device Manager.
- winver: Displays the Windows version and OS build.
- Read-only inspection is preferable before modifying drivers or device configuration.
Check Device Installation Logs and Events
If Code 10 persists, Windows diagnostic records may provide more context.
Device installation information is recorded in the SetupAPI device installation log, normally located at %windir%\INF\setupapi.dev.log.
To identify the Windows directory, open Command Prompt and run echo %windir%.
To verify that the log exists, run dir "%windir%\INF\setupapi.dev.log".
To inspect it without editing the original file, run notepad "%windir%\INF\setupapi.dev.log".
Search the log for the affected device's hardware ID or device instance identifier.
The SetupAPI log primarily records device installation activity. A runtime device-start failure may not have a corresponding explanatory entry.
You can also press Win + R, enter eventvwr.msc, and inspect Windows Logs > System.
Look for relevant events near the time the device failed, including events involving the device, driver, or Plug and Play subsystem.
Open Device Manager > affected device > Properties > Events to review device-specific events when the tab is available.
Do not assume that every warning or error in Event Viewer is related to Code 10.
Record event timestamps, providers, and error details before drawing conclusions.
Microsoft documents device installation troubleshooting at https://learn.microsoft.com/en-us/windows-hardware/drivers/install/troubleshooting-device-and-driver-installations.
Safe vs. Unsafe Code 10 Troubleshooting
Code 10 troubleshooting should begin with identification and reversible changes.
Avoid generic repair instructions that modify unrelated services, registry entries, or protected Windows files.
- Safe: Confirm the error in Device Manager > Properties > General.
- Safe: Record the driver version and hardware ID before making changes.
- Safe: Restart Windows and recheck device status.
- Safe: Inspect available drivers through Windows Update.
- Generally safe: Update drivers using official manufacturer packages matched to the hardware.
- Conditionally safe: Roll back a driver when a compatible previous version is available.
- Conditionally safe: Uninstall and redetect a device when a recovery path exists.
- Conditionally safe: Test an external peripheral with another known-working cable or port.
- Unsafe: Installing drivers from untrusted download websites.
- Unsafe: Disabling driver signature enforcement to bypass compatibility warnings.
- Unsafe: Deleting random files from Windows driver directories.
- Unsafe: Using registry cleaners that promise to repair Code 10 automatically.
- Unsafe: Removing driver packages without identifying the affected hardware.
- Unsafe: Changing BIOS or firmware settings without a device-specific reason and recovery procedure.
- Not recommended: Assuming Code 10 always means the hardware is permanently damaged.
- Not recommended: Repeatedly reinstalling drivers without recording whether the error changes.
Code 10 vs. Code 28 and Code 43
Windows Device Manager uses different problem codes to describe different stages of device failure.
Code 10 corresponds to CM_PROB_FAILED_START. The device was detected, but the device-start operation failed.
Code 28 corresponds to CM_PROB_FAILED_INSTALL. Windows does not have a selected working driver installed for the device.
Code 43 corresponds to CM_PROB_FAILED_POST_START. Windows reports that a device encountered a problem after its start sequence.
These codes can occur on similar types of hardware but should not be treated as interchangeable.
Always read the exact error under Device Manager > affected device > Properties > General before following a repair guide.
Microsoft's device problem code reference is available at https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/device-manager-problem-codes.
- Code 10: The device failed to start.
- Code 28: Windows could not complete driver installation and no driver is selected.
- Code 43: The device reported a problem after starting.
- The correct troubleshooting path depends on the actual code and device.
- A warning symbol alone does not identify the specific failure.
What If Device Manager Code 10 Still Appears?
If the error remains after using the appropriate driver update, rollback, and reinstall procedures, investigate whether the failure is specific to the operating system, driver, or hardware.
Record the computer model, exact hardware ID, installed driver version, Windows build, and any relevant diagnostic messages.
Check the official hardware manufacturer's support documentation for known compatibility problems.
If the issue began after a Windows update, review Settings > Windows Update > Update history to identify the installation date.
If the hardware manufacturer provides a diagnostic utility for the affected component, follow its documented instructions.
Testing an external device on another compatible computer can provide additional evidence without modifying Windows system components.
If the hardware fails repeatedly, contact the manufacturer or qualified technical support.
For storage devices, preserve important data before attempting repairs.
For organization-managed computers, contact the administrator before changing drivers, firmware, or security settings.
Do not reinstall Windows solely because Device Manager displays Code 10 unless broader diagnosis shows that a reinstall is justified.
A persistent Code 10 error does not guarantee a software-only repair. Some failures require hardware replacement or manufacturer service.
Key Takeaways and Related Guides
Device Manager Code 10 means that Windows detected a device but could not start it successfully.
Begin by confirming the error in Device Manager and recording the hardware ID, driver version, and Windows build.
Try a normal Windows restart, check Windows Update, and obtain compatible drivers from official sources.
If the issue appeared after a driver update, investigate the Roll Back Driver option before removing driver packages.
Use PnPUtil and Windows diagnostic logs for read-only investigation when basic troubleshooting does not reveal the cause.
Avoid registry cleaners, unverified drivers, forced driver removal, and unnecessary security changes.
If the error persists, check physical connections and consult the device manufacturer.
Official Microsoft Code 10 documentation: https://learn.microsoft.com/en-us/windows-hardware/drivers/install/cm-prob-failed-start.
Official Windows driver update instructions: https://support.microsoft.com/en-us/windows/hardware/drivers/update-drivers-through-device-manager-in-windows.
Official Device Manager error code reference: https://support.microsoft.com/en-us/windows/hardware/drivers/error-codes-in-device-manager-in-windows.
- Code 10 identifies a device-start failure, not necessarily broken hardware.
- Check Device Manager > Properties > General for the exact error.
- Record hardware IDs and driver versions before making changes.
- Prefer Windows Update and official manufacturer drivers.
- Roll back a recent driver update when appropriate.
- Reinstall device drivers only with a recovery method available.
- Use PnPUtil for additional read-only diagnostics.
- Investigate hardware if software troubleshooting does not resolve the error.
Related: