How to Fix Code 10 "This Device Cannot Start" in Windows

Code 10 means Windows detects the hardware but cannot start it. Restart Windows, check the device’s connection and power, then update, roll back, or reinstall the correct driver; if the error appears on another computer too, the hardware or its firmware is more likely at fault. First identify the exact Device Manager entry and record its model before changing anything.

What Code 10 means and which device is actually failing

Windows assigns Code 10 when it detects a device but cannot start it. The code does not identify the cause: a damaged or incompatible driver, a Windows update, insufficient USB power, a firmware problem, or failing hardware can all produce it.

Open Device Manager and find the entry with a yellow warning icon. Check categories such as Universal Serial Bus controllers, Network adapters, Display adapters, Sound, video and game controllers, or Other devices.

This device cannot start. (Code 10)

The message appears when Windows tries to start the device and the device or its driver fails initialization.

1. Right-click the affected device and select Properties.
2. On the General tab, read Device status and confirm that it shows Code 10.
3. Open the Details tab and select Hardware Ids from the Property list.
4. Record the device name, manufacturer, model, driver provider, driver date, and driver version.
5. Check the Events tab for a recent driver installation, device-start failure, or configuration change.

The hardware ID distinguishes devices with similar names. Values such as USB\VID_..., PCI\VEN_..., or a wireless adapter’s model identifier identify the exact component. If Device Manager shows another code, such as Code 28, Code 31, Code 43, or Code 45, troubleshoot that code instead of treating Code 10 as the active problem.

Before changing drivers, check the connection, power, and recent changes

This procedure applies to Windows 10 and Windows 11 devices that appear in Device Manager. You normally need an Administrator account for driver changes, firmware installers, and some Device Manager actions. Save open work before restarting. Driver removal does not normally delete personal files, but back up important files before firmware, BIOS, or Windows recovery work.

Check these causes before changing software:

• Disconnect and reconnect an external device firmly. Inspect the cable for damage and use the device’s own power adapter if it has one.
• For USB hardware, try another port. Connect directly to the computer rather than through an unpowered hub, dock, or monitor.
• If the device has a power switch or indicator, confirm that it is on. A USB device that works only when other USB devices are disconnected may be exceeding the available port or hub power.
• Note whether the failure began after Windows Update, a driver installation, new security software, a dock change, or a BIOS or firmware update.
• If possible, test the device on another computer. A failure there points toward the cable, device, power supply, or firmware rather than this Windows installation.

For a laptop, connect the charger while testing. For a graphics card, Wi-Fi card, or internal audio device, do not open the computer unless you can work safely with powered-off hardware and follow the manufacturer’s instructions.

Fix Code 10 in the safest order

Work through these steps in order. Each step is less disruptive than the next. Use an Administrator account when Windows requests permission.

1. Restart Windows from the Start menu, then check Device Manager again. A restart reloads the device stack and clears some temporary startup failures.

Start > Power > Restart

If Code 10 disappears, test the device in its normal application. If it remains, continue. Repeated restarts will not repair a persistent driver, power, firmware, or hardware fault.

2. Reconnect the device and try a known-good connection. For USB hardware, use another port directly on the computer. For network, audio, or display hardware, reseat the cable and check the device’s power source.

If the device starts, the original port, cable, hub, or power source is the likely cause. If it does not, continue to the driver checks.

3. Install pending Windows updates, restart, and check Device Manager. Windows Update can provide a compatible driver, but it can also introduce one that does not suit older hardware. If Code 10 began immediately after an update, use the rollback step instead of repeatedly installing updates.

Settings > Windows Update > Check for updates

The expected result is that Windows installs an applicable update and the device starts without Code 10. If the warning remains, the available update did not resolve the device’s startup problem.

4. Update the device driver through Device Manager. Right-click the affected device, choose Update driver, select Search automatically for drivers, and restart if Windows installs one.

The expected result is a changed driver entry and no Code 10 warning. If Windows says the best driver is already installed, its local or Windows Update search found nothing newer; that does not prove the current driver is suitable.

5. Roll back the driver if the problem began after a driver or Windows update. Open the device’s Properties, select the Driver tab, and choose Roll Back Driver if available.

Device Manager > affected device > Properties > Driver > Roll Back Driver

Choose a reason, confirm, and restart. If Code 10 clears, the earlier driver was likely incompatible with the device. If Roll Back Driver is unavailable, Windows may not have retained the previous package. Do not download a similarly named package from an unknown site.

6. Uninstall the device and let Windows rediscover it. Close applications that use the hardware first.

Before uninstalling a storage controller, system device, or critical network adapter, record the model and download a known-good driver from the computer or device manufacturer. Do not select Delete the driver software for this device unless you already have a compatible replacement and understand the recovery steps.

1. In Device Manager, right-click the affected device and select Uninstall device.
2. Confirm the removal without deleting the driver package unless necessary.
3. In Device Manager, select Action > Scan for hardware changes.
4. Restart Windows and check the device again.

Device Manager > Action > Scan for hardware changes

Windows should recreate the device entry and load a driver. If it returns with Code 10, install the driver supplied by the computer, motherboard, or device manufacturer. Match the exact model and Windows version; for a laptop, the laptop manufacturer’s package is often preferable to a generic component package.

7. Install manufacturer firmware only when the release specifically applies to your model and problem. Firmware can address USB controller, dock, graphics, Wi-Fi, or storage compatibility issues, but interrupting an update can leave hardware unusable.

Follow the vendor’s power and recovery instructions. If the vendor requires a BIOS update, use the documented recovery method. Do not change unrelated BIOS settings, and do not begin a BIOS update without reliable power, the exact model-specific file, and a recovery plan.

How to confirm the device is working again

A cleared warning icon is not enough. Confirm that Windows starts the device and that the application you use can access it.

1. Open Device Manager and select View > Devices by type if needed.
2. Open the device’s Properties and confirm that Device status says:

This device is working properly.

3. Check the Driver tab and record the provider, date, and version if you updated or rolled back the driver.
4. Test the hardware in its real use: transfer a file with a USB drive, join a network with the Wi-Fi adapter, play audio through the affected output, or open a 3D application for a graphics adapter.
5. Restart Windows once more and repeat the test. A device that works only until the next restart still has a startup, power-management, driver, or firmware problem.

You can inspect Event Viewer when the problem returns. Open Windows Logs > System and look around the failure time for entries from Kernel-PnP, the device driver, or a related service. The details may show a driver name or instance ID, but an event entry alone does not prove that the hardware is defective. Compare it with the exact device and driver information in Device Manager.

When Code 10 points to hardware failure

Stop treating the issue as a Windows driver problem when the device shows Code 10 on another computer, fails with a known-good cable and power source, or repeatedly fails after a correct manufacturer driver is installed. A USB device that disconnects under load, a graphics card that produces artifacts, or an adapter that disappears from Device Manager can have a physical or firmware fault.

Use controlled comparisons before replacing it:

• Test the device on another compatible computer.
• Test a known-good device in the same port, cable, or power setup.
• If the issue began after a recent driver change, use Roll Back Driver or System Restore when an appropriate restore point exists.
• Check the manufacturer’s support page for a model-specific driver, firmware release, recall, or documented compatibility issue.

System Restore can return system drivers and settings to an earlier state, but it does not repair physically damaged hardware and may remove applications installed after the restore point.

Do not use random driver-update utilities or packages from unofficial download sites. They can install the wrong driver, add unwanted software, or make recovery harder. Do not change BIOS settings merely to clear Code 10, and do not update the BIOS without reliable power, the exact model-specific file, and a recovery plan.

If the device fails on multiple computers or the manufacturer’s diagnostic tool reports a fault, replace it or arrange warranty service. If only this Windows installation is affected and a clean manufacturer driver or System Restore does not help, repairing or reinstalling Windows may be the final software step; back up your files first.

Conclusion

Start with the exact Device Manager entry, then check the connection and power before changing drivers. Restart and test the device after each change. If Code 10 follows the device to another computer or returns with a known-good driver, stop changing Windows settings and arrange hardware service or replacement.

Frequently Asked Questions

Will restarting Windows fix Code 10?

Sometimes. Restarting reloads the device driver and can clear a temporary startup or power-state failure. A persistent Code 10 requires checks of the connection, power, driver, firmware, and hardware.

Should I delete the driver when uninstalling the device?

Usually not on the first reinstall attempt. Let Windows rediscover the device while retaining the driver package. Delete the package only when you have a compatible replacement and a recovery plan.

Can Windows Update cause Code 10?

Yes. An update can install an incompatible driver or change how Windows starts the device. If the error began directly after an update, roll back the device driver and then install the manufacturer’s compatible version.

How do I know if the device itself is broken?

Test it on another compatible computer with a known-good cable and power source. If it shows the same failure there, hardware or device firmware is more likely than a problem limited to your Windows installation.