Fix PEERDIST_ERROR_NOT_LICENSED (0X00000FE0) Fast

I know seeing PEERDIST_ERROR_NOT_LICENSED (0X00000FE0) pop up is annoying — especially when you're just trying to update Windows or use a network feature. The error message "The SKU is not licensed" makes it sound like you need to buy something, but you don't. Here's the real fix.

The One Fix That Works

Skip the registry tweaks and third-party tools. This error happens because the Peer Distribution service (also called BranchCache) is running on a Windows edition that doesn't have the license for it — like Windows 10 Home, Windows 11 Pro Education, or older Windows 8/8.1 builds. Microsoft locks this feature to Enterprise and Education SKUs only.

Open Command Prompt as administrator. Hit the Start key, type cmd, right-click Command Prompt, and pick "Run as administrator." Then run these two commands:

sc stop PeerDistSvc
sc config PeerDistSvc start= disabled

The first command stops the service immediately. The second sets it to never start again. That's it. Close the window, restart your PC for good measure, and the error won't come back.

Why This Works

Peer Distribution (PeerDistSvc) relies on a feature called BranchCache. BranchCache is licensed only on Windows Enterprise, Education, and some Server editions. On Pro or Home, the service can still start if something triggers it — like a Group Policy setting or a misbehaving update — but it trips over the missing license and throws 0X00000FE0. By disabling the service, you stop it from attempting to initialize, which kills the error at the root.

Less Common Variations

Same error, different triggers. Here's where I've seen it outside the standard case:

• Windows Server with Desktop Experience: On Server 2016 or 2019 Standard, if you enable BranchCache via Server Manager but don't have the right CALs, this error can appear. Disable the service the same way, or uninstall BranchCache from Server Manager.
• Windows 11 Pro joined to Azure AD: Some Azure AD join policies force Peer Distribution to start. If the service won't stay disabled, check Group Policy for "Set-BitsTransfer" or "BranchCache" settings under Computer Configuration > Administrative Templates > Network > BranchCache. Set them to "Not Configured."
• After a feature update (like 22H2 to 23H2): Updates sometimes reset service startup types. If the error reappears after an update, just re-run the two commands. I've seen this on Windows 10 Pro 22H2 after the KB5026361 update.

How to Prevent It from Coming Back

Two things cause this error to return: Windows updates that reset service settings, and Group Policy pushing BranchCache back on. Here's how to lock it down:

1. Add a scheduled task that runs the two commands at startup. This catches any update that re-enables the service. Create a basic task in Task Scheduler, trigger "At startup," action "Start a program," program sc, arguments stop PeerDistSvc & sc config PeerDistSvc start= disabled.
2. Check local Group Policy (if on Pro or Enterprise). Run gpedit.msc, go to Computer Configuration > Administrative Templates > Network > BranchCache. Set all policies to "Not Configured." Don't just disable them — "Not Configured" prevents them from competing with the service's disabled state.
3. On Home editions, Group Policy isn't available. Just the scheduled task trick works reliably.

That's the whole thing. Two commands, one restart, and the error vanishes. No licensing headaches, no digging through logs. You're welcome.