Fix ERROR_SXS_PROTECTION_CATALOG_FILE_MISSING (0x000036fe)

1. Corrupted Windows Component Store (WinSxS)

The culprit here is almost always a corrupted Windows Component Store (the WinSxS folder). This happens when a Windows update or a .NET Framework installation leaves the catalog files in a half-baked state. You'll see error 0x000036FE pop up when installing software or running certain apps that depend on side-by-side assemblies.

Don't bother with random registry tweaks or third-party cleaners — they rarely help. The real fix is to repair the component store using built-in Windows tools.

Run DISM and SFC in sequence

1. Open Command Prompt as Administrator (right-click Start -> Windows Terminal (Admin) on Win10/11).
2. Run this DISM command to repair the component store health:

DISM /Online /Cleanup-Image /RestoreHealth

This checks for corruption in the WinSxS store and pulls replacement files from Windows Update. If you're offline or behind a proxy, add /LimitAccess and point to a local install.wim source.

3. After DISM finishes (might take 15-30 minutes), run SFC to fix system files:

sfc /scannow

Let SFC complete — it'll replace any damaged catalog files. Reboot after it finishes. 9 times out of 10, that's all you need.

If you're on Windows Server 2016 or older, check the CBS.log after the DISM scan (%windir%\Logs\CBS\CBS.log). Look for entries like "0x000036FE" or "cat file missing" — they'll tell you exactly which catalog is busted.

2. Failed .NET Framework Installation

Another common trigger: a failed .NET Framework 3.5 or 4.x update. I've seen this most often on Windows 10 1809 and 21H2 after applying a cumulative update that didn't finish cleanly. The error shows up when any app tries to load a .NET assembly.

Re-enable .NET Framework via Windows Features

Skip the uninstall-reinstall dance — just toggle the feature off and on:

1. Press Win + R, type optionalfeatures, hit Enter.
2. Uncheck ".NET Framework 3.5 (includes .NET 2.0 and 3.0)" and ".NET Framework 4.8 Advanced Services".
3. Restart the PC.
4. Go back to optionalfeatures and re-check both.
5. Windows will reinstall the frameworks fresh, fixing any missing catalog files in the process.

If you get an error during re-enablement, use DISM to install .NET Framework 3.5 directly:

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:D:\sources\sxs

Replace D: with your Windows installation media or ISO mount point. The /All flag pulls in all parent features.

3. Manually Restore Missing Catalog File

Sometimes the catalog file is just straight-up missing from the WinSxS manifest folder. This happens after a failed uninstall of a third-party application that mucked with the assembly store. You'll see the exact catalog path in the Event Viewer under System logs, source "SideBySide".

Find and restore the catalog

1. Open Event Viewer (eventvwr.msc), go to Windows Logs > System.
2. Filter by Event ID 33 or Source "SideBySide". Look for the error message with the catalog file path.
3. Example: c:\windows\winsxs\manifests\amd64_microsoft-windows-a..._.cat
4. If you have a known-good backup or a working machine with the same Windows version, copy the missing .cat file from there to the same path.
5. If no backup exists, find the corresponding manifest file (same folder, same name but .manifest extension) and run:

icacls "C:\Windows\WinSxS\Manifests" /restore "C:\Windows\WinSxS\Manifests\acl.bak"

That's a long shot — usually you need to reinstall the component via a Windows Update standalone package. Download the latest Servicing Stack Update (SSU) and Cumulative Update for your Windows version from Microsoft Update Catalog, then install them manually. This forces Windows to regenerate the missing catalog.

Quick Reference Summary