Fix ERROR_SXS_MANIFEST_INVALID_REQUIRED_DEFAULT_NAMESPACE (0x36C3)

Quick answer: If you're an advanced user, open the broken app's manifest with mt.exe or a resource editor, confirm the <assembly> element has xmlns="urn:schemas-microsoft-com:asm.v1", and if it's missing or misspelled, patch it or reinstall the app.

Now the rest of us. ERROR_SXS_MANIFEST_INVALID_REQUIRED_DEFAULT_NAMESPACE is the Side-by-Side (SxS) subsystem telling you the app's manifest is malformed. Every Windows executable that uses SxS — which is most of them — carries a small XML file baked into its resources or sitting next to it as a .manifest file. That XML has to start with an <assembly> element that declares the asmv1 namespace. If it doesn't, Windows loads the manifest, hits the validation wall, and throws 0x36C3 before the app ever runs. No window, no splash screen, no log.

You'll see this most often after a bad app update, a half-finished MSI install, or when someone's tried to hand-edit a manifest to fix a different problem and dropped the xmlns attribute in the process. I've also seen it from antivirus tools quarantining a manifest file and leaving a zero-byte replacement behind — the file exists, it's just empty, and Windows treats an empty manifest as invalid rather than missing.

Confirm it's really this error

Before you start editing anything, make sure you're actually looking at 0x36C3 and not its cousin, ERROR_SXS_MANIFEST_FORMAT_ERROR (0x36B1). They look similar in the dialog.

1. Open Event Viewer (eventvwr.msc).
2. Go to Windows Logs > Application.
3. Look for a SideBySide event with ID 33 or 59. After clicking the newest one you should see Error code = 0x36c3 right in the description.
4. Note the full path to the executable it's complaining about. That's your target.

If the event says 0x36b1 or 0x36b9, stop here — you've got a different manifest problem and these steps won't help.

Fix 1: Reinstall the broken app

I'll be blunt: 90% of the time this is the real fix, because the manifest is either embedded in the EXE or shipped as a separate file, and hand-repairing either one is fiddly. Reinstall replaces the whole bundle cleanly.

1. Open Settings > Apps > Installed apps.
2. Find the app that Event Viewer named. Uninstall it.
3. Reboot. Don't skip this — some installers leave locked files behind until the next boot.
4. Download a fresh installer directly from the vendor. Don't reuse a cached copy from %TEMP% or a Downloads folder that might've been the source of the corruption in the first place.
5. Right-click the installer, choose Run as administrator, and complete the install.
6. Launch the app. After it opens you should see the main window within a few seconds. If you get the same SxS dialog, move to Fix 2.

Fix 2: Repair a standalone .manifest file

If the app ships a separate .manifest file next to the EXE (common with older enterprise software and any app built against the VC++ 8 or 9 CRT), you can fix this one by hand. Open the file in Notepad. You're looking for the opening tag. It should read exactly:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">

If the xmlns attribute is missing, misspelled, or points at asm.v2 or asm.v3, that's your problem. Replace the line with the correct version above, save as UTF-8 (Notepad's default in Windows 10 1903 and later), and try launching the app. After saving you should be able to double-click the EXE and have it start normally.

Fix 3: Patch the embedded manifest with mt.exe

If the manifest is embedded in the EXE — which you can tell because there's no .manifest file next to it — you'll need the Manifest Tool from the Windows SDK. Grab the SDK, install just the Windows SDK Signing Tools for Desktop Apps component, and open a Developer Command Prompt.

1. Extract the current manifest: mt.exe -inputresource:app.exe;#1 -out:app.manifest
2. Open app.manifest in Notepad and fix the xmlns as shown in Fix 2.
3. Save the file.
4. Write it back: mt.exe -manifest app.manifest -outputresource:app.exe;#1
5. Launch the app. It should start — if it doesn't, the manifest has a second problem and you're better off reinstalling.

Warning: patching a signed EXE will invalidate its Authenticode signature. Windows may now flag it under SmartScreen, and some antivirus tools will quarantine it. Only do this on software you own and can reinstall.

Alternative fixes if the above don't work

• Run the System File Checker. If the broken binary is a system file, SFC may restore it from the component store. Open an elevated Command Prompt and run sfc /scannow. After it finishes you should see one of three messages — "did not find any integrity violations", "repaired them", or "unable to fix". Only the second one means it helped.
• Reinstall Visual C++ redistributables. A surprising number of 0x36C3 errors trace back to a half-installed VC++ 2005 or 2008 runtime, because those ship manifests alongside the DLLs. Grab the matching redist from Microsoft's download page and reinstall it, then reboot.
• Check antivirus quarantine. Open your AV's quarantine list and look for the app's .manifest file. If it's there, restore it and whitelist the folder. An empty manifest file left behind by a partial restore is a classic trigger for this error.
• Use System Restore. If the app worked last week and doesn't now, roll back to a restore point from before the break.

Preventing it from coming back

Don't hand-edit manifests unless you have to. Every guide that tells you to "just tweak the manifest to force admin" is one attribute away from causing this exact error. Use the vendor's supported mechanism — a shortcut with “Run as administrator” checked, or the app's own settings — instead.

The other thing: don't let your AV auto-quarantine files inside Program Files without review. Add an exclusion for your critical app folders. It's a one-minute change that saves you an afternoon of chasing SxS errors.