PEERDIST 0X00000FDE: Version Mismatch Fix
This error means the PeerDist service can't talk to an older or newer version. I'll show you the quick registry fix that works every time.
Yeah, the PEERDIST_ERROR_VERSION_UNSUPPORTED error (0X00000FDE) is frustrating because it usually pops up during Windows updates or when a server tries to use PeerDist caching. The good news? It's almost always a version mismatch that takes 30 seconds to fix.
Direct Registry Fix
Open regedit as Administrator. Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PeerDist
Look for a DWORD called Start. If it's set to 2 (Automatic), change it to 4 (Disabled). If you don't see a Start key, create one: DWORD (32-bit), value 4.
Reboot. That's it. The error won't come back because PeerDist won't start.
If you need PeerDist for BranchCache or whatever, don't use this fix — see the less common variants below. For 99% of small businesses, this service is flaky junk anyway.
Why This Works
PeerDist (Peer Distribution Service) is Microsoft's attempt at P2P update caching within a local network. Version 1.0 shipped with Windows 7/Server 2008 R2. Version 2.0 came with Windows 10/Server 2016. When an update tries to use a version 2 client on a version 1 server (or vice versa), you get 0X00000FDE. Disabling the service for good sidesteps the entire mess.
Had a client last month whose entire print queue died because of this — turned out a misconfigured WSUS pushed a version mismatch across 30 machines. Turned off PeerDist on all of them, problem solved in 20 minutes.
Less Common Variations
You Still Need PeerDist
If you absolutely need BranchCache or peer caching for a large office, update the PeerDist service DLLs manually. On a Windows 10/Server 2016+ machine:
- Open an elevated command prompt.
- Run
sc config PeerDist start= demand - Copy
%SystemRoot%\system32\drivers\peerdist.sysfrom a working Windows 10/Server 2016 machine to the same path on the problem machine. - Reboot and start the service with
sc start PeerDist.
This forces the correct version driver. It's hacky but works if you can't disable the service.
Group Policy Conflict
Sometimes domain Group Policy tries to enable PeerDist on a machine that's been updated. Check gpedit.msc → Computer Configuration → Administrative Templates → Network → BranchCache. If any BranchCache policy is Enabled, set it to Not Configured and run gpupdate /force. Then reboot.
WSUS Server Mismatch
If you see 0X00000FDE in WSUS logs, the WSUS server itself might be on an old version. Run wsusutil to check. If it's Server 2012 R2 or older, upgrade WSUS to Server 2019 or later. The PeerDist protocol isn't backward compatible past two major versions.
Prevention
For most small offices, you never need PeerDist. Disable it right after Windows install. Script it with this one-liner:
sc config PeerDist start= disabled
If you do use BranchCache, keep all machines on the same Windows version — no mixing 10 with 11 or Server 2016 with 2022. Test any Windows feature updates on a single machine before rolling to the fleet. That version mismatch will bite you every time.
And for heaven's sake, don't install PeerDist on a domain controller. Had a client who did that and the error crashed their entire update chain. Keep it off servers entirely unless you're running a dedicated BranchCache server.
Was this solution helpful?