You connect a USB device through a USB-C hub.

Windows detects it.

The device appears in Device Manager.

But instead of working normally, Device status shows:

This device cannot start. (Code 10)

The device might be a:

• USB audio interface;
• printer;
• webcam;
• external storage controller;
• network adapter;
• serial adapter;
• specialized USB accessory.

This error is easy to confuse with other USB failures, but Code 10 has a specific meaning.

Microsoft defines Code 10 as CM_PROB_FAILED_START: Windows created the device stack, but one of the drivers in that stack failed the request to start the device.

That gives us the most important rule:

Code 10 usually means Windows got far enough to recognize and configure a device, but the device or its driver stack could not complete startup.

That is different from Windows failing to identify the USB device in the first place.

Quick Answer

If a USB device shows Code 10 only when connected through a USB-C hub:

1. Check whether the same device starts when connected directly.
2. Disconnect other hub peripherals and retest.
3. Update or reinstall only the affected device driver.
4. Check chipset, USB, Thunderbolt, or USB4 drivers from the laptop manufacturer.
5. Try another data port on the hub.
6. Test another host USB-C port.
7. Only suspect the hub itself after the device works normally on the same computer without it.

Do not start by uninstalling every USB controller.

Hypothesis 1: The Device Cannot Start Anywhere

Start with the simplest possibility:

The hub may not be the real cause.

Connect the same device directly to the laptop when possible.

Then check:

Device Manager → Device → Properties → General

Code 10 appears directly too

Focus on:

• device driver;
• device firmware;
• Windows update;
• chipset/USB driver;
• the USB device itself.

The USB-C hub was removed from the path, so replacing the hub is unlikely to solve the underlying startup failure.

Device starts normally directly

Now the investigation changes.

You have proved that:

Windows + Device + Driver

can work.

The Code 10 appears only after the additional USB hub path is introduced.

Move to the next hypothesis.

Hypothesis 2: The Hub Path Changes How the Device Starts

A USB hub changes the topology between the peripheral and Windows.

Instead of:

USB Device → Host Controller

you now have:

USB Device → USB-C Hub → Host Controller

That does not automatically cause a problem, but it adds another controller and another connection layer to the startup path.

Simplify the setup.

Disconnect:

• SSDs;
• webcams;
• phones;
• printers;
• audio interfaces;
• other USB peripherals.

Leave only:

Laptop → Hub → Code 10 Device

Then restart the device connection.

Code 10 disappears

Another connected device, total power load, or the combined USB configuration may have contributed to the startup failure.

Code 10 remains

Try another genuine USB data port on the hub.

Also try another USB-C port on the laptop if available.

If the device works through one port but repeatedly shows Code 10 through another, you now have a connection-path clue rather than a generic Windows driver problem.

Hypothesis 3: Windows Loaded the Device but the Driver Stack Is Stale

This is where Code 10 differs from a basic USB detection error.

Microsoft's technical documentation states that Code 10 is set when a driver in the device stack fails the start request.

So check:

Device Manager → Device → Properties → Driver

Record:

• Driver Provider
• Driver Date
• Driver Version

Then use Microsoft's recommended first step:

update the affected device driver

Do not install random third-party “driver updater” software.

Use:

Windows Update

or:

the device manufacturer's official driver

or:

the laptop manufacturer's chipset / USB driver package.

Microsoft also recommends obtaining Windows hardware drivers through Windows Update or the hardware manufacturer's official source.

Rebuild Only the Failed Device

If updating does not help, reinstall the affected device instead of deleting the entire USB stack.

Use:

Device Manager → affected device → Uninstall device

Then disconnect the device.

Restart Windows.

Reconnect it and let Windows create a fresh device instance.

Microsoft documents this Device Manager uninstall/reinstall workflow and specifically cautions that a connected device can be immediately rediscovered if it is not physically disconnected first.

That means the cleaner sequence is:

Disconnect device

→ Uninstall device

→ Restart Windows

→ Reconnect

Avoid starting with:

Uninstall every USB Root Hub

or:

Remove every xHCI controller

because that can temporarily disable other USB devices and makes it harder to identify which change actually fixed Code 10.

Hypothesis 4: The Device Starts Alone but Fails Under Hub Load

Now reconnect the device through the hub with everything else removed.

If it starts correctly, add peripherals gradually.

For example:

Code 10 Device

→ Keyboard

→ Mouse

→ SSD

→ Webcam

→ Charging

If Code 10 returns only after another device is added, investigate:

• peripheral power demand;
• shared hub resources;
• host USB controller stability;
• charger and PD setup.

This does not mean Code 10 is simply a “not enough power” error.

It means the failure correlates with the more complex hub configuration.

If several devices begin disconnecting together rather than only one showing Code 10, use the separate LENTION guide on multiple USB-C hub devices disconnecting under combined load.

What If Code 10 Started After Windows Update?

The timing matters.

If the device worked normally before:

• Windows Update;
• chipset driver update;
• USB4 update;
• Thunderbolt update;
• device driver update;

check:

Device Manager → Device → Driver

and see whether:

Roll Back Driver

is available.

You should also check the laptop manufacturer's official support page for:

chipset

USB controller

Thunderbolt / USB4

and:

BIOS / UEFI

updates.

A USB device can use its own driver while still depending on the host controller and chipset underneath it.

So repeatedly reinstalling only the accessory driver may not resolve a host-side startup problem.

Code 10 Is Not the Same as Code 43

These two errors should not target the same search intent.

Code 10

This device cannot start.

Windows has created the device stack, but startup failed.

Code 43

Windows has stopped this device because it has reported problems.

This commonly appears with failures such as:

Unknown USB Device (Device Descriptor Request Failed).

If that is what Device Manager shows, use the LENTION guide for Device Descriptor Request Failed and USB Code 43 instead.

The practical distinction is:

Code 10 = device startup failure

Code 43 / Descriptor Request Failed = different USB recognition or device-reported failure path

Keeping these articles separate is important for SEO because users often search the exact Windows error code.

Code 10 Is Also Not “Device Not Migrated”

Another nearby Windows message is:

Device not migrated

This normally appears under:

Properties → Events

and relates to device configuration or migration history.

Code 10 is different because it appears as a current Device status problem.

If your device instead shows a migration event, use the LENTION guide explaining Windows Device Not Migrated errors through a USB-C hub.

This distinction also makes the LENTION Windows USB error cluster cleaner:

Device Not Migrated

→ migration/configuration history

Code 10

→ failed device start

Code 43

→ device/USB recognition failure

When a Simpler USB Path Helps

Changing the hub does not directly repair a Windows Code 10 driver failure.

But hardware can be useful as a controlled comparison path.

For common USB-A peripherals, a USB-C hub with four USB 3.0 data ports and separate PD input provides a straightforward USB layout.

The LENTION CB-C31 provides four USB 3.0 ports up to 5Gbps and up to 60W PD pass-through, with additional power available to connected peripherals when compatible PD power is present. Its current product page is actively listed for sale.

For USB-C peripherals, a USB-C hub with four USB 3.2 Gen 2 10Gbps data ports provides a similarly clear USB-C data layout.

The LENTION CE31s offers four USB-C data ports rated up to 10Gbps plus a separate PD input supporting up to 100W pass-through.

Neither product should be described as:

“fixing Code 10.”

Their value in this article is to provide a clear, predictable USB data path when isolating whether a problem follows:

the device

or:

the current hub topology.

Read the Result, Not Just the Error Code

If the entire USB-C hub is missing rather than one accessory showing Code 10, switch to the broader USB-C hub not recognized troubleshooting guide.

Quick Answers

What does “This device cannot start. (Code 10)” mean?

Microsoft defines Code 10 as a device start failure. One of the drivers in the device stack failed the request required to start the device.

Does Code 10 mean my USB-C hub is broken?

No. If the device also shows Code 10 when connected directly, focus first on the device, driver, Windows, or host controller.

Why does the device work directly but show Code 10 through the hub?

The additional hub changes the USB connection path. Test another hub data port, remove other peripherals, and verify the host USB-C connection.

Should I reinstall all USB drivers?

No. Start with the affected device. Reinstalling every USB controller can make troubleshooting harder.

Can insufficient power cause Code 10?

Power instability can contribute to device-start problems in some configurations, but Code 10 itself is not simply a “low power” code.

Final Takeaway

When Windows shows:

This device cannot start. (Code 10)

after connecting a device through a USB-C hub, do not treat it as a generic “USB device not recognized” error.

Test four hypotheses:

Can the device start directly?

Does the error appear only through the hub?

Can the specific driver stack be rebuilt or updated?

Does the failure appear only when the hub is under a heavier device load?

The most important rule is:

Code 10 means Windows created the device stack but the device failed to complete startup.

If the device fails everywhere, investigate the device and driver.

If it works directly but fails only behind the hub, investigate the added USB path.

And if Windows shows Code 43 or Device Not Migrated instead, use the troubleshooting workflow for that exact error rather than treating all Device Manager messages as the same problem.