Device Manager Code 10: Fix a Device That Won't Start

Device Manager Code 10 means Windows couldn't start the affected device. Start with a restart and connection checks, then work through approved updates, driver changes, and device reinstallation.

The message alone doesn't identify the underlying fault, so change one thing at a time and test afterward. On a business PC, involve IT before a change could interrupt network access, storage, or another employee's work.

First, identify the device and establish a consistent way to test it.

Key Takeaways

  • Record the device name, full error message, and driver version before changing anything.
  • After each repair attempt, inspect Device Manager and test the device's normal business function.
  • Keep driver changes within your company's approval process, especially on remotely supported computers.

Find the Affected Device and Record Its Status

The same Device Manager controls are available in Windows 10 and Windows 11. Start here rather than changing settings across several devices.

Locate the Device Showing Code 10

Right-click Start , select Device Manager , and expand the relevant category. Network adapters, Bluetooth, and Sound, video and game controllers are common places to look, depending on what stopped working.

Look for a warning symbol beside a device. Right-click that entry, choose Properties , and read Device status on the General tab. The message typically includes "This device cannot start. (Code 10)."

Record the exact device name and complete message. Under the Driver tab, also note the provider, date, and version. If several similar entries appear, ask IT to identify the correct one before proceeding.

Establish a Repeatable Success Test

After every troubleshooting step, reopen the device's properties. A successful result should replace Code 10 with "This device is working properly" and remove the warning symbol.

Then test the task that failed. For a network adapter, test the required business connection. For audio hardware, play sound through the intended output.

If a camera or microphone has a normal device status but still fails in Teams, follow our camera and microphone troubleshooting guidance. Application permissions and device selection need separate attention.

Restart the Device and Check Its Connections

Save your work before restarting anything. Also tell IT if the affected device provides your remote support connection.

Restart the PC and External Equipment

Select Start > Power > Restart . Use Restart rather than repeatedly closing the lid or signing out, because those actions don't restart Windows.

Once you're signed back in, inspect Device Manager and repeat your functional test. Record whether the error disappeared, stayed unchanged, or returned after use.

For an external device, follow its normal shutdown procedure, disconnect it when safe, and reconnect it. Don't unplug storage during a transfer. If the device has its own power supply, restart it according to the manufacturer's instructions.

Keep the PC connected to power throughout maintenance.

Inspect the Cable, Port, and Power Supply

Seat connections firmly and inspect cables for visible damage. For a USB device, try a compatible port directly on the PC instead of routing through a hub or dock, when practical.

Use a known-good compatible data cable if one is available. Some USB cables provide charging without the data connection a peripheral needs. Use only a correctly rated power adapter intended for the equipment.

After each change, check the device status and test again. Note which port and cable you used so IT can reproduce the result.

Don't open a laptop or reseat internal components as an employee-level troubleshooting step.

Review Windows Updates Before Changing Drivers

Open Start, search for Check for updates , and open the matching Settings page. Note any pending restart, incomplete installation, or failed update before proceeding.

On a managed business PC, let IT handle approved updates through the company's patching process. Don't bypass management settings or install every optional update simply because Device Manager shows Code 10.

After an approved installation finishes, restart if requested. Then reopen the affected device's properties and repeat its functional test.

Also compare the first failure with recent changes. Record new applications, connected peripherals, and driver installations, along with Windows updates. Timing gives IT a useful lead, but it doesn't establish that an update caused the problem.

If several coworkers report the same failure, include their device names in the support ticket. IT can compare affected and unaffected machines before changing a wider deployment.

Roll Back or Update the Affected Driver

These steps require approval and may require administrator access. Before changing a network adapter, arrange another way for IT to reach the computer.

Roll Back When the Previous Driver Is Relevant

If the device stopped working after a driver change, open its Properties > Driver tab and select Roll Back Driver , if available. Follow the prompts and restart if Windows requests it.

A grayed-out button means that rollback isn't available through that control. Don't try to recreate it by deleting driver files or removing unrelated software.

Afterward, compare the displayed driver version with your original record. Check Device status, then test the device under normal working conditions.

Record the result even if the error remains. That helps IT avoid repeating an unsuccessful change and preserves the sequence of troubleshooting.

Use an Approved Driver Update

If rollback isn't appropriate, IT can evaluate an approved driver update. In Device Manager, right-click the affected device and select Update driver > Search automatically for drivers .

Windows may report that the best available driver is already installed. That message doesn't establish that the device is functioning correctly; the status message and practical test still matter.

For specialty business equipment, preserve required features when choosing a driver. Our printer troubleshooting checklist explains why generic printer drivers can omit tray, scanning, or accounting functions.

After an authorized update, restart when requested and repeat the same checks.

Uninstall and Reinstall the Device Carefully

Device removal is a more disruptive step, so prepare before selecting it. IT should arrange a recovery path if the affected device handles networking, storage, display output, or essential input.

For a suitable peripheral, an authorized administrator can right-click its Device Manager entry and select Uninstall device . Read the confirmation dialog carefully.

If Windows offers an option to remove or delete the driver package, leave that option unselected unless IT has planned the replacement. Removing the device entry and removing its driver package are separate actions.

After uninstalling, restart the PC. Windows will attempt to detect and reinstall the device. For an external peripheral, reconnect it when appropriate. Device Manager also provides Action > Scan for hardware changes to request another hardware scan.

Next, find the device again and open its properties. Confirm that the expected entry has returned, then inspect its status and test its function.

A device that disappears from Device Manager hasn't passed the repair test. It must return, start successfully, and perform its intended task.

If Windows can't restore it, stop repeated removal attempts and hand the results to IT.

Investigate Repeat Failures Before Advanced Repairs

When Code 10 returns, preserve the evidence instead of cycling through the same changes. Repeated restarts and unrelated driver changes make the sequence harder to interpret.

Collect Device Events and Related History

Open the device's Properties > Events tab and record entries around the failure. Include complete messages and timestamps rather than a cropped error label.

Also note whether the problem follows docking, waking from sleep, or connecting particular equipment. Those observations help IT choose a test without assuming a cause.

If the PC also crashes or restarts unexpectedly, use our guide to Windows Reliability Monitor to organize the history. Keep application failures, full restarts, and device warnings distinct, even when they happen on the same day.

Protect the PC Before Deeper Work

System-file repairs, firmware changes, and operating system recovery belong with an authorized administrator. DISM repairs the Windows component store; System File Checker examines protected system files. Neither tool replaces testing the affected device afterward.

Before major work, protect business files and arrange access to the BitLocker recovery key if recovery requires it. Don't disable encryption, security software, or management controls to pursue an unapproved workaround.

Our business computer repair services can help diagnose persistent device problems. Provide the device name, driver version, business impact, and results of each attempted fix.

Frequently Asked Questions About Code 10

Does Code 10 Mean the Hardware Is Broken?

Code 10 alone doesn't establish that the hardware has failed. It reports that Windows couldn't start the device.

IT can compare its behavior using compatible connections or another approved computer, where practical. The result helps guide the diagnosis, but the code by itself doesn't justify replacing equipment.

Can I Keep Working While the Error Is Present?

That depends on the affected device. An unused peripheral may leave other work unaffected, while a failed network adapter can interrupt essential access.

Report storage warnings, repeated crashes, or lost connectivity promptly. Use an approved replacement or alternate workstation when the failure blocks a business-critical task.

How Do I Know the Repair Lasted?

Confirm normal device status, complete the original task, and repeat the test after a restart. If the problem previously appeared after sleep or docking, test that sequence too.

Document any recurrence rather than treating a single successful connection as the final result.

Return the Device to Dependable Service

A useful Code 10 repair ends with verified device operation , not merely a completed installer or successful sign-in. Keep the original error, each change, and the final test result in the support record.

Start with the least disruptive checks and stop once the device works consistently. If the warning persists, give IT that record before making deeper changes. A clear handoff supports the next repair decision and reduces repeated work.

ASK AN IT PRO