PEERDIST_ERROR_NO_MORE (0X00000FD5): No More Data Available

Quick Answer

Restart the PeerDistSvc service and clear the BranchCache cache. That fixes 90% of cases. If it doesn't, disable BranchCache entirely—it's rarely needed outside enterprise networks.

What's Happening Here?

This error comes from PeerDistSvc, the Windows service behind BranchCache. BranchCache is Microsoft's way of caching updates or files from a central server to your local network—think of it as a local copy of stuff your coworkers keep downloading. When the cache runs dry or the service gets confused about what's available, it throws 0X00000FD5 (PEERDIST_ERROR_NO_MORE). Had a client last month whose entire update queue stalled on Windows 10 22H2 because of this—Windows Update kept showing "0% downloading" with no real error. The underlying trigger? Their IT guy had toggled BranchCache on for a remote office, then left it half-configured.

In plain English: the system says "I got nothing left to give you" when there's actually data waiting. It's a sync glitch, not a hardware failure. Usually self-corrects after a reboot, but if it's persistent, you need to nuke the cache.

Fix Steps (Primary)

1. Restart the PeerDist Service
   • Open Command Prompt as Admin. Type: net stop PeerDistSvc && net start PeerDistSvc
   • Check if the error clears. This flushes any stuck state.
2. Clear BranchCache Cache
   • In the same admin CMD, run: netsh branchcache flush
   • This wipes the local cache. It'll rebuild on next request.
3. Reset BranchCache Configuration
   • If flush doesn't cut it, run: netsh branchcache reset
   • Then restart the service again. This nukes the config back to default.
4. Verify Service Startup Type
   • Open services.msc, find PeerDistSvc. Set it to Automatic (if you use BranchCache) or Disabled (if you don't). Apply, restart.

Alternative Fixes If the Main One Fails

If none of that worked, BranchCache is probably misconfigured or not needed. Skip the hassle:

• Disable BranchCache entirely. Run: netsh branchcache set service mode=disable
• Then stop the service: net stop PeerDistSvc and set it to Disabled in services.msc.
• Reboot. Windows Update and file transfers will work fine without it—BranchCache only helps in domain-joined networks with a hosted cache server.

I've seen this error on standalone Windows 10 Pro machines that had BranchCache accidentally enabled via Group Policy or registry. One guy fixed it by deleting HKLM\SYSTEM\CurrentControlSet\Services\PeerDistSvc (after exporting a backup) and rebooting. But honestly, disabling the service is cleaner and safer.

Prevention Tip

Don't enable BranchCache unless you have a real need—like a remote office pulling large updates over a slow WAN link. If you do use it, ensure your hosted cache server is reachable and the cache size limit is reasonable (default is 5% of disk). Monitor event logs for PeerDist warnings before they pile up. For everyone else: leave it off. Windows Update works fine without it.