Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix Code 10

Network adapter Code 10: this device cannot start in Device Manager

11 min read Updated October 5, 2026 Networking, Sharing & Printing

Fix it now

Code 10 is CM_PROB_FAILED_START: one of the drivers in the adapter’s stack failed the start request, so Windows gave up on the device. The card is still visible, which means Windows can see the hardware and only the start failed. Before you reinstall anything, read the failure reason the driver left behind, because Code 10 on its own names nothing.

Run these in an elevated PowerShell, substituting the failing adapter’s InstanceId

Get-PnpDevice -Class Net | Format-Table Status,Problem,FriendlyName,InstanceId
Get-PnpDeviceProperty -InstanceId "<paste the InstanceId>" -KeyName DEVPKEY_Device_ProblemStatus
  1. Open the adapter’s properties in Device Manager. If the message is anything other than the generic “This device cannot start”, the driver has supplied its own reason and that reason is the fault to chase.
  2. Uninstall the adapter in Device Manager, tick the option to remove the driver software if it is offered, and reboot.
  3. Install the driver for that exact model from the PC or motherboard maker’s support page, using the machine’s serial or model number rather than a generic chipset package.
  4. Open the adapter’s Power Management tab and clear the option that lets the computer turn the device off to save power, then retest after a sleep and resume rather than only after a cold boot.

If the adapter is onboard, check it is still enabled in the machine’s UEFI setup before spending time on drivers. A disabled onboard NIC usually disappears entirely, but a half-disabled one can fail to start instead.

If Device Manager now reports the adapter working properly and it survives a sleep, you are done. If not, the next section explains what start actually means and which neighbouring code you may really have.

Why it happens

Starting a device is a negotiation between Windows and every driver in that device’s stack. Microsoft’s own description of Code 10 is precise: it is set when one of those drivers fails the start request, and the documentation is candid that where the stack is deep it can be hard to tell which one. That is why the code carries no diagnosis. It marks the stage, not the cause.

There is more information available than most people use. If the device’s hardware key holds a FailReasonString value, Device Manager shows that string instead of the generic wording, so a driver that knows why it failed can tell you directly. Beyond that, the DEVPKEY_Device_ProblemStatus property on the device holds the failure code the start request returned. Reading those two before touching anything turns a guess into a diagnosis.

The neighbouring codes mark different stages, and they do not respond to the same treatment. Code 31 is CM_PROB_FAILED_ADD – Windows could not load the drivers required for the device at all, which is a driver store or filter problem rather than a hardware one. Code 1 is CM_PROB_NOT_CONFIGURED, an incomplete or interrupted installation. Code 56 is CM_PROB_NEED_CLASS_CONFIG, and it is a different animal entirely: Windows is still setting up the class configuration for the device, a state Microsoft describes as frequently transient.

The driver is wrong for this hardware revision

You have this one if The adapter works with one driver and fails with the other, or the failure appeared the day a Windows update replaced a working vendor driver.

  1. Identify the hardware exactly: adapter properties, Details tab, Hardware Ids.
  2. Download the matching driver from the machine vendor’s support page using the serial or model number.
  3. Uninstall the current driver with the remove-software option, reboot, then install the downloaded package.
  4. If the failure began immediately after a driver update, Roll Back Driver on the Driver tab is quicker and puts the machine back to a state you know worked.

Windows is still configuring the network class

You have this one if Code 56 rather than Code 10, often on a machine where VPN or security software was installed, upgraded or partly removed.

  1. Wait, and reboot once. Microsoft describes this problem code as frequently transient: the device restarts itself once class configuration completes.
  2. If it persists on a network adapter, Microsoft’s documented remedy is to reset the system’s network state with the Network reset button in Settings.
  3. Expect to re-enter Wi-Fi credentials and VPN client configuration afterwards; a network reset removes and reinstalls the adapters.
  4. If it still persists, the driver INF itself may carry invalid networking directives, which is a matter for the driver’s publisher.

This is the cause most often treated as a Code 10, and the treatments are opposite. Reinstalling the adapter driver on a Code 56 usually leaves it exactly where it was.

The adapter is stuck in a power state

You have this one if It fails after a resume or a shutdown, and comes back after a full restart or after mains power has been removed.

  1. Clear the power management option on the adapter that lets Windows turn it off.
  2. Turn off fast startup in Power Options, so that a shutdown is a real shutdown.
  3. Shut down fully, remove power for a minute on a desktop or hold the power button on a laptop, then start again.
  4. Apply the machine’s current UEFI firmware, which frequently corrects power-state handling for onboard adapters.

Stale bindings left by software that is no longer installed

You have this one if Every adapter fails at once, including virtual ones, and reinstalling drivers changes nothing.

  1. List what is bound to each adapter: Get-NetAdapterBinding -Name * | Sort-Object Name,DisplayName.
  2. Disable or remove bindings belonging to VPN or security products that are no longer on the machine, using that product’s own removal tool where one exists.
  3. In Device Manager, choose View then Show hidden devices and remove leftover virtual adapters for software that has gone.
  4. Reinstall the physical adapter’s driver last, once the stack is clean.

The hardware or its connection has genuinely failed

You have this one if The adapter disappears intermittently, or a card in a slot fails while a USB adapter in the same machine works perfectly.

  1. Reseat the card or the internal cable; on a laptop, reseat the module if it is accessible.
  2. Try a different slot, or the machine’s second network port if it has one.
  3. Test with an inexpensive USB adapter to confirm the rest of the machine is healthy.
  4. Replace the adapter if it is a serviceable part. A dead NIC in an otherwise good machine is a legitimate outcome, not a defeat.

Full reference

The four codes this article covers, as Microsoft states them

Code Constant Message Device Manager shows
Code 10 CM_PROB_FAILED_START This device cannot start. Try upgrading the device drivers for this device – unless the driver supplied its own FailReasonString
Code 31 CM_PROB_FAILED_ADD This device is not working properly because Windows cannot load the drivers required for this device
Code 56 CM_PROB_NEED_CLASS_CONFIG Windows is still setting up the class configuration for this device
Code 1 CM_PROB_NOT_CONFIGURED This device is not configured correctly

Reading the reason instead of guessing at it

  1. In Device Manager, open the adapter and read the Device status box. Wording other than the generic sentence means the driver wrote a FailReasonString into the device’s hardware key.
  2. Get the instance path: Get-PnpDevice -Class Net | Format-Table Status,Problem,FriendlyName,InstanceId.
  3. Read the start failure: Get-PnpDeviceProperty -InstanceId "<path>" -KeyName DEVPKEY_Device_ProblemStatus. Microsoft names this property as the place the start IRP’s failure code is recorded.
  4. Check the Setup logs under C:\Windows\INF\setupapi.dev.log for the driver installation that preceded the failure.

The network class key, and why to leave it alone

Adapter bindings and class configuration live under the Net device setup class, whose GUID Microsoft publishes as 4d36e972-e325-11ce-bfc1-08002be10318. You will find advice to edit the UpperFilters and LowerFilters values under that class key by hand. It sometimes works, and it is also the fastest way to leave a machine with no working network adapters at all. Prefer Get-NetAdapterBinding, the vendor’s own removal tool, and the Network reset button, all of which do the same job through supported paths.

If you do edit the class key, export HKLM\SYSTEM\CurrentControlSet\Control\Class\{4d36e972-e325-11ce-bfc1-08002be10318} first, and remove individual filter entries rather than the key. Deleting the key removes every network adapter on the machine.

Resetting the stack, and what it costs

netsh int ip reset is supported and documented, and it is heavier than it looks. Microsoft describes it as having the same effect as removing and reinstalling TCP/IP: it overwrites SYSTEM\CurrentControlSet\Services\Tcpip\Parameters and SYSTEM\CurrentControlSet\Services\DHCP\Parameters, and it needs a restart. Static addresses, gateways and DNS servers are among the values it rewrites, so write them down first. Passing a file name – netsh int ip reset c:\resetlog.txt – gives you a record of everything it changed.

Command What it does
Get-PnpDevice -Class Net Lists every network device with its status and problem code
Get-NetAdapter Shows the adapters Windows considers usable, with link speed and status
Get-NetAdapterBinding -Name * Lists what is bound to each adapter, which is where stale components show up
netsh int ip reset c:\resetlog.txt Rewrites the TCP/IP and DHCP parameter keys and logs every change; needs a restart
ipconfig /all Confirms which adapter is actually carrying traffic before you troubleshoot the wrong one

When it is not the adapter at all

  • Check which adapter holds the address. A machine with working Wi-Fi and a failed wired port looks online, and people spend an afternoon on the wrong device.
  • Check the Setup and System logs for the moment the code appeared. A driver installed by Windows Update at that timestamp is a strong lead.
  • On a virtual machine, check the hypervisor side. A synthetic adapter that fails to start is often a host or integration-services problem rather than a guest one.
  • On a docking station, test the adapter with the dock removed. Dock firmware is a common source of adapters that start once and never again.

Every code this article covers

Code What it points at Source
Code 10 CM_PROB_FAILED_START: one of the drivers in the device’s stack failed the start request Microsoft Learn
Code 31 CM_PROB_FAILED_ADD: Windows cannot load the drivers required for this device Microsoft Learn
Code 56 CM_PROB_NEED_CLASS_CONFIG: Windows is still setting up the class configuration for the device; often transient, and on a network adapter the documented remedy is a network reset Microsoft Learn
Code 1 CM_PROB_NOT_CONFIGURED: the device is not configured correctly Microsoft Learn

Confirm the fix worked

  1. Device Manager shows the adapter with no warning marker and reports that it is working properly.
  2. Get-PnpDevice -Class Net reports Status OK and no problem code for that adapter.
  3. Get-NetAdapter shows the adapter Up with a sensible link speed, and ipconfig /all shows an address, gateway and DNS servers on it.
  4. Sleep and resume the machine, then confirm the adapter returns without anyone touching it.
  5. Reboot once more and confirm the state holds, so you know you fixed it rather than started it by hand.

Questions people ask about this

Is there anything to buy to fix Code 10?

No software licence. Drivers from your hardware vendor are free and every tool used here ships with Windows. The only money involved is a replacement adapter where the hardware has genuinely failed.

Why did it start after a Windows update?

Usually because the update replaced a vendor driver with a generic one, or changed the order in which the stack loads. Reinstalling the vendor driver after the update normally settles it; if Windows keeps replacing it, check whether the vendor publishes a driver for the build you are now on.

Should I use Roll Back Driver?

Yes, if the failure began immediately after a driver update and the button is available. It is faster than hunting for the previous package and it returns the machine to a state you know worked.

Device Manager shows a warning but the internet works. How?

Another adapter is carrying the traffic – wireless while the wired port fails, or a USB adapter. Run ipconfig /all and find which adapter holds the address before you spend time on the other one.

What is the difference between Code 10 and Code 56 in practice?

Code 10 means a start attempt failed and usually needs the driver replaced. Code 56 means class configuration has not finished; Microsoft calls it frequently transient and, for network adapters, points at a network reset rather than at the driver. Treating a 56 like a 10 is the most common wasted afternoon on this error.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

License Error Wi-Fi adapter Code 43 or Code 45: the device stopped or is not present Free Fix Error 0x80070052: the directory or file cannot be created on a share License Error Error 0x80072746: endpoint security resets SMB, print and RDP connections Free Fix Remote Desktop error 0x108: your session ended because of a network error
โ† Back to Knowledge Base