Device Manager Code 10: What “This Device Cannot Start” Actually Means and How to Fix It (2026 Updated Guide)

Quick answer

Code 10 — “This device cannot start” — means the driver loaded, but when Windows asked the device to start, the device returned a failure. It’s a status, not a diagnosis. The fix depends on which device is showing the code, what changed recently, and whether the hardware itself is healthy. Identify those three things before doing anything.

Before you start

A direct warning before anything else: do not install a “driver updater” application to fix this. The category — Driver Booster, Driver Easy, DriverPack, IObit Driver Updater, and the dozens of clones — is consistently flagged by independent reviewers and security researchers for misleading practices, bundled software, and overstated diagnoses. Some are outright unsafe. None of them have access to drivers you can’t get directly from the device manufacturer or Windows Update, and several of them install drivers that are actively wrong for your hardware.

You don’t need a driver updater. You need to find the right driver from the right source — and most of the time, you don’t even need a driver update; you need to identify which device is failing and why.

A few more things to lock down:

  • Note exactly what changed before this started. A Windows update? A new peripheral? A driver install? A BIOS/UEFI update? The cause is often in the most recent change.
  • Don’t roll back BIOS/UEFI firmware unless you’re confident the rollback path is supported and you have the original installer. BIOS rollback can brick a system on devices that don’t support downgrade.
  • Don’t use “registry cleaners.” They will not fix Code 10 and they will sometimes make it worse.
  • Administrator rights are required for every fix below.

What this error means

The exact wording you see in Device Manager is: “This device cannot start. (Code 10)” — sometimes followed by additional text like “A request for the device descriptor failed” or “Insufficient system resources exist to complete the API.”

In the Windows driver model, when a device is enumerated, Windows loads its driver and then asks the device to start. The device responds with one of several status codes. Code 10 is “the start request failed.” Windows is reporting what the device told it. That’s why Code 10 is the most common and most generic of the Device Manager codes — almost anything that can go wrong with a device under Windows surfaces here.

What Code 10 doesn’t tell you: why the device refused to start. Was it a wrong driver? A hardware fault? A power-state problem? An IRQ conflict? A USB enumeration issue? The error code is identical for all of those, which is why people get stuck.

The fix sequence in this guide works by ruling out the cheap, common causes first, then escalating only when needed.

Where this error appears

Code 10 shows up in Device Manager (Right-click Start → Device Manager), with a yellow warning triangle on the affected device. Right-clicking → Properties → General tab shows the Code 10 message and any sub-text.

Most common offenders:

  • USB devices (mice, keyboards, audio adapters, DACs, controllers)
  • Network adapters (especially Wi-Fi adapters after a major Windows update)
  • Audio devices (Realtek, Intel SST, USB DACs)
  • Cameras (laptop webcams, especially after Windows Update changes)
  • Printers and printer-like devices (multifunction units)
  • Bluetooth radios

If multiple devices show Code 10 simultaneously, that’s a different problem — often a bus or controller issue rather than per-device drivers. Skip to the “Multiple devices” section below.

Common causes

Ranked by frequency, not by severity:

  1. A Windows update replaced a working driver with a generic one — particularly common with Wi-Fi adapters, audio devices, and some webcams. The Microsoft-supplied generic driver works for most chipsets but fails on specific revisions.
  2. A driver install was interrupted or corrupted — for example, you installed a driver, then unplugged the device, then plugged it back in.
  3. The device was disconnected or reset improperly — common with USB devices on laptops after sleep/wake cycles.
  4. A Fast Startup or hibernation state has the device stuck in an inconsistent power state.
  5. A real hardware failure — the device, the cable, or the port is faulty. Less common but always possible.
  6. Wrong driver version — usually because someone installed the wrong driver (e.g., a Windows 10 driver on Windows 11) or the manufacturer hasn’t certified a current driver for your Windows build.
  7. System file corruption affecting the driver subsystem itself. Rare; usually appears alongside other Windows instability.

Notice “missing or outdated driver” isn’t at the top of this list. It’s there, but it’s not the most common cause. The driver-updater industry exists because they’ve sold the idea that every Code 10 is a missing-driver problem. It isn’t.

Fixes to try first

Try these in order. Stop when the device starts working.

  1. Restart the device. Not the computer — the peripheral itself. For USB devices, unplug, wait ten seconds, plug into a different USB port. For internal devices, you’ll restart the PC at step 4. This eliminates roughly a third of Code 10 cases.
  2. Disable, then re-enable the device in Device Manager. Right-click the device → Disable → wait five seconds → Enable. This forces Windows to re-issue the start request. Works well for devices stuck in an inconsistent power state.
  3. Uninstall the device and reboot. Right-click the device → Uninstall device. Do NOT check “Delete the driver software for this device” unless the next step has already been read. Reboot. Windows will redetect the device and reinstall the driver. For USB peripherals, this fixes a surprising number of Code 10 cases.
  4. Disable Fast Startup and reboot fully. Settings → System → Power → Additional power settings → Choose what the power buttons do → Change settings that are currently unavailable → uncheck “Turn on fast startup.” Reboot. This forces a true cold boot, which clears stuck device states. You can re-enable Fast Startup later if you want.
  5. Run Windows Update. Settings → Windows Update → Check for updates → also click “Advanced options → Optional updates → Driver updates.” Optional driver updates are where Microsoft surfaces hardware-specific drivers that aren’t in the default Windows Update channel. This is the safe, official equivalent of running a driver updater — and unlike the driver-updater apps, it doesn’t bundle anything.

If the device is working at this point, stop here. Don’t continue to the advanced fixes if you don’t need to.

Advanced fixes

If you’re still seeing Code 10:

  • Get the manufacturer’s current driver — directly. Go to the device manufacturer’s support page (Intel, Realtek, Logitech, your laptop OEM’s support site, etc.). Download the current driver for your specific model and Windows version. Install it. Reboot. This is what driver-updater apps claim to do, except they often don’t, and they sometimes install the wrong one. Going direct is more reliable.
  • Roll back the driver. If the device worked before a recent driver update, in Device Manager → Properties → Driver tab → “Roll Back Driver.” Available only if Windows kept the previous version, but it’s the cleanest path when an update is the obvious cause.
  • Check Event Viewer. Windows Logs → System, filter for “kernel-pnp” and “DriverFrameworks” sources. The events around the Code 10 timestamp often contain the actual reason — for example, “device requires more power than the port can supply” tells you the issue is a USB power budget problem, not a driver issue at all.
  • For USB devices, in Device Manager find each “USB Root Hub” entry → Properties → Power Management → uncheck “Allow the computer to turn off this device to save power.” Then reboot. This stops Windows from selectively suspending the hub, which is a frequent cause of Code 10 on USB peripherals.
  • Run DISM and SFC. Only useful if you’ve ruled out per-device causes. Useful when multiple unrelated devices are showing Code 10 — that’s a sign of corruption in the driver subsystem itself.
  • Check for a recent BIOS/UEFI update from the OEM — but install carefully, and only if the OEM specifically mentions device-related fixes in the changelog. Don’t update BIOS hopefully.

Multiple devices showing Code 10

If three or more unrelated devices show Code 10 at the same time, you’re not dealing with a per-device driver problem. Likely causes:

  • A recent Windows feature update broke the driver subsystem. Check Settings → System → Recovery for the option to roll back to the previous version (only available within the rollback window — usually 10 days).
  • The Windows servicing stack is corrupted. Run DISM and SFC and consider a Windows Update component reset if you’re seeing update errors alongside Code 10.
  • A hardware-level issue with a controller — particularly a USB controller. If every USB device is failing, the USB host controller itself is the suspect. That’s diagnosed in Device Manager under “Universal Serial Bus controllers” — if the controllers themselves show errors, this is hardware-side.

If you are on a work or school device

Stop. Most enterprise environments lock driver installation to either Windows Update or an internal driver distribution mechanism (Intune, SCCM, or similar). Installing manufacturer drivers manually can violate device compliance policy and create more problems than it solves.

What to send to IT:

  • A screenshot of the Device Manager entry showing Code 10.
  • The exact device name and any hardware IDs (right-click device → Properties → Details tab → “Hardware Ids” from the dropdown).
  • What changed recently — Windows update, BIOS update, peripheral added.
  • Whether the device worked previously on this machine.

This is enough information for IT to triage without requiring remote access.

When to stop

Stop and escalate if:

  • You’ve tried the “fixes to try first” and at least two advanced fixes without success. At that point you’re looking at either a hardware fault or a driver problem the manufacturer needs to fix.
  • The device shows physical signs of a problem — overheating, a USB cable that wiggles, a port that’s been bent, an external device that doesn’t power on independently.
  • This is happening on multiple identical devices in your environment. That’s a software/policy issue, not a Code 10 issue.
  • A child or someone non-technical needs the device working today and the diagnostic loop is going to take longer than buying a known-good replacement. Sometimes a $25 USB hub is the right answer.
  • You’re tempted to install something called a “driver updater” or “PC fix” tool because you’ve run out of ideas. That’s the moment to step back, not the moment to install something. Nothing in that category solves Code 10.
  • How to Run DISM and SFC Safely — for repairing the driver subsystem when multiple devices fail.
  • Windows Update Error 0x80070643 — sometimes co-occurs with Code 10 when the underlying servicing stack is broken.
  • How to Reset Windows Update Components — useful when Windows Update can’t deliver driver updates either.

Official references

FAQ

Will updating all my drivers fix Code 10? Almost certainly not. Code 10 is one specific device failing to start. Updating unrelated drivers doesn’t help and can introduce new problems. Identify the specific device first.

Are driver updater apps safe to use? The category as a whole is not. Several of the most-advertised driver-updater apps have been flagged by security researchers for bundling unwanted software, exaggerating problems to push users toward paid versions, or installing incorrect drivers. The drivers they “find” are the same ones available free from the manufacturer or through Windows Update. There’s no upside.

Why does the same device work on another PC but not mine? Several possibilities: a different Windows build with different driver compatibility, a different USB controller (especially for USB 2.0 vs 3.0 issues), a different power configuration, or a corrupted driver state on your specific PC. The “uninstall and reboot” fix often resolves this.

Does Code 10 mean the hardware is dead? Not by itself. Most Code 10 cases are software-side. But if you’ve tried every fix above and the device still won’t start, hardware failure becomes the leading hypothesis. Test the device on another computer to confirm.

Why did Code 10 appear after a Windows update? Feature updates and major cumulative updates sometimes replace working drivers with generic Windows-supplied versions, or introduce subsystem changes that incompatible drivers can’t handle. The fix is usually re-installing the manufacturer’s current driver, or — within the rollback window — rolling back the Windows update itself.

Is Code 10 the same as Code 28 or Code 31? No. They’re distinct codes for distinct problems. Code 28 means “drivers for this device are not installed.” Code 31 means “this device is not working properly because Windows cannot load the drivers.” Code 10 means the driver loaded successfully but the device refused to start. The fix paths differ — don’t apply Code 10 fixes to those codes or vice versa.

↑ Back to top