The 30-Second Fix: Restart the Remote Storage Service
That error code 0X000010FF is Windows telling you it tried to reach the remote storage service and nobody answered. Nine times out of ten, the service just isn't running. It happens after a reboot, a Windows update, or when a backup job kills it and doesn't restart it.
Do this first—it takes less than a minute:
- Press
Win + R, typeservices.msc, hit Enter. - Scroll down to Remote Storage Service (sometimes listed as Remote Storage).
- Right-click it and select Start. If it's already running, right-click and choose Restart.
- Now try whatever you were doing that gave you the error. Should be gone.
If it starts but then stops again, the service is crashing. That's a different animal, and we'll deal with that next.
The 5-Minute Fix: Check Dependencies and Set Startup to Automatic
The Remote Storage service doesn't work alone. It depends on the Remote Procedure Call (RPC) service and the Distributed Transaction Coordinator. If either of those is set to Manual or Disabled, your remote storage will flake out.
Here's the quick check:
- Open
services.mscagain. - Find Remote Storage Service, right-click, select Properties.
- Under the General tab, set Startup type to Automatic. That way it starts when Windows boots, not when something decides it's needed.
- Click the Dependencies tab and note what's listed.
- Check those services—make sure they're running and set to Automatic (or at least Manual if that's how they ship).
- If any of those services are stopped, start them first, then start Remote Storage Service.
I once had a client whose entire print queue died because someone had disabled the Print Spooler's dependency on RPC. Same idea here. A dependency gets turned off, and the whole chain falls apart.
Still getting the error? Time to go deeper.
The 15-Minute Fix: Registry and Workgroup Settings
If the service is running but the error persists, the problem is often that the remote storage name table is registered on a domain that doesn't exist. This happens on workgroup machines that used to be on a domain, or after a server rename.
Here's the registry path that controls this:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RemoteStorage\ParametersLook for a value named RemoteStorageNameTable or similar. It usually holds a list of domain names. If you see a domain that no longer exists, delete it. If the value is missing entirely, that's also a problem—the service doesn't know where to look.
To fix it, you can create the value with the correct name of your current domain or workgroup. But before you start poking the registry, back it up. Export the key to a .reg file so you can restore it if things go sideways.
Another thing to check: the Remote Storage feature might not be installed. It's not enabled by default on Windows 10 or Server 2019. You'd need to add it via Server Manager or Control Panel > Programs > Turn Windows features on or off. If it's not installed, the service will start and immediately stop, throwing this error.
To add it on Server:
- Open Server Manager.
- Click Add roles and features.
- Select Remote Storage under File and Storage Services.
- Install and reboot.
On a desktop OS, you'd find it under Remote Differential Compression or Remote Storage in the features list. Yes, it's kind of hidden.
When to Walk Away
If you've done all this and the error still shows up, there's a chance the remote storage server on the other end is offline or the share is gone. Check the network path. Can you ping the remote host? Can you access the share manually from Explorer? If not, the problem isn't your machine—it's the other side.
I once spent an hour chasing this on a client's Windows 10 box, only to find their NAS had died the night before. The service was fine. The hardware wasn't.
Bottom Line
Most times, a simple service restart clears 0X000010FF. If not, check dependencies and startup type. If that fails, it's registry or the feature isn't installed. Rarely is it anything more sinister. Good luck.