PEERDIST_ERROR_OUT_OF_BOUNDS (0X00000FDD) fix

Quick answer

Stop the Peer Distribution service, delete the cache folder at C:\Windows\ServiceProfiles\LocalService\AppData\Local\PeerDist, then restart the service. No reboot needed.

Why this happens

The PEERDIST_ERROR_OUT_OF_BOUNDS error (0x00000FDD) means the BranchCache service tried to read data beyond the end of a cached chunk. Windows uses BranchCache to accelerate file transfers over LANs by splitting files into chunks and caching them across peers. When the internal index of those chunks gets corrupted — maybe from a partial download, a disk write error, or a hard shutdown — the service tries to access a chunk that doesn't actually exist.

What's actually happening here is the cache metadata got misaligned with the actual data on disk. The error code 0x00000FDD translates to PEERDIST_ERROR_OUT_OF_BOUNDS, defined in peerderr.h as "An operation accessed data beyond the bounds of valid data." The service itself can't fix this — it just fails and logs the error. You'll typically see this when using SMB file sharing with BranchCache enabled, or running BITS transfers that rely on PeerDist.

Fix steps

1. Stop the Peer Distribution service. Open Command Prompt as admin and run:
   net stop PeerDistSvc
   The service stops instantly. No spinning wheel.
2. Wipe the cache folder. Run:
   rmdir /s /q C:\Windows\ServiceProfiles\LocalService\AppData\Local\PeerDist
   This deletes the corrupted index and all cached chunks. You don't need to delete individual files — the whole folder is expendable.
3. Start the service again. Run:
   net start PeerDistSvc
   The service creates a fresh cache folder automatically on first access.

That's it. The error shouldn't appear again until the cache gets corrupted. Takes about 10 seconds total.

Alternative fixes

If the error returns within a few hours, the corruption might be caused by something else. Try these in order:

• Check disk integrity. Run chkdsk C: /f from an admin prompt, then reboot. A failing disk sector can corrupt the cache as it's written. If chkdsk finds bad clusters, replace the drive.
• Disable BranchCache entirely. If you don't use BranchCache (most home users don't), just turn it off:
  sc config PeerDistSvc start=disabled
  Then restart. You lose nothing — BranchCache is only useful on managed LANs with multiple machines.
• Update network drivers. Specifically the NIC driver. BranchCache relies on the network stack for chunk ID generation, and a buggy driver can produce overlapping chunk boundaries. Check Device Manager for a driver update, or go straight to the manufacturer's site.

Skip the registry hacks — they don't apply here. This error is purely about corrupt cache data, not service configuration.

Prevention

Prevent re-corruption by avoiding forced shutdowns during large file transfers. BranchCache writes chunk metadata while files are in flight, and a hard power-off at that moment is the primary cause. Also, run chkdsk monthly if you're on an older HDD — SSDs are less prone to this, but not immune.

If you're on a single PC and not using BranchCache for anything, the safest move is to leave the service disabled. It's off by default in Windows 10 Home and Pro — only gets enabled if you manually turned it on or joined a domain that pushes the policy.