If Device Manager keeps refreshing in Windows 10, treat it as a USB enumeration loop first: unplug external devices and hubs, then check Event Viewer and services before replacing hardware. Ignoring the loop can hide the faulty port, device, or driver while the constant reconnects waste time and make Device Manager hard to use. Start with the quickest isolation path.
Likely causes
Most often, the loop comes from a USB device or branch that keeps connecting and disconnecting. Less often, a background service, a driver issue, or firmware problem keeps reintroducing the same device state. Windows 10 is the main target here, and the same general pattern can also show up on Windows 11.
Say your USB keyboard works normally, but Device Manager flickers every few seconds. That points away from the keyboard itself and toward another USB device, a controller branch, or software that is repeatedly probing hardware.
Fastest order to check
- Disconnect nonessential external USB devices.
- Re-test the same device in another port if the loop returns.
- Check internal USB devices such as a webcam or SD card reader.
- Look for USB-related software and services that may be involved.
- In Device Manager, open the device or controller, then use the Driver tab to Update driver, Roll Back Driver, or Uninstall device and reinstall it after reboot.
- Escalate to BIOS, chipset, or hardware checks if the loop survives.
📊 Microsoft’s open-Device-Manager page applies to Windows 10. Source: Open Device Manager.
USB refresh checklist
This checklist is the fastest way to stop guessing. It maps likely triggers to one exact test, the expected result, and the next move if the refresh continues.
| Likely trigger | Exact test | Expected result | Next step |
|---|---|---|---|
| USB Root Hub | Device Manager > Universal Serial Bus controllers > right-click USB Root Hub > Disable device | The refresh loop stops or changes immediately | Re-enable it, then test the branch with another port |
| Webcam | Unplug the webcam, then reopen Device Manager from Start search | The loop stops | Test the webcam in another port; if it still loops, the device or cable is suspect |
| SD card reader | Remove the card and disconnect any external reader | The loop stops | Test the reader alone on a rear port |
| Wireless receiver | Unplug the receiver and wait 30 seconds | No further refreshes | Try a different port, preferably on a different controller branch |
| VMware USB Arbitration Service | services.msc > VMware USB Arbitration Service > Stop, if that service appears to be involved |
The loop stops while the service is stopped | Set Startup type to Manual, then test after a reboot |
| SSDP Discovery Service | services.msc > SSDP Discovery Service > Stop |
The loop stops in the reported workaround | Leave it disabled only if the tradeoff is acceptable for that system |
| RGB/fan controller | Disconnect the internal USB lead from the controller header | The loop stops | Move the controller to another header only after confirming the lead is the trigger |
| Faulty port | Move one device from a front port to a rear motherboard port | The loop changes or stops | Use the rear port branch for the next test |
| Motherboard header | Test the same USB device on another rear port on the same controller | The issue repeats only on one branch | Try a different controller branch if available |
| Power issue | Disconnect nonessential USB devices and test with the system at idle | The loop disappears when load is lower | Retest after a clean boot; if it persists, treat it as hardware |
| Chipset driver | Device Manager > USB controller > Properties > Driver > Update driver | The controller stabilizes after reinstall or update | Install the OEM chipset package if Windows Update has none newer |
| BIOS/firmware | Update BIOS/UEFI from the motherboard or OEM support page | USB detection becomes stable after reboot | If not, treat the board or header as suspect |
Is a USB device causing it?
Yes, a USB device can trigger nonstop refreshes, and that includes external peripherals plus onboard parts that appear as USB devices. Microsoft support also notes that many peripheral devices are classed as USB devices, with SD card readers and webcams given as examples.
Open Device Manager from Start search, then disconnect every nonessential USB device. If the loop stops, reconnect one device at a time. If it returns, test that same device in another port before moving to the next item.
Use the same-device port test
- Unplug the suspected device.
- Wait for Device Manager to settle.
- Plug the same device into a rear motherboard port, not a front-panel port.
- If the loop returns, move that same device to another rear port on the same controller.
- If the machine has another controller branch, test that branch separately.
Picture a USB webcam that causes refreshes only on the front panel. The same webcam on a rear port may run normally, which points to the front-port wiring or header rather than the camera itself.
Does a faulty USB root hub cause Device Manager to refresh?
It can. USB Root Hub is the branch in Device Manager that fans out to devices on a controller, so it is a practical place to isolate a bad port or a bad device path. If disabling one hub changes the loop, that branch deserves closer attention.
Isolate the branch
- Press Win+X, open Device Manager, then expand Universal Serial Bus controllers.
- Right-click one USB Root Hub entry and choose Disable device.
- Wait about 20 to 30 seconds and watch whether the refresh loop stops.
- If it stops, re-enable the hub and test the devices on that branch one by one.
- If it does not stop, restore the hub and test a different branch or controller.
A common mistake is assuming a rapidly refreshing Device Manager means every USB controller should be turned off at once. That makes the machine harder to recover and hides which branch actually changed the symptom.
Could background software be triggering it?
Yes. A reported case on Windows 10 involved VMware Workstation Player, and removing it fixed the problem. Another report said stopping SSDP Discovery Service made the issue go away. Treat both as checks, not proof of root cause.
Microsoft advisor guidance also says Windows does not store a log of these connections, and recommends NirSoft USB Log View to identify which device is causing the refreshes. (Microsoft Learn)
Check services and logs
- Press Win+R, type
services.msc, and open it. - Find VMware USB Arbitration Service, right-click it, and choose Stop.
- Watch Device Manager for 30 seconds.
- If the loop stops, set Startup type to Manual, reboot, and retest.
- If you use VMware and the loop returns after reboot, remove or reinstall the component and test again.
- For event tracing, run NirSoft USB Log View and watch for repeated connect and disconnect entries.
Device Manager path:
Win+X > Device Manager > device > right-click > Properties > Driver tab
Actions:
Update driver
Roll Back Driver
Uninstall device
Check "Delete the driver software" when reinstalling a corrupted driver
Hidden devices:
Device Manager > View > Show hidden devices
When the loop survives the easy checks
If unplugging devices, testing ports, and checking services do not stop the refreshes, move to internal USB devices and then to firmware. Webcams, internal card readers, RGB controllers, and other onboard USB parts can sit on internal headers and keep announcing themselves to Windows 10.
Next, update the chipset driver. Microsoft’s update-driver page covers Windows 11 and Windows 10, and Microsoft says driver updates for most hardware devices are automatically downloaded through Windows Update. If Windows Update has no newer package, install the OEM or chipset vendor driver directly. (Microsoft Support)
Escalation ladder
- Open Device Manager and check for any device with a warning icon.
- Right-click the USB controller or related device, then use Update driver.
- If the driver is already current, choose Uninstall device, then reinstall it after reboot.
- Check Windows Update for optional driver updates.
- Update BIOS or UEFI from the motherboard or system vendor.
- If the refresh loop survives all of that, suspect the motherboard, internal header, or power delivery path, and contact the vendor or a repair shop.
Suppose a desktop with a front-panel SD card reader keeps looping even after every external device is removed. If the rear ports stay quiet but the front bay still triggers refreshes, the internal header or the reader assembly becomes the next branch to replace or disconnect.
Prevention: keep the device that caused the loop on a known-good rear port, and avoid front-panel ports for high-churn devices such as webcams, card readers, and wireless receivers.
Frequently asked questions
Why does my computer keep refreshing?
A constant refresh usually means Windows is seeing repeated hardware changes, most often from USB activity. Start with external devices, then check the specific controller branch in Device Manager. If nothing external changes the behavior, test internal USB devices and background services next.
Why does Device Manager keep refreshing every few seconds?
The usual pattern is a device, hub, or service repeatedly entering and leaving the USB bus. Open services.msc, stop any suspicious USB-related service one at a time, and watch whether the interval changes. If it does, you have a narrower target to test.
Can a USB device cause Device Manager to refresh nonstop?
Yes. A webcam, SD card reader, wireless receiver, or another USB-classed peripheral can trigger the loop if it is failing or the port is unstable. Test the same device in a rear motherboard port, then in another rear port on the same controller.
How do I find which device is causing Device Manager to refresh?
Use a one-device-at-a-time test and record the result. If that is still unclear, run NirSoft USB Log View and look for repeated connection events. Pair that with Device Manager > View > Show hidden devices to spot stale or ghost entries.
Can VMware or other background services cause Device Manager to keep refreshing?
They can. A reported fix involved removing VMware Workstation Player, and another involved stopping SSDP Discovery Service. Test one service at a time in services.msc, then reboot before deciding whether to keep the change.