STG_E_REVERTED (0x80030102) Drive Fix

Yeah, that STG_E_REVERTED error is annoying. You're working, then bam — Windows tells you the object that doesn't exist. Feels like the drive ghosted you. Let's get it back.

The Quick Fix: Dismount and Remount

Here's what actually works almost every time. Open Disk Management — right-click Start, select Disk Management. Find the drive showing the error (it'll probably have no drive letter or show as RAW). Right-click it and choose Change Drive Letter and Paths. Click Remove to dismount it. Then click Add, assign a drive letter. Done.

Had a client last month with a Seagate Backup Plus that threw this error every time they plugged it in. Dismount, remount, and it's been solid for three weeks. That's the fix.

If that doesn't work, try this command in an admin Command Prompt:

mountvol [drive letter]: /d

Then reassign the letter via Disk Management.

What's Actually Happening Here

Windows maintains a storage object for each mounted volume. That object holds file handles, buffer states, and metadata. STG_E_REVERTED (0x80030102) means Windows tried to access that object, but it got rolled back or invalidated. Usually because the underlying drive disconnected momentarily — USB cable wiggle, power spike, or a network drop for NAS drives. The driver sees the drive disappear, then reappear, but the object is toast. Dismounting forces Windows to create a new object from scratch.

This is different from a corrupted file system. If it were corruption, you'd see data read errors, not this specific code. So skip CHKDSK initially — it won't help here. I've seen people run CHKDSK for hours for nothing. Just dismount.

Less Common Variations

Sometimes the drive shows up with a drive letter but still errors. Happens with Thunderbolt docks or USB-C hubs with iffy power delivery. Try the mountvol command on that letter. If it fails, reboot the machine. That clears the storage stack completely. On server systems, I've seen this with SAN LUNs after a fabric failover. In that case, you might need to rescan the bus in Disk Management or use diskpart:

diskpart
list disk
select disk X
rescan

That forces the OS to re-enumerate the storage devices.

Another variation: the error shows in Event Viewer under source VolMgr with event ID 157. That means the disk driver reported a surprise removal. Check your USB or SATA cables — they might be loose. I had a user with an external SSD on a 6ft USB extension cable that caused this hourly. Swapped to a shorter, shielded cable — no more errors.

Prevention: Keep the Object Intact

Preventing this is about preventing disk drops. For USB drives: use a high-quality cable, avoid extensions, plug directly into motherboard ports (not front panel). For network drives: make sure your router or switch has stable power — a cheap UPS on the switch helps.

Also, always use Safely Remove Hardware before unplugging. Yeah, people ignore this, but it flushes caches and properly tears down the storage object. If you yank the cable, the object gets orphaned. Next access throws the error.

For NAS or SAN, check your iSCSI or FCoE connections for proper timeout settings. Increase the session timeout from default 60 seconds to 120 in the initiator settings. Gives the connection a bit of wiggle room during temporary glitches.

One final tip: if you see this error frequently on the same drive, run a quick health check with CrystalDiskInfo or SMART data. A failing drive can cause intermittent disconnects that trigger STG_E_REVERTED. Caught a dying WD Black 2TB that way — the drive was dropping out mid-transfer, causing the error every time. Replaced it, problem gone.

Bottom line: don't panic, don't run chkdsk first. Dismount and remount. If it keeps happening, chase the cable or the drive health. You'll be back to work in minutes.