All USB Devices Disconnect & Reconnect? 7-Step Fix (2026)

The plink-plink sound is one of the most irritating noises in computing. One moment you are mid-paragraph in an important email, or deep into a ranked match, and the next, your mouse freezes for a fraction of a second. That familiar disconnect/reconnect chime plays, and suddenly you are back in control. It feels like a ghost in the machine.

If you are seeing all USB devices disconnect and reconnect in a synchronized loop, do not panic. This is not necessarily a sign that your motherboard is dying. In fact, in my fifteen years of troubleshooting enterprise systems and personal builds, this specific "synchronized reset" behavior is almost always a software conflict or a power management issue, not a physical hardware defect. While it affects many Windows 10 and 11 users, it is solvable.

Instead of randomly uninstalling drivers or restarting your PC into Safe Mode repeatedly, we are going to use a diagnostic tree. We will move from the most likely software culprits (Power Settings, Drivers) to the less common firmware issues, and finally to hardware checks. This approach saves you hours of frustration.

Step 1: Diagnose the Root Cause with Event Viewer

Before applying any fixes, we need to know what Windows thinks is happening. You can skip random guessing by looking at the system’s own black box: Event Viewer.

Open the Start menu, type Event Viewer, and hit Enter. Navigate to Windows Logs > System. Here, we are looking for "Information" and "Error" entries related to Plug and Play (PnP) service.

Identifying Specific Port Failures

Look for entries from the source "Kernel-PnPIo" or "USB-RDR". The specific error codes tell the story:

• Error Code 22: This usually means a device is not recognized or its descriptor request failed.
• Error Code 10: This indicates the device was disconnected abnormally.

Pay attention to the timestamps. If you see a burst of Code 10 errors for multiple different devices (mouse, keyboard, headset) at the exact same second, the issue is likely with the Controller or the Power Supply logic, not the individual cables. If only one device is throwing errors, the problem is isolated to that specific port or cable.

In my experience, when users report "all devices" blinking out simultaneously, the Event Viewer almost always shows a cascade of Code 10s. This confirms we are dealing with a system-wide power or driver loop, which directs us to the next steps.

Step 2: Fix Windows Power Management Settings

Windows 10 and 11 are aggressive about saving battery. On laptops, and increasingly on desktops to save energy, the OS will put USB controllers into a low-power state. If the "wake-up" signal is delayed or the controller doesn't handshake correctly, it causes a full disconnect.

Disabling USB Selective Suspend

The most common cause of these loops is a feature called "USB Selective Suspend." We need to turn this off to test if it is the culprit.

Method A: Power Options (Recommended)

1. Search for and open Control Panel.
2. Go to Power Options (set View by to "Large icons" if you don't see it).
3. Click Change plan settings for your active power plan.
4. Click Change advanced power settings.
5. Expand the USB settings tree, then USB selective suspend.
6. Set both Suspend state when plugged in and on battery to Disabled.
7. Click Apply and OK.

Method B: Device Manager

Sometimes the setting in Power Options isn't enough, or the specific port has its own override.

1. Right-click the Start button and select Device Manager.
2. Expand Universal Serial Bus controllers.
3. Right-click each USB Root Hub (there may be several, e.g., Root Hub (USB 3.0), Generic USB Hub) and choose Properties.
4. Go to the Power Management tab.
5. Uncheck Allow the computer to turn off this device to save power.
6. Repeat this for every Root Hub and Hub listed.
7. Also, expand Keyboards and Mice. Right-click your connected devices, go to Properties > Power Management, and uncheck the same setting here.

Why does this happen? Modern USB protocols have complex handshake states. If Windows tries to suspend a port while a device (like a high-polling-rate mouse or an RGB controller) is actively polling for data, the handshake fails. The system then forces a full reset, causing that plink sound. Disabling the suspend feature forces the controller to stay in a "low but active" state rather than a deep sleep.

Note: On desktop PCs, this won't save significant power. On laptops, you may see a negligible drop in battery life (often less than 5%), which is a fair trade-off for stability.

Step 3: Update or Reinstall USB Drivers

If power settings didn't stop the bleeding, the next suspect is the driver stack. Windows Update often installs generic USB drivers that are fine but not optimized for your specific chipset. Or, a recent update may have corrupted the USB Root Hub drivers.

Handling Driver Conflicts and Blue Screen Risks

We want to force Windows to re-establish a clean connection with your USB controllers.

1. Open Device Manager.
2. Expand Universal Serial Bus controllers.
3. Right-click on each USB Root Hub and Generic USB Hub and select Uninstall device.
   • Caution: If you are using a USB mouse, you will lose your input method. Have a keyboard and mouse ready.
4. Do not restart immediately.
5. Go to Action in the top menu and click Scan for hardware changes. Windows will detect the hubs and reinstall the current best driver.

Rolling Back Drivers

If this issue started right after a Windows Update, the new driver might be buggy.

1. In Device Manager, right-click a USB Root Hub > Properties > Driver tab.
2. Click Roll Back Driver if the option is available.
3. If the option is grayed out, it means no previous driver version is stored on the system. In this case, try installing the chipset drivers directly from your motherboard manufacturer's website (Intel, AMD, or ASMedia USB drivers).

Warning: Be careful with third-party "Driver Boost" software. In 90% of cases I see, these tools install outdated or incorrect drivers that cause instability. Stick to Microsoft's automatic install or the official chipset utility from your hardware vendor. If you encounter a Blue Screen (BSOD) during this process, it often points to a deeper hardware instability or a failing driver file, at which point you should stop and move to hardware diagnostics.

Step 4: Check BIOS/UEFI Settings for USB Legacy Support

Sometimes, the issue originates below the operating system, in the firmware. Your motherboard has power management features that can cut power to USB ports when the system is idle, even if Windows says it shouldn't.

ErP Ready and Power Saving in Firmware

Restart your computer and enter the BIOS/UEFI setup (usually by pressing Del, F2, or F12 during boot). The menus vary by manufacturer, but look for these specific settings:

• ErP Ready / ErP 2013 / ErP 2009: This setting controls power consumption during the "soft off" state. If this is set to Enabled, it may cut power to USB ports more aggressively. Try setting it to Disabled.
  • Note: Disabling ErP means your PC will use a tiny amount of standby power even when "off." This is usually negligible for desktops.
• USB Legacy Support: Ensure this is set to Auto or Enabled. Some boards have an option to "Force Enable USB" or "USB Wake Support." Toggle these to see if it stabilizes the ports.
• Motherboard Power Saving: Look for options like "Deep Sleep S4/S5" or "Instant On/Off." On ASUS boards, this might be under "APM Configuration." On MSI, it might be under "Settings > Advanced > USB Configuration."

I have found that on several Gigabyte and ASUS motherboards, the default "ErP" setting causes exactly this behavior: the USB controller powers down completely, and when you move the mouse, it has to "wake up" the whole subsystem, resulting in a disconnect/reconnect cycle. Disabling ErP often resolves the issue instantly.

Step 5: Hardware Diagnostics and Physical Inspection

If you've exhausted the software and firmware options, we need to look at the physical layer. A loose cable inside your PC can cause intermittent signal loss that mimics a driver issue.

Testing Ports and Cables

Perform a visual inspection of your rear panel ports. Look for bent pins or dust/debris. It sounds basic, but it happens.

• The Swap Test: Move your mouse to a different USB port (preferably a different color, e.g., from USB 3.0 blue to USB 2.0 black). If the issue stops on the new port, you have isolated a failing controller.
• The Linux Test: If you are comfortable, boot from a Linux USB stick. Linux often uses different kernel modules and power management strategies. If your devices do not disconnect in Linux, the hardware is likely fine, and the issue is definitively tied to Windows driver or power policies. This is a crucial diagnostic differentiator.
• Internal Check (Desktops): If you have a tower PC, open the case. Reseat the front panel USB headers (if applicable) and ensure the main power cables to the motherboard are secure. A loose 24-pin ATX connector can cause voltage dips that affect USB controllers.

If you are using a USB 3.0 extension cable to connect your PC to a rack-mounted unit, that cable might be the failure point. High-speed USB cables are sensitive to length and quality. Try a shorter, high-quality direct connection.

Advanced: Third-Party Software and Driver Conflicts

This is the "hidden" culprit that many guides miss. In recent years, gaming peripherals and RGB lighting software have become major sources of USB instability.

Identifying Rogue RGB and Gaming Software

I have seen numerous cases where iCUE (Corsair), Razer Synapse, or Logitech G Hub drivers interfere with the USB controller. These applications often run background services that poll devices for lighting changes or macro states. If the USB controller is already stressed by power saving, the extra polling can trigger a disconnect.

• The Test: Disable all RGB and gaming peripheral software at startup. Use msconfig or Task Manager > Startup to turn them off.
• Observe: Let the system run for a few hours. If the plink sound stops, you have found the conflict.
• The Fix: Update the specific peripheral software to the latest version. Manufacturers are aware of these driver conflicts and are often patching them. If iCUE is the culprit (as it frequently is, according to community reports), consider using the basic "iCUE Basic" version if available, or switching to a different hardware brand that has more stable drivers.

Note: This is why a "clean" Windows install sometimes fixes the issue—it removes the bloatware that was triggering the bug.

When to Consider External USB Controllers

If you have confirmed via hardware diagnostics that the internal USB controller is failing (e.g., one side of the motherboard has dead ports, or all ports are unstable regardless of software settings), your next option is external hardware.

Bypassing Faulty Onboard Ports

• PCIe Internal Cards: For desktops, you can buy a PCIe USB 3.0 controller card. This bypasses the motherboard's broken controller entirely. Choose a card with a reputable chipset (like ASMedia or Renesas) rather than a no-name Chinese brand, as driver support for off-brand chips is often poor.
• External Hubs: For laptops, a high-quality powered external USB hub (with its own power brick) can help. The hub has its own dedicated controller, offloading the work from your laptop's failing internal port.

This is a commercial solution for a hardware failure. It is not a "fix" for a software bug, but a workaround for a dying piece of hardware.

FAQ

Why do my USB devices keep disconnecting and reconnecting? The top three causes are: 1) Windows Power Management (USB Selective Suspend) is too aggressive; 2) Corrupt or conflicting USB Root Hub drivers; 3) Third-party software (like RGB lighting tools) causing polling conflicts.

How to find which USB is disconnecting and reconnecting? Use Event Viewer > Windows Logs > System. Look for Error codes 10 and 22. The "Source" column will tell you the specific device instance, and the "Data" field often contains the error code. If multiple devices disconnect at the exact same timestamp, it’s a controller-wide issue.

Do USB drivers need to be updated regularly? No. Windows Update usually handles generic USB drivers automatically. You only need to manually update if you are using a specific chipset tool (like Intel Rapid Storage or ASMedia utility) or if a bug is reported by the manufacturer. Avoid installing random "driver update" software from unknown vendors; it can cause blue screens.

Conclusion

The path to a stable USB setup is logical, not random. Start with the Diagnostic Tree:

1. Software: Check Power Options and Device Manager to disable aggressive power saving.
2. Drivers: Reinstall USB Root Hubs or roll back to a previous stable version.
3. Firmware: Disable ErP Ready in your BIOS if you are on a desktop.
4. Hardware: Isolate the failure using different ports or a Linux boot test.

If you still see issues after these steps, look at your third-party software (RGB/Gaming tools). Remember, if Linux works perfectly, your hardware is likely fine, and the problem is purely within the Windows environment. If a recent Windows Update triggered the problem, a System Restore to a point before the update is a valid fallback.

Which step resolved your issue? Let me know in the comments if you found the culprit in iCUE or a specific power setting. For a deeper dive into manual driver updates, check out our guide on How to Update Drivers on Windows 11.