This chapter covers troubleshooting USB device issues, a common topic in the CompTIA A+ Core 1 (220-1101) exam under Objective 5.1 (Hardware Troubleshooting). USB connectivity problems account for roughly 10-15% of hardware troubleshooting questions on the exam. You will learn the systematic approach to diagnosing and resolving issues such as device not recognized, power failures, driver problems, and hardware faults. Mastery of this topic is essential for passing the A+ certification and for real-world IT support roles.
Jump to a section
Imagine a secure office building with multiple entry points. Each USB port is like a security checkpoint (host controller) with a guard (root hub) managing several lanes (ports). When a visitor (USB device) arrives, the guard checks their ID (device descriptor) and assigns them a temporary badge (address). The guard then logs the visitor's capabilities (configuration descriptor) and determines which lane they should use (endpoint). If the visitor is a VIP (high-power device), the guard must first check if the building's power system can handle the load (power budget). If the visitor doesn't respond to the initial greeting (enumeration fails), the guard may try resetting them (USB reset) or reassigning a new badge. Sometimes, the visitor's ID is corrupted (bad descriptor), or they require more power than the building can supply (overcurrent). The guard can also detect if a visitor is not compatible (unsupported device) and deny entry. The building's central security system (operating system) logs all entries and errors. If many visitors fail at once, the guard may be overwhelmed (host controller failure), or the building's power grid may be faulty (motherboard issue).
What is USB and Why Troubleshoot It?
Universal Serial Bus (USB) is a standard interface for connecting peripherals to a computer. It supports hot-swapping, meaning devices can be connected and disconnected without powering down the system. USB has evolved through versions 1.x (1.5/12 Mbps), 2.0 (480 Mbps), 3.x (5/10/20 Gbps), and 4 (40 Gbps). The 220-1101 exam focuses on USB 2.0 and 3.0/3.1 Gen 1/2. Troubleshooting USB issues is critical because nearly every peripheral—keyboards, mice, printers, external drives, webcams, and flash drives—uses USB. Common problems include device not detected, intermittent disconnections, slow transfer speeds, and power errors.
How USB Works Internally
USB uses a host-driven protocol. The host controller (usually integrated into the chipset) manages all communication. The host polls devices periodically. When a device is connected, the following occurs: - Electrical Detection: The host detects a change in voltage on the D+ or D- lines. For USB 2.0, a full-speed device pulls D+ high, a low-speed device pulls D- high. USB 3.0 uses additional SuperSpeed pairs. - Reset: The host sends a reset signal (SE0 state for at least 10 ms) to put the device into a known state. - Enumeration: The host assigns a unique address (1-127) and reads the device descriptor (18 bytes) containing Vendor ID (VID), Product ID (PID), and class code. Then it reads configuration descriptors, interface descriptors, and endpoint descriptors. - Configuration: The host selects a configuration (usually the first) and the device is ready for use.
Key Components, Values, Defaults, and Timers
Host Controller: Manages the USB bus. Types: EHCI (USB 2.0), xHCI (USB 3.x and backward compatible). xHCI is the current standard.
Root Hub: Part of the host controller, provides physical ports. Each port can supply up to 500 mA for USB 2.0, 900 mA for USB 3.0.
Power Budget: Total power available per port. Exceeding this triggers overcurrent protection.
Descriptors: Device (18 bytes), Configuration (9 bytes), Interface (9 bytes), Endpoint (7 bytes). The device descriptor includes bcdUSB (USB version), idVendor, idProduct.
Addresses: 7-bit, so up to 127 devices (address 0 reserved for unconfigured devices).
Endpoints: Each device has up to 32 endpoints (16 IN, 16 OUT). Endpoint 0 is the default control endpoint.
Transfer Types: Control (enumeration), Bulk (large data, e.g., printers), Interrupt (keyboards, mice), Isochronous (audio/video).
Timers: The host controller has a timeout for device response. If a device does not respond within 5 seconds (typical), the host may fail enumeration and report 'Device Not Recognized'.
Configuration and Verification Commands
In Windows, Device Manager is the primary tool. Key actions:
- View hidden devices: Run set devmgr_show_nonpresent_devices=1 then devmgmt.msc.
- Check power: In Device Manager, right-click USB Root Hub > Properties > Power Management > uncheck 'Allow the computer to turn off this device to save power'.
- Driver update: Right-click device > Update driver.
- Uninstall/reinstall: Uninstall device, then scan for hardware changes.
- USB troubleshooting tool: usbview.exe (Windows SDK) shows USB topology and descriptor details.
- Linux: Use lsusb to list devices, dmesg to see kernel messages, usb-devices for descriptors.
- macOS: System Information > USB for device list.
Interaction with Related Technologies
Power Management: USB selective suspend (default after 2 seconds of inactivity) can cause devices to stop responding. Power management settings in Windows can disable this.
BIOS/UEFI Settings: Legacy USB support must be enabled for USB devices to work in pre-OS environments. xHCI hand-off may need adjustment.
Driver Stack: Class drivers (e.g., HID, mass storage) handle common device types. Vendor-specific drivers may be required. Driver conflicts cause 'Code 39' or 'Code 43' errors.
Overcurrent Protection: The host controller monitors current draw. If a device draws more than allowed, the port is disabled and an 'Overcurrent' error appears in Device Manager.
USB Hubs: External hubs have their own power budget. Bus-powered hubs share power with the host; self-powered hubs have their own supply. Connecting too many high-power devices to a bus-powered hub can cause failures.
Step-by-Step Troubleshooting Methodology
Identify the Symptom: Device not recognized, intermittent connection, slow speed, power error, or no power.
Check Physical Connections: Try a different port, cable, or computer. Ensure the cable is not damaged. USB 3.0 cables have more wires; a faulty cable can cause speed downgrades.
Check Power: For high-power devices (external drives), use a self-powered hub or the computer's rear USB ports (more stable power).
Update Drivers: Use Device Manager to update or reinstall drivers. For mass storage devices, the generic driver is usually sufficient.
Check Device Manager: Look for yellow exclamation marks. Common error codes:
- Code 10: Device cannot start (driver or hardware issue). - Code 28: Driver not installed. - Code 39: Driver missing or corrupted. - Code 43: Device descriptor failure (hardware or driver problem). 6. Disable USB Selective Suspend: In Power Options > Advanced settings > USB settings > USB selective suspend setting > Disabled. 7. Reset the USB Controller: In Device Manager, uninstall all USB controllers from the 'Universal Serial Bus controllers' section, then restart. The system will reinstall them. 8. Check for BIOS Updates: Outdated BIOS can cause USB compatibility issues, especially with USB 3.0. 9. Test in Safe Mode: If the device works in Safe Mode, the issue is likely driver-related. 10. Use Event Viewer: Check System logs for USB-related errors (source: USB, Event ID 1-3).
Common Pitfalls and Exam Traps
Assuming a dead port: Always test with a known-good device. A single port failure could be a motherboard issue, but multiple port failures suggest host controller or driver problem.
Overlooking power: Many candidates forget that USB ports have power limits. Plugging a high-power device into a bus-powered hub can cause failures.
Confusing USB 2.0 and 3.0: USB 3.0 ports have additional pins; using a USB 2.0 cable in a USB 3.0 port will limit speed to USB 2.0. The exam may test this.
Ignoring BIOS settings: Legacy USB and xHCI hand-off settings are common exam topics.
Misinterpreting error codes: Code 43 (device descriptor failure) often indicates a hardware problem, not just a driver issue. The exam expects you to know this.
Identify the symptom and gather info
Determine whether the device is not detected at all, works intermittently, operates at slow speeds, or causes power errors. Check if the issue occurs with other devices on the same port or with the same device on other ports. Note any error messages (e.g., 'USB Device Not Recognized', 'Power Surge on Hub Port'). This step narrows down whether the problem is with the device, cable, port, host controller, or driver.
Check physical connections and cables
Inspect the USB cable for damage, try a different cable, and connect the device to a different USB port. If using a hub, connect directly to the computer. For USB 3.0 devices, ensure the cable and port are both USB 3.0 (blue port, SS logo). A faulty cable can cause intermittent connections or speed downgrades. Also check for bent pins or debris in the port.
Check power supply to the device
Some devices (e.g., external hard drives) require more power than a single port can provide. Use a self-powered hub or connect to a powered USB port (often on the back of the computer). In Device Manager, check the properties of the USB Root Hub for power usage. If the device is not spinning up or LED is dim, power is likely insufficient.
Update or reinstall drivers
Open Device Manager and locate the device (might be under 'Other devices' with a yellow exclamation). Right-click and select 'Update driver' > 'Search automatically for drivers'. If that fails, uninstall the device and scan for hardware changes. For mass storage devices, the generic driver is usually adequate. For vendor-specific devices, download the driver from the manufacturer's website.
Disable USB selective suspend
USB selective suspend allows the system to turn off a USB port to save power. This can cause devices to stop responding. To disable: Control Panel > Power Options > Change plan settings > Change advanced power settings > USB settings > USB selective suspend setting > set to 'Disabled' for both battery and plugged in. Restart the computer.
Reset the USB host controller
In Device Manager, expand 'Universal Serial Bus controllers'. Right-click each entry (e.g., 'Intel(R) USB 3.0 eXtensible Host Controller') and select 'Uninstall device'. Do this for all USB controllers. Restart the computer; Windows will automatically reinstall the drivers. This clears any corrupted driver state or resource conflicts.
Check BIOS/UEFI settings
Restart the computer and enter BIOS/UEFI setup (usually F2, Del, or F10). Ensure 'Legacy USB Support' is enabled (for older devices) and 'xHCI Hand-off' is enabled (for USB 3.0 compatibility with older OS). Save and exit. Incorrect BIOS settings can prevent USB devices from working during boot or in the OS.
Test in Safe Mode or alternative OS
Boot into Safe Mode (Windows) or a live Linux USB. If the device works in Safe Mode, the issue is likely a third-party driver or software conflict. If it fails in all environments, the problem is hardware-related (device, cable, or motherboard). This step isolates software vs. hardware causes.
In an enterprise environment, USB issues often arise with peripheral deployment, such as connecting barcode scanners, receipt printers, or external storage at point-of-sale (POS) systems. For example, a retail chain deploys USB barcode scanners across hundreds of registers. A common problem is intermittent disconnection due to USB selective suspend. The IT team configures group policy to disable USB selective suspend on all POS machines, resolving the issue. Another scenario involves connecting external hard drives for backup. Users plugging high-power 3.5" drives into front-panel USB ports (which may not supply sufficient power) experience drive failures. The solution is to use rear USB ports or self-powered hubs. In a data center, USB 3.0 flash drives are used for OS installation. If the BIOS has xHCI hand-off disabled, the USB 3.0 drive may not be recognized during boot, causing delays. The engineering team enables xHCI hand-off in BIOS settings across all servers. Performance considerations: USB 3.0 cables are more sensitive to length; cables longer than 3 meters may cause signal degradation. In production, IT professionals often use active extension cables or USB over Ethernet for long distances. Misconfiguration of power management in Windows can lead to user complaints of 'device not working after sleep'. The fix is to disable 'Allow the computer to turn off this device to save power' on each USB Root Hub. Troubleshooting at scale requires remote management tools like PowerShell to reset USB controllers or disable selective suspend across many machines.
The 220-1101 exam tests USB troubleshooting under Objective 5.1 (Given a scenario, troubleshoot problems with devices and peripherals). Specifically, you must know how to resolve 'Device not recognized', 'Intermittent connectivity', 'Power failure', and 'Driver issues'. The exam loves to test the following wrong answers:
'Replace the motherboard' – Candidates often jump to this when multiple ports fail. The correct first step is to reset the USB controller or update drivers, as the host controller is often separate from the motherboard and can be reset.
'The device is broken' – When a device fails on one port but works on another, the problem is with the port, not the device. The exam will present a scenario where a device works on the back ports but not the front; the answer is insufficient power or a faulty front panel connection.
'Update the BIOS' – While sometimes needed, the exam expects you to first try simpler steps like disabling USB selective suspend or resetting the controller. BIOS update is a last resort.
'Replace the USB cable' – This is correct only if the cable is visibly damaged or the issue is intermittent. The exam may include a scenario where the cable is fine but the device is not recognized; the answer is to reinstall drivers.
Specific numbers: USB 2.0 max power = 500 mA, USB 3.0 = 900 mA. Default USB selective suspend timeout = 2 seconds. Device address range = 1-127. The exam may ask: 'A USB device is not working after the computer wakes from sleep. What should you do?' Answer: Disable USB selective suspend or uncheck 'Allow the computer to turn off this device to save power'.
Edge cases: USB 3.0 devices plugged into USB 2.0 ports will work at USB 2.0 speeds. The exam might present a scenario where a USB 3.0 external drive is slow; the answer is it's connected to a USB 2.0 port. Also, overcurrent protection: if a device draws too much power, the port is disabled and an 'Overcurrent' error appears in Device Manager. The solution is to disconnect the device and restart the computer.
To eliminate wrong answers, focus on the underlying mechanism: if the device is detected but not working, it's likely a driver or power issue. If not detected at all, check physical connection, port, or host controller. If intermittent, check power management or cable.
USB 2.0 max power is 500 mA; USB 3.0 max power is 900 mA per port.
USB selective suspend is enabled by default and can cause devices to stop responding after idle; disable it in Power Options.
Device address range is 1-127; address 0 is reserved for unconfigured devices.
Code 43 in Device Manager indicates a device descriptor failure, often hardware-related.
To reset USB controllers, uninstall all entries under 'Universal Serial Bus controllers' in Device Manager and restart.
USB 3.0 devices are backward compatible but will run at USB 2.0 speeds if connected to a USB 2.0 port.
Overcurrent errors occur when a device draws more power than allowed; disconnect the device and restart.
BIOS settings 'Legacy USB Support' and 'xHCI Hand-off' must be enabled for proper USB functionality.
These come up on the exam all the time. Here's how to tell them apart.
USB 2.0
Maximum speed: 480 Mbps (High Speed)
Maximum power: 500 mA per port
Cable has 4 wires (Vbus, D+, D-, GND)
Ports are usually white or black
Host controller: EHCI
USB 3.0
Maximum speed: 5 Gbps (SuperSpeed) for Gen 1, 10 Gbps for Gen 2
Maximum power: 900 mA per port
Cable has 9 wires (additional SuperSpeed pairs)
Ports are usually blue or teal
Host controller: xHCI (backward compatible)
Mistake
All USB ports supply the same amount of power.
Correct
USB 2.0 ports supply up to 500 mA, USB 3.0 up to 900 mA. Some ports (e.g., front panel) may supply less due to wiring. Also, USB ports can be limited by the host controller's total power budget.
Mistake
If a USB device is not recognized, the device is broken.
Correct
The device may be fine; the issue could be a driver, port, cable, or power problem. Always test the device on another computer before concluding it's faulty.
Mistake
Updating the BIOS always fixes USB issues.
Correct
BIOS updates can fix compatibility issues, but they are not the first step. Most USB issues are resolved by driver updates, power management changes, or resetting the host controller.
Mistake
USB 3.0 devices will work at full speed on any USB port.
Correct
USB 3.0 devices are backward compatible with USB 2.0 ports but will operate at USB 2.0 speeds (480 Mbps). To get USB 3.0 speeds, both the port and cable must be USB 3.0.
Mistake
Disabling USB selective suspend always resolves intermittent disconnections.
Correct
While it often helps, intermittent disconnections can also be caused by faulty cables, loose connections, or driver issues. Selective suspend is just one of many potential causes.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
The most common cause is a driver issue or a power management setting. First, try a different USB port and cable. If that fails, open Device Manager and look for the device under 'Other devices' with a yellow exclamation. Update or reinstall the driver. Also, disable USB selective suspend in Power Options. If the device still fails, reset the USB host controller by uninstalling all USB controllers in Device Manager and restarting. If none of these work, test the device on another computer to determine if the device itself is faulty.
Intermittent disconnections are often caused by USB selective suspend or a faulty cable. Disable USB selective suspend in Power Options. Also, check the cable for damage and try a different one. If using a hub, connect directly to the computer. In Device Manager, for each USB Root Hub, go to Properties > Power Management and uncheck 'Allow the computer to turn off this device to save power'. If the problem persists, update chipset drivers or try a different USB port.
Code 43 means Windows has stopped the device because it reported a problem (device descriptor failure). This typically indicates a hardware issue with the device, cable, or port. It can also be caused by a corrupted driver. First, uninstall the device and scan for hardware changes. If that fails, try a different port or cable. If the error follows the device to another computer, the device is likely faulty. If it stays on the same port, the port or host controller may be bad.
USB 3.0 ports are often color-coded blue (or teal for USB 3.1), while USB 2.0 ports are usually black or white. Additionally, USB 3.0 ports may have an 'SS' (SuperSpeed) logo next to them. You can also check in Device Manager: USB 3.0 host controllers are labeled 'eXtensible Host Controller' or 'xHCI'. In Windows, connect a device and check the 'Speed' property in the device's properties (e.g., 480 Mbps for USB 2.0, 5 Gbps for USB 3.0).
USB selective suspend is a power-saving feature that allows the system to put an idle USB port into a low-power state. By default, the port suspends after 2 seconds of inactivity. This can cause devices like mice, keyboards, or external drives to stop responding until the user interacts with them again. To fix this, disable USB selective suspend in Power Options or uncheck 'Allow the computer to turn off this device to save power' for each USB Root Hub in Device Manager.
The drive is likely connected to a USB 2.0 port or using a USB 2.0 cable. USB 3.0 devices are backward compatible but will operate at USB 2.0 speeds if the port or cable is only USB 2.0. Ensure you are using a blue USB 3.0 port and a cable with the USB 3.0 logo. Also, check that the drive is not connected through a USB 2.0 hub. Additionally, background processes or a fragmented drive can slow performance.
To reset all USB ports, open Device Manager, expand 'Universal Serial Bus controllers', right-click each entry (e.g., 'Intel(R) USB 3.0 eXtensible Host Controller') and select 'Uninstall device'. Do this for all USB controllers. Then restart the computer. Windows will automatically reinstall the drivers and reset the USB ports. Alternatively, you can use the 'devcon' command-line tool or a simple restart if the issue is temporary.
You've just covered Troubleshoot: USB Device Issues — now see how well it sticks with free 220-1101 practice questions. Full explanations included, no account needed.
Done with this chapter?