Remote Storage Recall Failed: 0x000010FE Fix

Quick answer

Restart the Remote Storage Service and check if the file's placeholder is corrupted. If the file is missing on the remote tier, you'll need to restore it from backup.

Why this happens

This error shows up when Windows Server's Hierarchical Storage Management (HSM) can't pull a file back from remote storage — like a tape library, cloud tier, or network share. It's common after a network timeout, when the remote storage service is down, or when the file's placeholder file gets corrupted (often from a botched defrag or chkdsk). I've seen it mostly on Server 2012 R2 and 2016 boxes with Storage Manager for SANs or third-party HSM tools.

Fix steps

1. Check the Remote Storage Service status — Open Services.msc, find "Remote Storage Service" or "Remote Storage Notification." If it's not running, start it. If it's stuck, right-click → Properties → change Startup type to Automatic, then restart the server.
2. Check the file's placeholder — Right-click the file → Properties → Attributes. If "Offline" is checked and grayed out, the file is stuck. Run fsutil file queryFileNameId C:\path\to\file.ext in an admin command prompt. If it returns "File not found" or weird IDs, the placeholder is toast.
3. Try recalling the file manually — Use PowerShell: Invoke-CimMethod -ClassName Win32_OfflineFile -MethodName Recall -Arguments @{FileName='C:\path\to\file.ext'}. This forces the recall outside the GUI. If it times out or errors, the remote storage is unreachable.
4. Check the remote storage connection — If you're using iSCSI, check the iSCSI initiator. If tape, check the tape drive. If cloud, check the network and auth. Use ping or Test-NetConnection to the remote endpoint.
5. Restart the server — I know it's basic, but I've seen this error go away after a clean boot when the service was hung. Do it during maintenance.

Alternative fixes if those fail

• Clear the offline file cache — Run reg delete HKLM\SYSTEM\CurrentControlSet\Services\RemoteStorage\Parameters /f (backup the key first). Then restart. This resets the HSM database. You'll lose the placeholder info for all offline files, but they'll re-sync on next access.
• Restore the file from backup — If the remote storage is dead (e.g., tape drive died, cloud provider lost data), you can't recall the file. Restore it from a backup to the local path, then delete the broken placeholder with fsutil sparse setflag C:\path\to\file.ext 0 and replace it.
• Remove and re-add the remote storage location — In Server Manager, remove the remote storage link, then add it again. This re-registers the HSM agent and often fixes the recall.

Prevention tip

Don't defrag drives with offline file placeholders — it corrupts them. Also set a regular task to recall and re-pin critical files every 30 days to make sure the remote storage is still breathing. If you're using cloud tiers, monitor the network latency. Anything over 100ms can cause timeouts.