Fix ERROR_SXS_INVALID_XML_NAMESPACE_URI (0x000036be) - Windows

You click an app and nothing happens. Or you get a popup with error code 0x000036BE and the message about an invalid namespace URI in the manifest. This is a side-by-side (SxS) error — Windows can't reconcile the application's internal manifest with what's on your system.

I've seen this most often with older games, business software like QuickBooks, or custom enterprise tools after a Windows update. The fix depends on what's broken. Here's the path I'd take, starting with the quickest attempt.

30-Second Fix: Reinstall Visual C++ Redistributables

More than half the time, this error is caused by a missing or corrupted C++ runtime. Windows uses these for app manifests. If one's busted, you get namespace errors.

Go to the official Microsoft download page for Visual C++ Redistributables. The direct link is: https://aka.ms/vs/17/release/vc_redist.x64.exe (for x64) or search for “Visual C++ Redistributable latest supported downloads”.
Download both vc_redist.x64.exe and vc_redist.x86.exe (even if you have a 64-bit system — some 32-bit apps need the x86).
Run each installer. Choose Repair if offered, otherwise let it install.
Restart your computer.

After restart: Try launching the app that gave the error. If it opens, you're done. If not, move to the next step.

5-Minute Fix: Clear the Side-by-Side Cache

The SxS cache (C:\Windows\WinSxS) stores component manifests. Sometimes a stale manifest with a bad namespace URI gets stuck there. Clearing the cache forces Windows to rebuild it.

Important: Don't delete the WinSxS folder manually. You'll break Windows. Use the built-in cleanup tool.

Open an admin Command Prompt. Press Windows Key, type cmd, right-click Command Prompt, choose Run as administrator.
Type the following command and press Enter:
```
DISM.exe /Online /Cleanup-Image /StartComponentCleanup
```
This tells Windows to scan the component store and remove superseded or broken manifests.
Wait for it to finish. It can take 2-5 minutes. You should see a message like “The operation completed successfully.”
Type this next command and press Enter:
```
sfc /scannow
```
This checks system files for corruption. Let it run fully — it might take 10-15 minutes.
After it finishes, restart your PC.

After restart: Launch the app. If the error persists, it's time to go deeper.

15+ Minute Fix: Manually Edit the App's Manifest

This is the nuclear option, but sometimes you have to. The app's manifest file contains an XML namespace URI that's wrong. You need to find and fix that URI.

Where to look: The manifest is usually embedded inside the .exe or .dll, or sitting next to it as a separate .manifest file.

Find the manifest file. Right-click the app's .exe, choose Properties, go to the Details tab. If there's a “Manifest” section, it's embedded. If not, look in the same folder for a file named appname.exe.manifest or appname.manifest.
If the manifest is embedded: You'll need a tool like Resource Hacker (free) to extract it. Open Resource Hacker, load the .exe, find the Manifest resource (usually under RT_MANIFEST), and save it as a .manifest file.
Open the .manifest file in Notepad. You'll see something like this at the top:
```
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
```
The namespace URI is urn:schemas-microsoft-com:asm.v1. If the app uses a different, invalid URI (like a misspelling or an old scheme), that's your problem.
Fix the namespace URI. The correct value is always urn:schemas-microsoft-com:asm.v1. If you see anything else, change it. Also check for xmlns:asmv3="urn:schemas-microsoft-com:asm.v3" — if present, that's fine, but don't add it if it's missing.
Save the file and, if extracted, re-inject it into the .exe using Resource Hacker (right-click the manifest resource, choose Replace Resource, select your fixed file).
Restart your PC and try the app again.

Warning: Editing manifests can break the app further if you change the wrong thing. Only change the namespace URI — don't touch anything else unless you know what you're doing.

When None of This Works

If you're still stuck, the app itself is probably incompatible with your version of Windows. Check the developer's website for an update, or run the app in compatibility mode (right-click .exe > Properties > Compatibility > run as Windows 7 or Windows 8). I've seen that work for older accounting software.

And if you're not comfortable editing XML or using Resource Hacker, skip the advanced fix. Reinstall the app from scratch — a clean install often replaces the broken manifest.