A No-Guessing Procedure for a PC That Suddenly Has No USB Devices
I’ll help you isolate why a PC has suddenly lost every USB device, starting with power and physical connections before moving through firmware, the operating system, hubs, and individual ports. The sequence is designed to preserve keyboard and network access whenever possible.
When a keyboard, mouse, storage drive, and other USB devices all stop working at once, replacing parts is rarely the best first move. The failure may be as simple as a disconnected hub or overloaded port, but it can also involve firmware settings, the operating system’s USB stack, or the motherboard’s USB controller.
The useful distinction is whether all USB devices are missing everywhere or whether they fail only in one operating-system session, through one hub, or on one group of ports. Work through the checks in that order. The goal is to gather evidence without making the computer harder to control.
Start by defining what has actually failed
Disconnect nonessential USB hardware first. Leave one known-good, basic keyboard connected directly to a rear motherboard port if the computer is a desktop. On a laptop, use a built-in keyboard if it still works. Remove USB hubs, docks, card readers, external drives, printers, webcams, and charging cables for now. A faulty device or shorted hub can interfere with more than its own connection.
Try the keyboard and mouse on different physical ports, but don’t test every accessory at the same time. USB ports on the front of a desktop case may depend on an internal cable, while rear ports connect directly to the motherboard. On a laptop, ports may be distributed across more than one internal controller, so a working port on one side is useful evidence.
Also check whether the problem exists outside the operating system. Restart the computer and try to enter the firmware setup screen using the manufacturer’s indicated key, commonly shown briefly during startup. If the keyboard works in firmware but stops working once the operating system loads, the motherboard’s basic USB hardware and power are probably functioning. If it works nowhere, stay focused on power, ports, firmware, and hardware before changing operating-system settings.
Confirm your recovery controls: Before changing firmware settings or reinstalling drivers, check your motherboard or laptop manual for the setup key, reset procedure, and any available non-USB input options. Keep an internal keyboard, Ethernet connection, or another working control path available if your system provides one.
Check power and the simplest physical causes
Shut the computer down normally if you still have control. If that isn’t possible, use the operating system’s power control or hold the power button only as a last resort. Once the system is off, disconnect the AC power from a desktop or the charger from a laptop, and remove attached USB devices. Wait briefly, then reconnect power and start with only the known-good keyboard attached.
This complete power removal matters because a USB controller can remain in an abnormal state while the computer appears to be off. A normal restart doesn't always remove standby power from every controller. Don’t treat this as a permanent fix if the problem returns, but it is a low-cost way to separate a stuck controller from a persistent fault.
Look closely at the ports. Bent contacts, debris, looseness, physical damage, or a connector pushed sideways can prevent a connection and may create a short. Don’t force a plug into a damaged port or probe inside it with metal. If a port looks damaged, leave it unused and test another one.
For a desktop, inspect the internal USB cables from the case’s front-panel ports to the motherboard if the rear ports work but the front ones don't. Make sure the connector is seated in the correct header. For a laptop or all-in-one computer, don’t open the chassis merely to inspect a port unless you’re comfortable with the manufacturer’s service procedure; an external test is usually more efficient.
Separate a port problem from a controller problem
Test one simple device at a time, directly connected to the computer. A wired keyboard is a better first test than an external hard drive because it draws less power and presents fewer driver variables. If possible, use a device that works on another computer. Wireless keyboard and mouse receivers can fail because of their batteries, pairing, or receiver hardware, so they’re not ideal for the initial diagnosis.
If one port works, map the failure by location. Try the remaining rear ports, then the front ports, without reconnecting the hub or other accessories. A single dead port suggests local physical damage or a port-level fault. A complete row or group of dead ports may point to a shared controller, a motherboard header, or a firmware setting.
If every direct port fails but a network connection remains available through built-in Ethernet or Wi-Fi, keep that connection in place. It may let you use remote support, download the correct motherboard or laptop drivers, or copy diagnostic results without relying on USB storage. A USB Ethernet adapter doesn't help preserve network access if USB itself has failed; use a built-in network interface when possible.
Be cautious with high-draw devices during testing. External hard drives, bus-powered hubs, and some docks can expose a power problem that a keyboard won't. Once basic USB input works again, reconnect accessories one by one. The device that causes the failure to return is an important suspect.
Use firmware to test the boundary
If the keyboard works in firmware setup, avoid changing unrelated options. Look for USB-related settings only if the failure began after a firmware change, a reset, or a hardware installation. Names vary, but settings may refer to USB support during boot, legacy input support, xHCI, external ports, or individual port enablement.
The exact option depends on the motherboard, laptop, and firmware version. Don’t disable a setting simply because its name is unfamiliar. If you find a USB setting that is clearly disabled, record its original value before changing it. Save one change, restart, and test. If the change has no effect, return it to the previous value rather than accumulating several unexplained changes.
If the firmware screen can't see the keyboard at all, a firmware reset may be worth considering, but it can also reset boot order, memory settings, storage-controller modes, and other custom configuration. On a desktop, use the documented clear-CMOS method for the specific motherboard. On a laptop, use the manufacturer’s documented reset or recovery process. Don't improvise with battery removal or jumpers when the manual doesn't support it.
A firmware update isn't the next automatic step. It can resolve controller compatibility problems, but it also introduces interruption risk and must match the exact system model and revision. Consider it only after you’ve established that the problem is firmware-level or the manufacturer specifically identifies a relevant fix.
If USB works in firmware, troubleshoot the operating system
When USB input works before the operating system loads, boot normally with only the basic keyboard connected. If the keyboard fails at the login screen but works in a recovery environment or safe mode, a driver, service, startup program, or recent update is more likely than a dead port.
Use built-in keyboard navigation where possible. On Windows, Device Manager can show USB controllers, hubs, and devices with warning symbols; uninstalling a device entry and restarting can make the operating system detect it again. Focus on the affected USB controller or hub rather than removing unrelated hardware. Windows can reinstall standard controller drivers during startup, but the exact behavior depends on the system and operating-system version.
If you have no working mouse, use keyboard navigation or connect through a remote-management method that was already configured. Avoid downloading random “USB fixer” utilities. They add another variable and may change drivers or system settings without explaining what they changed.
On Linux, inspect the kernel or system logs for USB disconnects, enumeration errors, power faults, or controller resets, using the distribution’s available tools. On macOS, check System Information for the USB section and test without the hub or dock. Across operating systems, the same principle applies: determine whether the system detects the controller, detects the device but can't initialize it, or detects nothing at all.
If the failure started immediately after an update or driver change, use the operating system’s supported rollback or recovery option. Keep a non-USB network path if you need to obtain a driver. Download drivers from the computer or motherboard manufacturer, and match the exact model rather than choosing a similar-looking package.
Treat hubs, docks, and accessories as separate suspects
A hub or dock can fail while the computer’s own ports continue working. Test every device directly on the computer before reconnecting the hub. If direct connections work, reconnect the hub by itself, then add its devices one at a time. A powered hub should have its own correctly connected power adapter; a bus-powered hub may not provide enough power for several devices.
Docks can also combine USB with video, Ethernet, charging, and proprietary firmware. If all dock-connected devices fail but direct USB devices work, troubleshoot the dock’s cable, power supply, firmware, and host connection rather than the motherboard. A damaged USB-C cable can carry power but fail to carry data, or may not support the capabilities the dock expects.
Don't use a hub to “split” a suspected failing port while diagnosing it. That makes it harder to tell whether the original port, the hub, or one attached device is responsible. A direct connection gives you cleaner evidence.
Decide when the evidence points to hardware
Hardware becomes the leading explanation when every operating-system and firmware test fails, multiple known-good devices fail on every direct port, and a complete power removal changes nothing. It is also more likely if the failure followed liquid exposure, a surge, a damaged connector, a burning smell, or a visibly deformed port.
A motherboard can have a failed USB controller while the rest of the computer continues to boot. A laptop’s port board, internal cable, or mainboard may be replaceable, but the practical repair depends on the model. Before buying a replacement motherboard or external expansion card, test with a known-good device and, if possible, a second operating system or recovery environment. This prevents an operating-system problem from becoming an expensive hardware purchase.
If one or more ports still work, you may be able to restore basic use with a direct keyboard and mouse while planning a repair. A PCIe USB expansion card can be a reasonable desktop workaround when the motherboard’s onboard controller has failed, but it requires an available compatible slot and may not help with firmware-level input or boot-time use. On a laptop, an external hub is a workaround only if at least one reliable port remains.
Rebuild the system gradually
Once basic USB operation returns, reconnect devices in a controlled order: keyboard, mouse, network equipment, storage, printer, and finally hubs or docks. Restart after a major driver or firmware change, and note which action restored the connection. If the problem comes back, remove the last device or change and repeat the test.
The finished diagnosis should answer three questions: do USB devices work in firmware, do direct motherboard or laptop ports work, and does the failure follow a particular hub, accessory, port group, or operating-system session? Those answers are more useful than a list of devices that happened to be unplugged.
Start with the least disruptive explanation, preserve any working network or input path, and make one change at a time. That approach costs little, protects your access to recovery tools, and gives you a defensible next step when the problem turns out to be a damaged port or failing controller rather than a loose cable.