Fix ERROR_UNABLE_TO_INVENTORY_DRIVE (0X000010E5) on Windows

You're running a backup, a disk check, or just opening Disk Management, and Windows slaps you with ERROR_UNABLE_TO_INVENTORY_DRIVE (0X000010E5) — "Unable to retrieve the drive status." The drive might still show up in File Explorer. It might not. Either way, Windows tried to ask the drive "hey, are you okay?" and got nothing back.

That silence is the whole story. The drive isn't refusing to answer on purpose. The signal isn't making it, or the drive is too sick to reply. I've seen this error come up most often right after someone moves a tower to dust behind it, or after a laptop takes a tumble off a couch. Physical stuff first. Software second.

Work through these in order. Don't skip to the software fixes just because they're easier — you'll waste an hour chasing a cable problem with chkdsk.

Cause 1: Loose or failing SATA data cable

This is the number one cause and it's not close. SATA data cables work loose over time. Heat cycles, vibration from case fans, somebody bumping the desk — the connector creeps out of the port a millimeter and suddenly the drive drops off the bus for a split second. Windows notices, tries to inventory the drive, and gets nothing.

Laptop users, you're not immune. M.2 drives can work loose if the retention screw was never installed (I've opened machines where the drive is literally held in by the thermal pad). 2.5" SATA drives in laptops sit on a flimsy connector that flexes every time you pick the machine up by the corner.

What to do

1. Shut the machine down completely. Not sleep. Not hibernate. Full shutdown, then pull the power cord.
2. Open the case (desktop) or bottom panel (laptop).
3. Find the drive. Unplug the SATA data cable from both ends — drive side and motherboard side.
4. Look at the connector. Bent pins? Green corrosion? Replace the cable. They cost three dollars.
5. Plug both ends back in firmly. You should feel a small click. If it wiggles, it's not seated.
6. Check the power cable too. Molex-to-SATA adapters are notorious for this.
7. Boot up and open Disk Management (diskmgmt.msc). The drive should appear within a few seconds.

After booting, watch for the drive to vanish and reappear in File Explorer. If it does, swap the SATA cable for a known-good one before doing anything else. A $4 cable has fixed this error for me more times than I can count.

If the drive is an external USB enclosure, try a different USB port and a different cable. Preferably one that doesn't route through a hub. Bus-powered enclosures on a cheap hub cause this error constantly.

Cause 2: The drive itself is dying

If reseating the cable didn't fix it, run a SMART check before you assume it's software. A drive that can't respond to inventory requests is often a drive that's about to fail outright. Bad sectors pile up, the drive spends longer and longer on retries, and eventually it stops answering the controller altogether.

The warning signs line up like this: clicking or grinding sounds, the drive disappearing during large file transfers, boot times that stretch from twenty seconds to two minutes, and — the big one — this exact error during VSS snapshots or Windows Backup.

Check SMART status

Open an elevated Command Prompt and run:

wmic diskdrive get model,status,size,serialnumber

Look at the Status column. OK means it's happy. Anything else — Pred Fail, Error, Unknown — and you should back up data immediately.

For a deeper look, use CrystalDiskInfo (free, no install needed on the portable build). Check these attributes:

• Reallocated Sectors Count — any non-zero raw value is bad news.
• Current Pending Sector Count — sectors waiting to be remapped.
• Uncorrectable Sector Count — sectors the drive already gave up on.
• UDMA CRC Error Count — this one specifically points at cable or connection problems.

If CrystalDiskInfo shows the drive as Caution or Bad, stop troubleshooting the error and start copying files off. Do the important stuff first. Don't run a full image — the drive might die mid-copy.

The real fix when a drive is failing is replacement. Chkdsk won't save a drive that's physically degrading. It'll just make things worse by hammering the platters.

Cause 3: Filesystem corruption or a stuck volume mount

Once you've ruled out cable and hardware, look at the software layer. If the drive was yanked during a write, or the machine lost power mid-operation, the filesystem's dirty bit can stick. Windows then refuses to inventory the drive because it thinks the volume is in an unsafe state.

This is common on USB drives that got "Safely Removed" the lazy way — pulled out while the light was still blinking. The drive is fine, but the volume metadata is garbage.

Run a targeted chkdsk

In an elevated Command Prompt, identify the drive letter first:

diskpart
list volume
exit

Then run chkdsk against the affected letter. Replace D: with your drive:

chkdsk D: /f /r /x

Expect this to take a while on large drives — a 4TB spinning disk can run for eight hours. You'll see a progress percentage. Don't cancel it. If chkdsk reports "Cannot lock current drive," it's because something has the volume open. Reboot and let it run at startup.

Clear the readonly flag

Sometimes a disk gets flagged read-only after a botched removal. Check with:

diskpart
list disk
select disk 1
attributes disk

If you see "Current Read-only State: Yes," clear it:

attributes disk clear readonly

Then refresh Disk Management. The drive should inventory cleanly.

Reassign the drive letter

Occasionally the mount point itself is broken while the volume is fine. In Disk Management, right-click the volume, choose Change Drive Letter and Paths, and assign a fresh letter. Eject and reinsert if it's removable. This takes ten seconds and has fixed this error for me on more than one externally-encrypted drive that lost its association after a BitLocker hiccup.

Reset the VSS writers if backup triggered it

If the error only shows up during Windows Backup or a third-party imaging tool, VSS is likely stuck. From an elevated prompt:

net stop vss
net stop swprv
regsvr32 /s ole32.dll
regsvr32 /s oleaut32.dll
regsvr32 /s vss_ps.dll
vssvc /register
net start swprv
net start vss

Then run vssadmin list writers and confirm every writer shows State: Stable with no errors. If a writer still shows failed, reboot and check again.

Quick reference

One last thing: if the drive is a Samsung 870 EVO or 980 Pro made before 2022, check for firmware updates. Both lines had firmware bugs that caused random dropouts and inventory failures. Samsung's Magician software handles the update in about five minutes, and it's saved me from replacing perfectly good drives.