Fix 0XC000029E Remote Storage Media Error

Remote storage media error on Windows Server or client. Usually means a tape or removable drive failed. Check the device, drivers, and system event logs first.

Quick answer: The culprit is almost always a failing tape drive, removable disk, or the media itself. Check the device in Device Manager, look at the System event log for the underlying cause, then replace the media or the drive.

This error, STATUS_REMOTE_STORAGE_MEDIA_ERROR (0XC000029E), shows up when the Remote Storage Service (also called RSM on older systems or the storage service on newer ones) tries to read or write to a piece of media—a tape cartridge, a removable drive, or even a mounted VHD—and the device just doesn't respond correctly. You'll see this when you're using Windows Server 2003/2008/2012 with Removable Storage Manager, or if you're running a backup app that relies on the built-in volume shadow copy or media services. It's also common after you've loaded a new tape into a library and the drive hasn't been cleaned in a while. I've fixed this exact error dozens of times, and it's rarely a software bug. It's hardware or media.

The system logs will usually point to the device that's failing. Don't skip that step—it saves you from guessing.

How to fix the 0XC000029E error

Check the event logs first. Open Event Viewer (eventvwr.msc) and look under Windows Logs > System. Look for events from source RemoteStorage or Ntfs right before the error. They'll name the specific device or volume. Note the device name and the actual error (like a SCSI sense code). That tells you if it's a tape drive, a disk, or a controller issue.
Verify the media is clean and correctly seated. If it's a tape, eject it, check for dust or damage, and reinsert. For a removable disk, make sure it's firmly connected and not showing signs of wear. A dirty tape head produces exactly this kind of error.
Clean the drive. If it's a tape library, run a cleaning tape through it. It's the cheapest fix you'll ever do. I've seen this resolve 0XC000029E more times than I can count.
Update or reinstall the device driver. Go to Device Manager, find the storage device (e.g., a tape drive or storage controller), right-click, and select Update Driver. If that doesn't help, uninstall the device and scan for hardware changes. For older systems, the manufacturer's driver is better than the generic Windows one.
Run chkdsk on the volume if it's a disk. If the error is tied to a mounted volume, open Command Prompt as admin and run chkdsk /f /r on that drive. That will catch and mark bad sectors. But back up your data first—don't run this on a live production volume without a backup.
Remove and re-add the media in the storage service. In Windows Server, open Computer Management > Removable Storage (on older versions) or Storage > Removable Disks (on newer). Find the failed media, right-click, and select Dismount, then Mount. That resets the media state.

If that doesn't fix it

Sometimes the problem is deeper. Try these:

Replace the media. Tapes have a limited lifespan. If you've been reusing the same tape for months, it's probably worn out. Swap it with a fresh tape and try again.
Check the SCSI/FC connection. Loose cables or a failing HBA cause media errors. Reseat the cables, and if you have another port, try that.
Update firmware on the drive or controller. Manufacturers release firmware fixes for exactly these kinds of issues. Check the vendor's site.
Disable and re-enable the remote storage service. Open Services, find Removable Storage or Remote Storage, restart it. That's a long shot, but it's free.

Prevention

Once you get this fixed, don't let it happen again. Set up a regular cleaning schedule for tape drives—every 200 hours of use or monthly, whichever comes first. Monitor the event logs for early warnings—chances are the drive was throwing errors for days before this one appeared. And always keep spare media around. The one thing that guarantees this error comes back is ignoring the hardware until it fails completely.

One more thing: if you're running this on a modern Windows Server (2016 or later), the old Remote Storage Service is deprecated. You're likely using a third-party backup tool. In that case, the error message might come from the storage stack, but the fix is still the same—look at the hardware.