USB flash drive not showing up in "This PC" at all... is it totally dead?

duyj

Guys, I'm literally crying right now. I was working on my final presentation, and suddenly my 64GB SanDisk drive just disappeared from "This PC". No warning, no "device disconnected" sound, nothing.

I unplugged it and plugged it back in—nothing. Try another USB port? Nope. Restarted my PC twice? Still nada. It doesn't even show up under "This PC" with a drive letter, it's just completely invisible. I have 3 months of unbacked-up project files on this thing. Is it completely bricked? Is there ANY way to save my data, or am I totally screwed? Please tell me there's hope...

ikjt

Data does not exist unless it exists in three places. Welcome to the "I learned about backups the hard way" club, membership is free and painful.

Does the drive light up or get hot when plugged in? If it turns into a mini hand-warmer, it’s cooked.

7xdu

ikjt Don't panic just yet, kid. "Not in This PC" doesn't automatically mean it's dead, Windows File Explorer is just dumb sometimes.

Do this right now:

Right-click the Start Button and open Disk Management (diskmgmt.msc).

See if your drive shows up there as "Unallocated", "RAW", or without a drive letter.

If it's there without a letter, right-click it -> Change Drive Letter and Paths -> assign a letter (like X🙂. Boom, fixed.

If it doesn't show up in Disk Management at all, check Device Manager under "Universal Serial Bus controllers". Let us know what you see.

zj7h

7xdu Assigning a drive letter only works if the partition table is intact and the OS actually mounts the block device. If the filesystem corrupted to RAW, forcing a letter won't magically fix the offset, and Windows will just prompt them to format it—which they absolutely SHOULD NOT do if they want their data back.

Also, telling a stressed user to mess with Disk Management without explicitly warning them not to click "Initialize Disk" is dangerous advice.

e0hd

zj7h Let us break down the failure modes systematically to help OP isolate the layer.

When a flash drive is plugged in, three distinct handshakes occur:

Physical/Power: 5V rail powers the controller and NAND memory.

USB Enumeration: Controller identifies itself to the host controller via Vendor ID (VID) and Product ID (PID).

Logical Mount: OS reads the Master Boot Record (MBR) or Partition Table to mount file systems (NTFS/exFAT).

If Device Manager (devmgmt.msc) lists an "Unknown USB Device (Device Descriptor Request Failed)", the controller isn't even completing Step 2. This usually indicates a blown fuse diode, dead crystal oscillator, or corrupted controller firmware. If it shows up under "Disk Drives" with its proper capacity, the hardware is alive, and only Step 3 failed.

7xdu

zj7h Fair point on the "Initialize" warning, shouldn't have glossed over that.

@OP, another quick practical sanity check before you start grieving:

Have you tried plugging it into the back USB ports directly on the motherboard (if you're on a desktop)? Front panel USB ports are notoriously bad for dying or dropping voltage, especially on cheaper cases. Also, try a Mac or a Linux live USB if you have one lying around. Windows USB drivers love to soft-lock until a full system power cycle (unplug PC power cord for 30s).

8nmj

e0hd Writing this down: diskmgmt.msc for volume checks, devmgmt.msc for hardware enumeration.

Quick question for Floor 4: If it shows up as "Unknown USB Device", is there any software fix, or is it purely a hardware repair job at that point?

ikjt

8nmj Software fix for broken physical hardware? Sure, just download more RAM while you're at it!

If the hardware controller can't speak to the motherboard, no software on Earth can talk to it. It's like trying to call a smartphone that got thrown into a blender.

e0hd

8nmj To answer your question: if it fails descriptor requests, software recovery tools (like Recuva or R-Studio) cannot interact with the drive because there is no logical interface exposed to the OS.

At that stage, professional data recovery labs have to desolder the NAND flash chip from the PCB and read the raw binary directly using a specialized hardware programmer (a process called "Chip-Off recovery").

zj7h

7xdu Testing on Linux is actually the only sane first step here. Windows error handling for failing USB mass storage is atrocious; it will freeze Explorer hanging on I/O calls.

Boot any Ubuntu live USB, run lsblk or dmesg -w in the terminal, and plug the drive in. dmesg will print kernel logs in real-time and tell you exactly whether the kernel sees the hardware connection or if it's throwing I/O bus errors. Stop guessing with Windows GUI tools.

8nmj

zj7h Adds dmesg -w and lsblk to notes under "Linux diagnostic tools for dead drives" 📝

Thanks! Learned more from this thread than my entire IT semester.

ikjt

zj7h Ah yes, telling a panicking user who doesn't know how to assign a drive letter to boot into a Linux Live environment and parse kernel logs via terminal. Classic Reddit tech elitism at its finest.

Next you're gonna ask OP to break out a multimeter and solder station.

7xdu

ikjt Lol, gotta agree here. Let's not scare OP away with terminal commands just yet.

@OP: Check Disk Management and the back USB ports first. If Device Manager shows nothing changing when you plug/unplug it, and the drive stays cold/dead on multiple computers, the hardware controller died. If the files are worth $300+, send it to a data recovery lab. If not, consider it a very expensive lesson in Cloud Backup 101. Update us with what you see in Device Manager!