Fixing SXS Unknown Encoding 0x36BD in Windows

You're Stuck, I Get It

This error usually shows up when you try to install some old software or a driver, and Windows just throws this cryptic 0x36BD nonsense. It's not your fault. The culprit is almost always a corrupt or mismatched manifest file inside the Windows Side-by-Side (SxS) store. Don't bother reinstalling Windows — that's a waste of time.

Fix #1: Re-register the Assembly (Fastest)

Open an admin command prompt. Press Win+X, choose "Terminal (Admin)" or "Command Prompt (Admin)". Run this:

sfc /scannow

Let it finish. That fixes system files but not always the SxS store. If the error persists — and it often does — go straight to this:

DISM /Online /Cleanup-Image /RestoreHealth

Wait. DISM takes 15-30 minutes. Don't cancel it. After it finishes, reboot. Then run sfc again. This one-two punch fixes about 80% of cases.

If That Didn't Work — Re-register the Specific Assembly

You'll need the assembly name from the error log. Check Event Viewer under Windows Logs > Application. Look for event ID 33 or 63 from source "SideBySide". The log shows the assembly name like Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.0.0_en-us_*. Copy that full name.

Run this, replacing the name with your one:

regsvr32 /u "C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.0.0_en-us_*"
regsvr32 "C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.0.0_en-us_*"

Do that for both x86 and x64 versions if they're listed. Reboot.

Why This Works

The SxS store holds multiple versions of DLLs and manifests. Each manifest has an encoding declaration (UTF-8, UTF-16, etc.). When the encoding header is missing, corrupted, or mismatched with the actual bytes, Windows throws 0x36BD. Re-registering the assembly forces Windows to re-read and re-validate that manifest. Rebuilding the store via DISM does the same thing at scale.

Less Common Variations

Stuck on a Specific App

If only one app triggers this, check its manifest file. Look in the app's install folder for a .manifest file or a <appname>.exe.manifest. Open it in Notepad. The first line should be something like <?xml version="1.0" encoding="UTF-8" standalone="yes"?>. If the encoding attribute is missing or wrong (e.g., says UTF-8 but file is UTF-16), fix it. Save, then reinstall the app.

After a Windows Update

Sometimes a Windows Update breaks the SxS store. If DISM doesn't fix it, try removing the latest update. Go to Settings > Update & Security > Windows Update > View update history > Uninstall updates. Uninstall the most recent one. Reboot. If error's gone, block that update temporarily.

32-bit vs 64-bit Conflicts

Old 32-bit software on a 64-bit system causes this sometimes. The fix: install the app in compatibility mode. Right-click the installer, go to Properties > Compatibility, check "Run this program in compatibility mode for:" and pick Windows 7 or even XP SP3. Apply, run it.

Prevention: Keep the Store Clean

Do this once a month and you won't see 0x36BD again:

1. Run DISM and sfc as shown above.
2. Keep Windows updated. Missed updates corrupt the store over time.
3. Uninstall old software properly. Don't just delete folders — use Programs and Features or a good uninstaller like BCUninstaller.
4. If you're a developer, test your app's manifest with the Windows SDK tool mt.exe to validate encoding before deployment.

That's it. You've already seen the fix. Go run those commands and you'll be back in business in 30 minutes.