If Device Manager hangs on “Scanning for hardware changes,” try unplugging external peripherals first, then retry. If it still hangs, a common cause may be a driver lookup failure or a broken Plug and Play service path. Leaving it stuck can block new hardware detection and send you toward the wrong fix. Device Manager is Windows’ hardware management tool, and it stalls here while it enumerates Plug and Play devices, assigns resources, and checks driver paths.

Device enumeration

Device enumeration table
A Windows Device Manager window shows highlighted hardware entries

Use the checks below to separate a one-device problem from a Windows path problem.

  • If the scan starts as soon as a USB hub is attached, unplug the hub, then reopen Device Manager. Add devices back one at a time.
  • If a Bluetooth icon or adapter was added recently, remove the Bluetooth adapter or disable it in Device Manager. Then update or roll back that adapter’s driver.
  • If the hang began after installing a driver, restart, then open Device Manager again. Roll back the driver or uninstall the device.
  • If a docking station is connected, disconnect it from the laptop. Test on the laptop alone, then update dock firmware and its chipset driver if the dock is the trigger.
  • If no external devices are connected yet the scan still hangs, restart Windows, then retry. If needed, check the Plug and Play service path.
  • If a PCI card was added or replaced, power off, reseat the card, then retest. Update the chipset and card driver.
  • If only one laptop port causes the hang, move the device to another port. Replace the cable or the device if the problem follows it.
  • If the scan is slow only after Windows Update ran, pause new device changes and wait briefly. Check whether the device already has a signed driver installed.

What the stuck scan means

What the stuck scan means
A hand plugs an Ethernet cable into a desktop computer port

Plug and Play searches locally first and then Windows Update if needed. It can also load and unload drivers dynamically, which means one bad device path can make the whole scan wait on a result that never arrives.

The fastest first move is simple: unplug external hardware, then use Action > Scan for hardware changes again after a Restart.

Likely causes

One external peripheral is blocking enumeration

A bad USB device, hub, dock, or adapter can keep Device Manager busy while Windows tries to read it. USB and PCI buses take full advantage of Plug and Play, so a single weak link on either path can stall the scan.

  1. Unplug every nonessential USB device, including hubs, flash drives, printers, external drives, and adapters.
  2. If you use a docking station, disconnect it from the laptop.
  3. Open Device Manager again and choose Action > Scan for hardware changes.
  4. If the scan clears, reconnect only one downstream device at a time.

A driver lookup is failing or looping

When Windows cannot finish a local driver search, it may fall back to Windows Update. That path is normal, but a damaged or mismatched driver can keep the install loop going instead of finishing cleanly.

  1. In Device Manager, right-click the device that changed most recently.
  2. Select Properties > Driver.
  3. Choose Roll Back Driver if the option is available.
  4. If rollback is unavailable, choose Uninstall device, then restart Windows and reconnect the device.

Say your USB audio interface works until a new driver is installed, then Device Manager hangs when you scan for changes. That points to the driver path, not the cable. Rolling back or reinstalling the device is the safer next step than removing unrelated hardware.

Windows Update or the driver store is slow to respond

Windows Update can be part of the device installation flow when local search does not find a match. Drivers obtained through this path are WHQL signed, which matters for trust and compatibility, but the lookup can still take time if the catalog or driver store is busy. (Microsoft)

  1. Open Settings > Windows Update and check for updates.
  2. Install any pending updates, then restart.
  3. Return to Device Manager and scan again.
  4. If the device still lacks a working driver, get the package from the OEM or chipset vendor site and install it manually.

A dock, hub, or bus-connected device is reporting bad state

USB and PCI devices are common triggers because they depend on automatic detection and resource assignment. A dock can expose several internal devices at once, so one bad component can make the whole chain look stuck.

  1. Disconnect the dock or hub entirely.
  2. Test with only the built-in keyboard, touchpad, and display.
  3. If the hang clears, reconnect devices one at a time until the offender returns.
  4. Update the dock firmware or chipset driver only after the bad branch is identified.

Suppose a desktop with a PCI Wi-Fi card hangs during scanning only after a new graphics driver is added. That does not mean the video card is bad. It means the new driver or the PCI device path needs a closer look before anything else is removed.

Device Manager scan triage

Use the checks below to match the symptom to the next safe step.

  • If it only happens with a USB hub attached, remove the hub and test each downstream device separately.
  • If it only happens with Bluetooth enabled, disable the adapter and update or roll back that driver.
  • If it started after a driver install, restart Windows and then roll back or uninstall that device.
  • If it only happens on a docked laptop, undock and retest, then update the dock and chipset drivers if needed.
  • If it only happens on one front-panel USB port, move to another port and replace the cable or device if the problem follows it.
  • If no external devices are attached at all, restart Windows and then check the Plug and Play service.
  • If a new PCI card was installed, reseat the card after shutdown and then install the vendor driver.
  • If the scan is slow after updates, wait briefly, then check Device Manager again and install the device driver from the OEM if needed.

Is a USB device causing the hang?

Yes, a USB device can absolutely make the scan hang. A bad hub, flash drive, printer, or cable can interrupt enumeration before Windows finishes naming the device or loading its driver. The cleanest test is to remove all external USB hardware and retry from the bare system.

  1. Save your work.
  2. Unplug every USB peripheral except input devices you need to keep control of the PC.
  3. Open Device Manager and choose Action > Scan for hardware changes.
  4. If the hang clears, reconnect devices one at a time until the offender returns.
  5. If the same device always triggers the hang, uninstall it from Device Manager > (device) > Properties > Driver and reinstall the vendor driver.

Could a dock or Bluetooth adapter be the problem?

Yes. A dock can present multiple internal USB, audio, network, and storage paths at once, and a Bluetooth radio sits on a bus path that Plug and Play must enumerate. If either one reports a bad state, the scan can pause while Windows waits on that branch.

  1. Disconnect the dock from the laptop.
  2. In Device Manager, expand Bluetooth and disable the adapter if the hang appears after pairing changes.
  3. Restart Windows, then rescan.
  4. Reattach only the dock or only the Bluetooth adapter, not both at once.
  5. If one item is the trigger, update its driver from the manufacturer site instead of reinstalling everything else.

Does Device Manager need admin rights?

Yes. Device installation wizards typically need administrator privileges, and membership in the Administrators group is a common way to allow a wizard to search Windows Update for drivers. A standard account can open Device Manager, but driver installation and some changes may stop short without elevation.

  1. Sign in with an administrator account, or approve the prompt with admin credentials.
  2. Open Device Manager with Win+X > Device Manager.
  3. Right-click the device and select Update driver.
  4. Choose the automatic search option if you want Windows to check local sources and then Windows Update.

Hardware wizards are part of the normal Windows device installation path. They can search Windows Update for device drivers when a local match is missing, and that lookup is one reason the scan can appear to hang on a slow or stubborn device branch.

Why Windows Update and drivers matter

Windows Update is the fallback driver source when local search fails. That matters because Plug and Play searches locally first, then goes to Windows Update if necessary, while also assigning hardware resources and loading drivers dynamically. WHQL-signed drivers from Windows Update are part of the trust chain during setup.

  1. Open Settings > Windows Update and install pending updates.
  2. Return to Device Manager > (device) > Properties > Driver.
  3. Use Update driver if Windows has a newer package.
  4. If Windows has none, download the driver directly from the OEM or chipset vendor site and install it manually.

Win+X > Device Manager > (device) > right-click > Properties > Driver tab
Actions: Update driver, Roll Back Driver, Uninstall device
View > Show hidden devices

Hidden or duplicate devices are not all safe to remove. Leave gray entries alone unless they match hardware that is gone for good, such as an old dock, a removed Bluetooth adapter, or a device that no longer exists. Keep the active entry for the device you still use.

Still not working?

Still not working?
A Windows Device Manager window is open with USB devices listed

If the quick checks fail, move to the service path and the last known bad device. The right next step is usually a restart, then a targeted driver rollback or removal of the most recently added peripheral. A full shutdown is not always the first choice here because Fast Startup can keep part of the old hardware state around.

  1. Restart Windows, then try Device Manager again.
  2. Open services.msc and confirm Plug and Play is running.
  3. If the scan still hangs, remove the last device or driver you added.
  4. For a stubborn driver, go back to Device Manager > Properties > Driver and choose Roll Back Driver or Uninstall device.
  5. If the issue survives all of that, contact the device or PC vendor for a chipset, dock, or firmware package that matches your model.

Prevention is simple here: add one new USB, PCI, or docked device at a time, then confirm Device Manager opens and scans normally before attaching the next item.

Keep reading

Frequently asked questions

Why is Device Manager stuck scanning plug and play compliant hardware?

That usually means Windows is waiting on one device branch to finish enumeration, driver lookup, or resource assignment. Start by disconnecting external hardware, then restart Windows and scan again. If the hang remains with nothing attached, the driver store or Plug and Play service path is the more likely target.

How do I stop Device Manager from scanning Plug and Play forever?

Remove external hardware first, then restart Windows instead of forcing a shutdown. After that, open Device Manager and use Action > Scan for hardware changes. If it still loops, check the last installed driver under Properties > Driver and roll it back or uninstall it.

Does Device Manager need administrator rights to detect hardware?

For detection alone, it can open under a standard account, but device installation wizards require administrator privileges. If Windows needs to search Windows Update or change a driver, use an administrator account and confirm the prompt. That is the safest way to let the wizard finish.

Can a bad USB or PCI device make Device Manager hang?

Yes. USB and PCI buses take full advantage of Plug and Play, so a failing hub, adapter, dock, card, or cable can block the scan. Remove the device, then reconnect only one item at a time until the problem returns. That isolates the bad branch fast.

Should I unplug devices before opening Device Manager?

Yes, if the scan hangs as soon as Device Manager opens. Unplug hubs, docks, flash drives, and other nonessential peripherals first, then retry. Leave only the devices needed to control the PC. If the issue clears, add hardware back one piece at a time.

How does Plug and Play find drivers in Windows?

Plug and Play searches locally first, then Windows Update if needed. During setup it can assign resources, load and unload drivers dynamically, and notify applications when new hardware is ready. If the local driver search fails, Windows Update becomes the fallback source.

Often, yes. Windows Update can be part of the device installation flow when a local match is missing, and that path uses WHQL-signed drivers. If the scan starts hanging after a driver update, check the device’s Driver tab, then roll back or reinstall that driver package.