Fix PEERDIST_ERROR_NOT_INITIALIZED 0X00000FD6

Windows can't use Peer Distribution because the BranchCache service never started. The fix is to manually initialize the service and set it to auto-start.

Quick answer

Run net start PeerDistSvc as admin and set the BranchCache service to start automatically.

What's actually happening here

This error appears when Windows tries to use Peer Distribution—the feature that lets your PC grab Windows updates from other local PCs instead of Microsoft's servers—but the underlying BranchCache service never started. The error code 0X00000FD6 translates to "the supplied object has not been initialized," which is Windows' way of saying the BranchCache driver or service hasn't been loaded into memory. You'll see this most often when running DISM commands with /ScratchDir or when Windows Update tries to use peer caching on a fresh install of Windows 10 22H2 or Windows 11 23H2. The service exists, the binaries are there, but nobody told it to wake up.

Fix it – step by step

Open an elevated command prompt. Hit Win + X, choose Terminal (Admin) or Command Prompt (Admin).
Check the current state of the BranchCache service.
```
sc query PeerDistSvc
```
Look for STATE. If it says STOPPED, you've found the problem. If it says RUNNING, something else is wrong—see the alternative fixes below.
Start the service manually.
```
net start PeerDistSvc
```
This forces the service to initialize immediately. The reason step 3 works is that net start loads the service's driver and fires the initialization routine that sets up the peer distribution object. If it fails with "access denied," you're not running as admin.
Set the service to start automatically.
```
sc config PeerDistSvc start= auto
```
Without this, the service won't survive a reboot. The start= auto option tells Windows to launch the service at boot time, which prevents the error from coming back after a restart.
Reboot and test.
Run a command that previously threw 0X00000FD6—likely DISM /Online /Cleanup-Image /RestoreHealth or a Get-WindowsUpdate PowerShell cmdlet. The error should be gone.

What if the main fix doesn't work?

Two scenarios where the above fails:

Service refuses to start. If net start returns error 2 (file not found) or error 1075 (dependency failure), your BranchCache driver is corrupt or disabled. Open Services.msc, find BranchCache, and check the Dependencies tab. It needs HTTP and CryptSvc running. If those are fine, run sfc /scannow to repair missing BranchCache system files. On rare occasions, a group policy blocks Peer Distribution entirely—check gpedit.msc under Computer Configuration > Administrative Templates > Network > BranchCache.
Service starts but error persists. This points to a corrupted BranchCache store. Clear the cache with netsh branchcache flush, then stop and restart the service: net stop PeerDistSvc && net start PeerDistSvc. That wipes the database and forces a clean initialization.

Why you shouldn't just ignore this

Peer Distribution saves bandwidth on metered connections or slow networks. When it's broken, every PC in your house downloads the same Windows update from the internet instead of pulling it from a neighbor's machine. On a 50 Mbps connection with four PCs, that's hours of wasted bandwidth. Fixing this also clears the way for DISM repair operations that often hang with the same error.

Prevention – keep it running

After you apply the fix, run sc query PeerDistSvc | findstr START_TYPE to confirm it says AUTO_START. Don't let third-party "tweaking" tools disable this service—most of them blindly turn off BranchCache to save resources. If you're on Windows 11 Pro with group policy, set "Allow BranchCache for network files" to Enabled. That's it. The service stays initialized, and 0X00000FD6 never comes back.