0X00001100 Remote Storage Media Error Fix

You're staring at error 0X00001100 and your backup just died. I've been there.

This error means the Remote Storage Service (RSM) hit a media error—a bad tape, a corrupt disk, or a drive that's about to fail. Don't panic. Here's the fix that works 9 out of 10 times.

The Quick Fix: Force a Media Check and Replace the Media

1. Open Removable Storage Manager
   Go to Start > Administrative Tools > Removable Storage. If you're on Windows Server 2016 or later, you'll need to install the Removable Storage Manager feature first (it's not installed by default).
2. Find the problematic media
   In the left pane, expand Libraries > Change Media. Look for any media with a yellow exclamation or red X. That's your problem.
3. Mark it as bad
   Right-click the media and select Properties. On the General tab, check Media is bad. Click Apply. You'll see a warning—that's normal. Click OK.
4. Don't use that media again
   Eject it. Label it as bad. Dispose of it properly. Do not try to reuse it.
5. Insert fresh media
   Put in a new tape or disk. The system should auto-detect it. If it doesn't, right-click the library and select Refresh.
6. Restart the service
   Open a Command Prompt as Administrator (Win + X > Command Prompt (Admin)). Run:
   

   net stop remotestorage
   net start remotestorage

   After these commands, you should see The Remote Storage service was started successfully.
7. Test the backup
   Run a manual backup job. If it completes without the 0X00001100 error, you're good.

Why This Works

RSM tracks every tape or disk in its database. When a sector goes bad, RSM flags the media with an error code (0X00001100). But it won't automatically stop using that media—it'll keep trying and failing. By explicitly marking the media as bad, you force RSM to skip it and move to good media.

This isn't a software problem. It's a hardware problem that the software is reporting. The fix is to remove the broken hardware from rotation.

Less Common Variations

1. The error appears on a brand new tape

This happens when the tape drive itself is dirty or failing. Run a cleaning tape first—a single pass. If the error persists, the drive's read/write head is damaged. Replace the drive.

2. The error happens with every tape in the library

You're looking at a drive problem, not a media problem. Check the SCSI or SAS cables. Reseat them. If the error continues, replace the drive.

3. The error shows up in the Event Log but backups still run

RSM logged a transient error—a single bad sector that was corrected. This is common with aging media. The fix is the same: mark the media as bad and replace it. If you ignore these warnings, you'll eventually get a backup failure.

4. Windows Server 2019 or 2022 with USB tape drives

Microsoft dropped RSM support for USB tape drives starting in Windows Server 2016. If you're using a USB tape drive, you'll see error 0X00001100 constantly. The real fix is to switch to a SAS or Fibre Channel drive. Or use third-party backup software that handles USB tapes directly.

Prevention Tips

• Replace tapes on a schedule. Most LTO tapes have a 10-15 year shelf life, but in active use, replace them every 2-3 years. Mark the install date on each tape.
• Run cleaning tapes regularly. Every 4-6 weeks for heavy use. More often if your environment is dusty.
• Monitor Event ID 101 and 201 from the Remote Storage Service. These warn about media errors before you get a full failure.
• Test your backups monthly. Not just verify—actually restore a file. Catching a bad tape early saves you from a 0X00001100 nightmare at restore time.
• Keep spare drives on hand. Tape drives fail without warning. Having a spare can cut your downtime from days to hours.

That's it. Mark the bad media, replace it, move on. If you're still seeing 0X00001100 after replacing both media and drive, you've got a cabling or controller problem. Check your SCSI or SAS bus termination. That's rare, but it happens.