When a USB is not detected, first determine whether Windows hears the connection, Device Manager lists hardware, or Disk Management sees storage. Those are different failures. Test one known-good port and cable, then stop if the device clicks, overheats, repeatedly disconnects, or reports the wrong capacity. Do not initialize, format, or run CHKDSK before protecting important files. A stable drive visible in Disk Management may still be recoverable even without a File Explorer letter.
Map the Last Place Windows Can See the USB
“Not detected” can mean no electrical response, a failed USB enumeration, a storage device without a mounted volume, or simply a missing drive letter. Open Device Manager and Disk Management without accepting prompts to initialize or format. Record the displayed name, capacity, status, and any problem code.
| Observed state | Likely layer | Safest next move |
|---|---|---|
| No sound, light, or Device Manager change | Port, cable, power, enclosure, or device electronics | Try one known-good direct connection |
| Unknown USB Device or warning icon | Enumeration, descriptor, power, or driver start | Read the exact Device Manager code |
| Disk Management shows correct capacity | Volume, filesystem, partition, or letter issue | Protect data before making metadata changes |
| Disk appears RAW or Unallocated | Filesystem or partition access is damaged | Recover first; do not format or create a volume |
| Capacity is zero or wildly wrong | Bridge, firmware, controller, or media trouble | Stop software repair and seek specialist assessment |
This map prevents an ineffective sequence of driver reinstalls on a damaged drive. It also avoids treating a harmless letter collision as data loss.
Check One Physical Variable at a Time
Remove hubs and verify the connection
Connect directly to the PC. For an external drive, use its original power supply and a known-good data cable of the correct type. Test one other port, preferably on a different side of a laptop or a rear motherboard port on a desktop. Do not repeatedly power-cycle a drive that spins down, clicks, or vanishes under load.
Compare with a harmless known-good USB device. If nothing works in that port, the computer branch becomes stronger. If the important drive fails on two computers while other devices work, suspect its cable, enclosure, controller, or media.
Separate enclosure trouble from disk trouble carefully
An external HDD or SSD may sit behind a USB-to-storage bridge. A failed bridge can hide a healthy disk, but opening an enclosure may void a warranty or expose a drive that uses hardware encryption. Some portable drives integrate the USB controller. Do not remove the disk unless its design, encryption, warranty, and safe handling are understood.
Stop on physical warning signs
Clicking, grinding, burning odor, liquid exposure, impact damage, repeated resets, or extreme heat are not filesystem symptoms. Scanning does not repair hardware. Disconnect the device and consult a recovery professional when the files justify the cost.
Read Device Manager Evidence Instead of Guessing
Expand Disk drives, Universal Serial Bus controllers, and Portable Devices. Open the suspicious item’s Properties and note Device status. Microsoft’s device-installation troubleshooting guidance explains that a warning icon and problem code identify installation or configuration trouble. Keep the exact code because Code 10, Code 43, and an unknown descriptor do not have identical causes.
Use Action > Scan for hardware changes after one reconnection. Restart Windows if the controller appears stuck. Obtain chipset, USB-controller, and storage drivers from the PC or motherboard manufacturer. Avoid generic driver-download sites.
Uninstall only the clearly identified device entry
If the same stable device has a reproducible driver-start problem, uninstall its device entry and reconnect so Windows can enumerate it again. Do not indiscriminately remove every USB controller on a remote-managed PC. Ensure a keyboard, recovery path, and administrator access remain available.
Power management is a pattern, not a universal answer
If recognition fails mainly after sleep, inspect USB selective suspend and the hub’s power-management setting. Change one setting temporarily and retest. A drive that disconnects during reads on multiple computers is more concerning than a port that sleeps only on one Windows installation.
Use Windows logs to confirm timing
Reliability Monitor and Event Viewer can reveal when a driver, controller, or storage service failed. Match the timestamp to the connection attempt. A recurring event after resume supports a power or driver branch, while repeated disk resets during ordinary reads suggest unstable access. Do not treat one unrelated warning as proof. Capture the source, event ID, and time so an administrator can compare it with driver-installation records.
On a managed PC, also ask whether device-control policy blocks removable storage. Policy can allow the USB hardware to enumerate while denying volume access. Bypassing such controls is neither a repair nor an appropriate data-recovery step.
Interpret Disk Management Without Writing to the Drive
If Disk Management shows the correct physical disk and a healthy volume, File Explorer may only lack a letter. Check for a collision or a volume mounted as a folder. Follow a controlled partition and volume check before changing anything.
A healthy non-system data volume can receive an unused drive letter, provided it is not an application dependency and BitLocker access is understood. Never assign or change letters on EFI, recovery, or unfamiliar system partitions. If the filesystem is unsupported by Windows, use the appropriate operating system rather than formatting.
If BitLocker identifies the volume, locate the correct recovery key through the authorized account or administrator. Recovery software must not be presented as a way around encryption. A locked but correctly detected encrypted volume is different from a missing partition, and guessing keys or altering metadata can reduce the chance of normal access.
RAW, Unallocated, and Not Initialized require restraint
These states can result from damaged filesystem metadata, a lost partition, enclosure translation differences, or an incorrect disk identity. Initialization writes disk metadata. Formatting creates a filesystem and can overwrite evidence. The safer order is backup or recovery first, then structural repair after recovered files are verified.
The same rule applies when Windows offers “You need to format the disk.” Read what to do before formatting rather than accepting the prompt.
Recover Files From a Stable, Recognized USB With Drecov
Drecov performs Windows file retrieval from computers, HDDs, SSDs, external disks, USB media, and memory cards. It finds pictures, video, documents, mail content, audio, and archives without repairing the source. The workflow starts with Quick Scan. Deep Scan can follow while the device stays stable. Users may filter and preview candidates, then save selected results to other healthy storage. Lost Partition Recovery covers a missing logical volume.
⚠ Warning: Install it on a drive different from the one where your data was lost to prevent overwriting.
Drecov is appropriate only when Windows recognizes stable storage with a plausible capacity but its files, volume, or partition are missing or inaccessible. It cannot fix a dead USB controller, supply power, repair an enclosure, or stabilize failing media. If the device drops offline during reads, stop scanning.
Step 1: Open Drecov and choose the original USB device
Install and launch PandaOffice Drecov from a healthy Windows disk, not the affected USB. Prepare a separate healthy destination with sufficient capacity. Select the original USB device or lost-partition entry and confirm its reported size before proceeding.
Step 2: Start Quick Scan and check familiar paths
Run Quick Scan first. Inspect expected folders and relevant file categories. Compare filenames, sizes, and dates. A damaged directory can separate files from their former paths, so keep credible candidates even when their names have changed.
Step 3: Use Deep Scan only while detection remains stable
Continue with Deep Scan if Quick Scan misses the needed files and the USB remains online at the correct capacity. End the scan if Windows disconnects it, read errors escalate, speed collapses, or physical symptoms appear.
Step 4: Filter, preview, and save away from the USB
Filter by file type, name, former location, size, or date. Preview representative supported files. A successful preview supports that sample’s readability but does not prove every page, frame, archive member, or linked item is intact. Recover selected data to the prepared healthy disk, never to the USB being examined.
Step 5: Locate and verify the recovery output
When the destination looks empty, browse its Recovery Folder and Drecov Folder directories. Open a varied sample, compare sizes, and verify critical documents and media. Only afterward should you initialize, format, run CHKDSK, rebuild a partition, or replace the enclosure. For broader logical-loss context, see the deleted, formatted, and lost-drive recovery overview.
⚠ Warning: Install it on a drive different from the one where your data was lost to prevent overwriting.
Verify the Fix at the Layer That Failed
After a port or driver correction, reconnect once and confirm that Device Manager shows no problem code. For a letter correction, open several existing files without editing them, then safely eject the device. Following recovery and later reformatting, copy disposable test data to the drive, eject it, reconnect it, and compare the files.
A single appearance in File Explorer is not enough. The USB should hold a stable identity and capacity through reconnects and ordinary reads. Recurring detection loss points back to hardware, power, cable, enclosure, or controller trouble.
Conclusion
For the exact error “usb not detected,” confirm the failure layer before changing storage. An undetected USB drive becomes easier to diagnose when you identify the last Windows layer that can see it. Begin with one safe physical test, read Device Manager evidence, and interpret Disk Management without writing metadata. If stable storage appears with missing data, Drecov can scan, preview, and recover available files to another healthy drive. It cannot repair physical USB faults, so unstable hardware should be disconnected rather than repeatedly scanned.
⚠ Warning: Install it on a drive different from the one where your data was lost to prevent overwriting.
