Fix ERROR_SXS_XML_E_BADPEREFINSUBSET (0x000036EB)

What's actually happening here

ERROR_SXS_XML_E_BADPEREFINSUBSET (0x000036EB) shows up when Windows tries to load a side-by-side assembly, finds an XML manifest that references something that doesn't exist. The manifest says "this component needs version 1.2.3 of library foo.dll," but that version isn't installed, or the path is wrong. This usually happens after a botched Windows Update, a manual .NET framework install gone sideways, or restoring a system image from a different machine. I've seen it most often on Windows 10 20H2 and Windows 11 22H2 after cumulative updates that partially failed.

The error itself comes from the Windows Component Services (SxS) subsystem. It's not a user-facing app error; it'll crash apps that depend on the broken assembly. You might see it in Event Viewer as a side-by-side configuration error, or get a popup saying "The application has failed to start because its side-by-side configuration is incorrect."

Fix 1: Quick check — run SFC and DISM (30 seconds to 2 minutes)

This handles most cases. Don't skip it just because you think it's basic. The reason step 3 works is that SFC repairs corrupted system files by comparing them against the local component store. DISM repairs the component store itself.

1. Open Command Prompt as Administrator. Hit Start, type cmd, right-click, choose Run as administrator.
2. Run this command:
   

   sfc /scannow

   Wait for it to finish. It'll say either "Windows Resource Protection did not find any integrity violations" or "found corrupt files and repaired them."
3. If SFC found nothing or couldn't repair, run DISM next:
   

   DISM /Online /Cleanup-Image /RestoreHealth

   This pulls fresh component store files from Windows Update. If you're offline, you'll need a Windows installation ISO. Let it run — takes a few minutes.
4. Reboot. Try your app again.

When this works: If the manifest corruption is in a single system file and the local component store is healthy. About 60% of the time, this is all you need.

Fix 2: Check the specific app's manifest manually (5 minutes)

If the error returns, we need to find which manifest is broken. The error code alone doesn't tell you which app. Here's how to track it down.

1. Open Event Viewer. Press Win+R, type eventvwr.msc, hit Enter.
2. Go to Windows Logs > Application. Look for errors with Source: SideBySide or event ID 33, 35, 59.
3. Click one. The error message will say something like:
   

   Activation context generation failed for "C:\Program Files\SomeApp\app.exe". Dependent Assembly Microsoft.Windows.Common-Controls,processorArchitecture=amd64,type=win32,version=6.0.0.0 could not be found.

   That tells you exactly which assembly is missing.
4. Now go to C:\Windows\WinSxS\Manifests and find the manifest file that should contain that reference. The file name will match the assembly name (e.g., x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.0.0_none_...).
5. Open the manifest in Notepad. Look for the <assemblyIdentity> entry. Check that the version, processorArchitecture, and type match exactly. If you see a reference to a sub-assembly that doesn't exist in the C:\Windows\WinSxS\ folder, that's your problem.
6. The fix: reinstall the app that references the broken manifest. Uninstall it cleanly, reboot, reinstall the latest version from the vendor's site.

Why this works: The app installer will put the correct manifest and all required assemblies into WinSxS. Don't try to edit manifests manually — you'll break things worse.

Fix 3: Fallback — Windows Update Repair or In-Place Upgrade (15+ minutes)

If the above didn't help, the component store is likely deeply corrupted. This happens when a previous update didn't fully commit, or a disk error zapped the manifest directory.

1. Run the Windows Update Troubleshooter (Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update). It can reset update components.
2. Still broken? Do an in-place upgrade. Download the Windows 11 (or 10) Media Creation Tool from Microsoft's site. Run it and select Upgrade this PC now. It'll reinstall your current version while keeping apps and files. This replaces the entire WinSxS folder.
3. If that also fails (rare), you're looking at a clean reinstall. Backup your data first.

When to do this: If you see the error across multiple apps, or if DISM fails with "source files could not be found" even with an ISO. Skip the in-place upgrade if you're on an insider build or have heavy customizations — just clean install.

What NOT to do

• Don't delete anything from WinSxS manually. That folder is Windows' assembly cache. Removing files there can brick your system.
• Don't use registry cleaners. They don't fix manifest corruption and can break side-by-side configuration.
• Don't ignore disk errors. Run chkdsk C: /f first if you suspect a hardware problem. Corrupted manifests can come from bad sectors.