Fix 0X000010CE Invalid Media Pool Error Windows Server

Yeah, that error is annoying. You're trying to run a backup to tape or manage media pools, and Windows Server just tells you the pool identifier is invalid. You know the pool exists, but the system doesn't agree. Let's get it sorted.

First Fix: Re-register Removable Storage Manager (RSM)

This works 9 times out of 10. Windows Server stores media pool info in a database managed by RSM. That database sometimes gets corrupted or desynchronized. Re-registering RSM rebuilds it.

Open Command Prompt as Administrator. Right-click Start, choose Command Prompt (Admin) or PowerShell (Admin).
Stop RSM service. Type:
```
net stop "Removable Storage"
```
After pressing Enter, wait for it to say "The Removable Storage service was stopped successfully."
Now re-register the RSM database. Type:
```
rsm.exe /REGDATABASE
```
You should see no output — that's normal. If you get an error, it usually means you're not running as administrator.
Restart the service:
```
net start "Removable Storage"
```
You'll get a confirmation message.
Try your backup or media management operation again. Often the error is gone after this.

What you should see: The error 0X000010CE no longer appears when you query or use media pools. If it persists, move to the next fix.

Second Fix: Delete and Recreate the Specific Media Pool

Sometimes just one pool is broken. Here's how to nuke it and start fresh.

Open Computer Management. Right-click Start, choose Computer Management.
Go to Storage > Removable Storage > Media Pools. You'll see a list of pools.
Find the pool that's causing the error. Right-click it, choose Delete. A confirmation box appears. Click Yes.
If it won't delete (you get another error), you need to force it via command line. Open Command Prompt as Admin again.
Type:
```
rsm delete /PAG:PoolName
```
Replace PoolName with the exact name of your pool. For example: rsm delete /PAG:BackupPool. You should see a message like "Media pool deleted successfully."
Now recreate the pool. In Computer Management, right-click Media Pools, choose Create Media Pool. Give it a name and set the properties you need.
Try your backup again.

Why this works: The pool's internal identifier in the RSM database was corrupted. Deleting it removes the bad entry. Creating a new one generates a fresh, valid identifier.

Why You Got This Error

The error code 0X000010CE is ERROR_INVALID_MEDIA_POOL. It means the pointer or ID your backup software (like NTBackup or Windows Server Backup) is using to reference a media pool doesn't match anything in the RSM database. Common triggers:

You restored a backup from a different server that had different media pools.
Someone deleted or renamed a pool while a backup job was queued.
The RSM database file (usually at C:\Windows\System32\NtmsData\NtmsTape.ntf) got corrupted after a crash or power loss.
You're using NTBackup on a newer Windows Server (like 2008 R2) and it's not fully supported — happens more often than you'd think.

Less Common Variations

Sometimes the error shows up in the Application Event Log with Event ID 123 or 124 from source "NTMS". You might also see it when trying to format a tape in the pool. A more rare variation happens with iSCSI tape drives — the pool ID gets scrambled after a reconnection. In that case, you need to uninstall and reinstall the tape device driver.

Another variation: The error occurs when running ntbackup.exe from command line with a /J (job) parameter that references a pool. If you're scripting backups, double-check that the pool name in the script matches exactly. Case matters. Spaces matter.

If you're on Windows Server 2012 or later, RSM is deprecated and might not be running at all. In that case, you need to enable the feature via Server Manager, or switch to a modern backup tool that doesn't rely on RSM storage pools.

Prevention Tips

Always stop backup jobs before renaming or deleting media pools. Never do it while a job is running.
Keep RSM database backups. You can back up the entire C:\Windows\System32\NtmsData folder after a clean boot.
On older servers (2003, 2008), reboot once a month. RSM can get flaky after weeks of uptime.
If you're using NTBackup, consider moving to Windows Server Backup or a third-party tool. NTBackup is a ticking time bomb on modern hardware.
Document your media pool names. Use simple names without special characters. Backslash, slash, or colon in a pool name? Asking for trouble.

Final thought: This error almost always points to a corrupt RSM database or a stray reference. The re-register trick fixes most cases. If you find yourself deleting media pools more than once a quarter, something deeper is wrong — probably a failing tape library or a flaky driver.