Start by cross-testing the device and cable on a direct port and another computer. Record the exact Device Manager error, and never format a USB storage device containing files you need just because Windows cannot read it.
Check which part of the USB connection fails
The message USB device not recognized is a symptom, not a diagnosis. The peripheral may be faulty, the cable may carry power but not data, the port or hub may be damaged, the device may need more power, or Windows may have a driver or enumeration problem. A storage drive that does not appear in File Explorer follows a slightly different path from a mouse or keyboard that never connects.
If the device is a USB storage drive with important files, do not accept a format or initialization prompt as a fix. Preserve the data first. If the connector or port is visibly damaged, hot, smells burnt or only works when held at an angle, stop testing it.
| Test result | What it suggests | Next step |
|---|---|---|
| One device fails in one port | Port, cable or device-specific issue | Try a direct alternate port and a known-good compatible cable. |
| Several devices fail in the same port | Port, hub, power or host-controller path | Remove the hub and test another direct port. |
| Device works on another computer | Original PC, port, driver or power path | Inspect Device Manager and test a direct port. |
| Device fails on two computers with a known-good cable | Peripheral, cable compatibility or device firmware | Check the device manufacturer's support instructions. |
| Storage device appears in Disk Management but not File Explorer | Mounting, partition or drive-letter issue rather than USB enumeration alone | Follow the SSD/disk detection guide and protect data. |
Test the device, cable, port and hub one at a time
Disconnect the device, wait briefly and connect it directly to a built-in USB port rather than a dock or unpowered hub. On a desktop, test another accessible port that is documented for the same connector type. For a device with a detachable cable, try a known-good cable that supports the device's data and power needs; some cables are intended primarily for charging.
If the peripheral needs substantial power, use its manufacturer-approved power supply or a suitable powered hub. A hub adds another component to the connection path, so remove it during initial isolation and add it back only after the direct test is stable.
Test the same device on another computer if available. If it works there, focus on the original PC's port, host controller, driver stack or power path. If it fails across systems with a known-good cable, the peripheral or its firmware becomes a stronger suspect. Neither test is conclusive on its own, but together they narrow the possibilities.
- Safely disconnect the peripheral and inspect the connector externally.
- Connect directly to a different suitable port without a hub.
- Test with a known-good, data-capable cable where the cable is detachable.
- Try the same device on another computer if available.
- Record exactly which combination succeeds or fails before changing drivers.
Read the Device Manager error before reinstalling a driver
Open Device Manager, find the affected device or Unknown USB Device entry, and open Properties. Record the exact Device status error code and the device name before making changes. A yellow warning symbol shows that Windows has a problem with the device, but the code and device class give more useful direction.
If the code points to a missing or malfunctioning driver, use Windows Update or the peripheral maker's official support page for the exact model and Windows version. Microsoft documents how to update, reinstall or roll back a specific driver through Device Manager. Avoid bulk driver updaters and registry cleaners.
If the issue began immediately after a driver update, use the driver's Roll Back Driver option when available and compare behavior. If you uninstall a device entry as a targeted troubleshooting step, save your work first and restart Windows so it can re-enumerate the hardware. Do not repeatedly uninstall every USB controller without a model-specific reason.
Treat USB storage differently from a keyboard or mouse
If a USB flash drive or external SSD is detected by Windows but not shown in File Explorer, open Disk Management and inspect its status without making changes. It may be offline or lack a drive letter, but it may also have a damaged partition or failing storage. Use its capacity and identity to make sure you are looking at the correct device.
Do not initialize, format, delete partitions or run destructive disk commands on a drive containing important files. If it reports RAW, Not Initialized, I/O errors or disappears intermittently, prioritize a backup or recovery path rather than trying to make the warning disappear.
For USB-C devices, check the port and cable capability as well as the connector shape. A USB-C port may support a subset of data, display or power features, and a physically compatible cable does not automatically support every mode. Use the device and computer manuals for the exact capabilities.
When the fault needs hardware service
Stop using a port that is loose, visibly bent, burnt or unusually hot. Do not force an oversized connector into a port, bend the plug to maintain contact, or open a powered device to inspect its circuitry. A damaged port or peripheral may need service even if Windows no longer displays an error.
If several devices fail on one PC after direct-port and cross-computer tests, update Windows through supported channels and check the computer manufacturer's official chipset or USB-controller guidance. If the machine is under warranty or the controller problem persists, seek model-specific service rather than installing unrelated drivers.
A USB error can originate from the peripheral, cable, port, hub, power budget, device firmware or Windows driver stack. A cross-test isolates the fault more reliably than changing every driver at once. The available error details differ between device classes and Windows versions.
See the evidence behind this topic
These TWW research pieces examine the measurements, mechanisms, or testing questions related to this guide. Research pages distinguish measured results from general technical guidance.
- Windows Shows 100% Disk Usage but Very Low MB/s: What Is Actually Happening?100% active time is not the same thing as 100% storage bandwidth. The difference is the key to diagnosing many Windows disk complaints.
- Does More RAM Actually Make Windows Faster? What to Measure Before UpgradingYes—when memory capacity is the bottleneck. If Windows already has enough memory for the workload, adding more RAM may make little or no measurable difference.
Sources & further reading
Frequently asked questions
Why does Windows say USB device not recognized?
The message can arise from the device, cable, port, hub, power path or Windows driver stack. Test a direct port, a suitable known-good cable and another computer before choosing a repair.
Should I uninstall all USB controllers in Device Manager?
No. Start with the exact device and its error code, then follow the manufacturer's or Microsoft's targeted guidance. Broad controller changes can disrupt other peripherals and are not the first step.
What if my USB drive asks to be formatted?
Do not format it if you need the files. Check the drive's identity and status, avoid writes, and use a data-preservation or recovery path if the data matters.
Can a USB-C cable charge a device but fail to transfer data?
Yes. Cable capabilities vary. Use a known-good cable that supports the data function and power level required by the device, and verify the port capabilities in the manufacturer's documentation.
We distinguish documented facts, measured results, and informed guidance. If a claim depends on a specific device, software version, game, or test method, that context should be stated rather than implied.
Meet the author·See our testing methodology·Read our editorial policy
