PEERDIST 0X00000FD4: Missing Data in Cache Fix

You're Seeing 0X00000FD4

It's annoying, I know. The error pops up when Windows tries to grab files from other PCs on your network but can't find them. The real fix is simpler than most sysadmins admit.

The Short Fix: Clear the Cache

Open PowerShell as Administrator. Don't bother with CMD, it's slower. Run:

net stop peerdistsvc
net stop PeerDistSvc
sc stop PeerDistSvc

# Clear the cache folder
rd /s /q "C:\Windows\ServiceProfiles\LocalService\AppData\Local\PeerDistPub"
rd /s /q "C:\Windows\Temp\PeerDist"

# Restart the service
net start PeerDistSvc

Close the PowerShell window. Reboot if you're paranoid — I've seen it work without a reboot 9 times out of 10.

Why This Works

The culprit here is almost always a corrupted cache. Windows BranchCache (which uses PeerDist) caches files it thinks you'll need again. If that cache gets stale or partial after a Windows update or network change, it throws 0X00000FD4. Deleting those two folders forces a fresh start. The service rebuilds the cache on next use.

When the Cache Clear Isn't Enough

If the error comes back, check these:

1. Service Dependencies

PeerDistSvc relies on the HTTP service. Run:

sc qc PeerDistSvc

Look for DEPENDENCIES. Should list HTTP. If it's missing, re-register:

sc config PeerDistSvc depend= HTTP

2. Group Policy Tweaks

Some enterprise setups block BranchCache via GPO. Open gpedit.msc, go to Computer Configuration > Administrative Templates > Network > BranchCache. Set "Turn on BranchCache" to Enabled. Then run gpupdate /force.

3. Windows Defender or Third-Party AV

I've seen Bitdefender and Kaspersky block the cache folder. Add an exclusion for C:\Windows\ServiceProfiles\LocalService\AppData\Local\PeerDistPub in your AV's settings.

Less Common Variations

Error Shows Only After Windows Update

This usually means the update changed the BranchCache version. Reset the service completely:

sc stop PeerDistSvc
sc delete PeerDistSvc

# Reinstall the service
cd C:\Windows\System32
PeerDistSvc.exe -install

Error on Domain-Joined PCs

Check the DNS settings. BranchCache needs proper name resolution. Run nslookup your-pc-name. If it fails, fix DNS first.

Error in Hyper-V or SQL Server

These apps sometimes call PeerDist directly. If the cache clear doesn't work, disable BranchCache per app:

sc config PeerDistSvc start= disabled

Prevention

Don't let the cache grow too big. Set a max cache size via Group Policy (Computer Configuration > Administrative Templates > Network > BranchCache > Set BranchCache cache size as percentage of disk). I set it to 5% on servers, 2% on workstations.

Also, avoid waking PCs from sleep when they're downloading updates. That's when the cache corrupts most often. Set power plans to stay awake during update windows.

One last thing: if you're using Windows 10 22H2 or Windows 11 23H2, there's a known bug with BranchCache. Microsoft has a hotfix (KB5031445) for it. Apply that if nothing else works.

Summary Table

That's it. You'll be back online in under 5 minutes. No need to reinstall Windows or run DISM scans — I've seen that waste hours. Stick to the cache clear, and you're good.