ERROR-A / Search

Start with a symptom, message or error code.

Explore
Menu
Error code
10

Code 10 means the device could not start. Additional manufacturer text may narrow the condition: keep the entire message, not just the number. A USB peripheral, network adapter and storage controller need different tests and precautions; the code does not establish physical failure.

Windows Device Manager Code 10

Identify the device that cannot start and check its specific driver, keeping Code 10 separate from Code 43.

Try this first

1 quick checks · ~3 min

  1. Read the complete statusRead the message and choose the appropriate test.

Find your situation

See all the clues. Choose the one that matches what you observe.

Detachable USB peripheral

Compare a port and another compatible computer before changing Windows.

Started after a driver change

Check the version and consider returning to the previous one.

Internal device, network, audio or storage

Choose model documentation and preserve access to the PC.

Diagnostic signals

ObservationAdditional manufacturer status
Text such as STATUS_DEVICE_POWER_FAILURE guides adapter-specific support; it neither authorizes opening the PC nor proves an electrical failure.
ObservationWorks on another computer
Points toward the original port, driver or platform. Failure on two compatible systems directs you to the manufacturer rather than repeated reinstalls.

Step-by-step solutions

01

Read the complete status

  • Estimated time: 3 min
  • Easy
  • Low risk

Read the message and choose the appropriate test.

  1. In Device Manager, open Properties > General for the device with a warning. Record its name, code, additional message and, under Driver, provider and version.

  2. Identify whether it is external USB or internal and what changed before failure. If it now shows 31 or 43, use the exact related guide: reinstalling for the old code loses that information.

Sources:
02

Safely isolate a USB peripheral

  • Estimated time: 10 min
  • Easy
  • Low risk

  1. Only for a detachable peripheral that is not needed to boot: close its activity, safely eject storage where applicable and try a direct connection to another compatible port without a hub. Use another suitable data cable if detachable. Do not disconnect drives during writes.

  2. If it starts, investigate the original connection path; do not change all USB drivers. If it persists, test on another compatible, authorized computer. If it works there, focus on the original PC’s driver and platform; if it fails there too, stop reinstalling and give the manufacturer both results.

Sources:
03

Evaluate the recent change

  • Estimated time: 15 min
  • Easy
  • Low risk
  • Administrator required
  • Restart required

  1. Compare when failure started with the driver installation, not just the package’s printed date. If it worked before that version changed, use Properties > Driver > Roll Back Driver when available and authorized.

  2. Save work and restart if prompted. If it starts on the previous version, report the regression to the manufacturer; do not immediately reinstall the failing version. If the button is unavailable, do not force similar packages: ask the OEM for a compatible version. If unchanged, continue by device class.

Sources:
04

Choose support by device class

  • Estimated time: 5 min
  • Easy
  • Low risk

  1. For integrated laptop network or audio, look for the exact model’s OEM package: it may include system-specific adaptations. For an added PCI/PCIe card, consult its manufacturer and compatibility with that motherboard and Windows. Do not turn the USB comparison into casual removal of internal cards.

  2. For Intel Wi-Fi/Bluetooth, compare the complete message with its specific guide and start with the OEM package. For storage, identify whether it controls the boot drive; if unsure, do not uninstall it or change BIOS storage mode. For audio or networking, failure of one function does not establish that the whole board is faulty.

  3. If the manufacturer offers a compatible correction for that state, prepare the package and recovery before installing it. If model, Windows and package do not clearly match, request assistance instead of trying several at random.

Sources:
Next step

Still not working?

If Code 10 persists with the correct package, give the manufacturer the full message, model, versions and USB comparison where applicable. Without a safe way to recover input, network or boot access, stop before removing the device. Do not use third-party driver updaters or registry deletions.

Sources

Documentation behind this guide. Editorial recommendations are identified separately.

Source review: . A documentation review, not a physical hardware test.

Related problems

windows
Error code

Windows Code 43 error

Windows stopped a device after a driver reported a problem. Code 43 describes that state, not a specific failed part, and can affect different device classes.

View solution
windows
Error message

USB device not recognized in Windows

Windows displays a USB device recognition warning. Start with the connection and read device status: the warning does not automatically mean Code 43 or a drive that needs formatting.

View solution
windows
Error code

Device Manager Code 31

Windows cannot load the drivers the device needs. Check for an appropriate update before removing it from the system.

View solution