SXS XML_E_INTERNALERROR 0x000036D9 Fix

What You're Looking At

That 0x000036D9 error is a side-by-side (SXS) manifest parse failure. Windows can't read the XML manifest file for an application — usually a game or an old business tool. You'll see it right when the app starts, often after a Windows update or a reinstall of Visual C++ redistributables.

The culprit here is almost always a corrupted system file or a botched app installation. Don't bother reinstalling the OS — that's overkill 9 times out of 10. These three steps will handle it, starting with the fastest.

Fix 1: Quick SFC Scan (30 seconds)

Open a Command Prompt as Administrator — hit Win, type cmd, right-click and pick "Run as administrator". Then run:

sfc /scannow

Let it run. It checks core system files, including the SXS store. If it finds corruption, it'll pull a clean copy from the local cache. Reboot after it finishes. Try launching the app again.

If SFC reports "Windows Resource Protection did not find any integrity violations", move to the next fix. Same if it finds errors but the problem persists — SFC can only fix so much when the store itself is shot.

Fix 2: DISM + Component Store Repair (5 minutes)

When SFC isn't enough, you need to fix the component store that SFC relies on. Still in that admin command prompt, run:

DISM /Online /Cleanup-Image /RestoreHealth

This takes 3–5 minutes. It downloads fresh files from Windows Update to repair the SXS store. If you're offline or on a slow connection, use:

DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess

Swap the source path to a Windows install USB or ISO. After DISM finishes, run sfc /scannow again — it'll catch what DISM fixed. Reboot.

Pro tip: if DISM fails with error 0x800f081f, your source files are missing. Mount a Windows ISO or use a working PC's C:\Windows\WinSxS folder as the source.

Fix 3: Nuke the Problematic App (Hard Reset — 15+ minutes)

If the first two fixes didn't work, the problem is likely in the app's own manifest files, not the system. You've got two roads here.

Option A: Clean Reinstall the App

1. Uninstall the application from Settings > Apps > Installed apps.
2. Reboot the machine. Yes, a full restart.
3. Reinstall using the latest installer — grab a fresh copy, don't use cached files.
4. If the error was tied to a Visual C++ redistributable (common with older apps), uninstall all Visual C++ packages, then reinstall the latest from Microsoft's site.

Option B: Clean Boot + Registry Check

Sometimes a third-party service or shell extension corrupts the manifest load. Do a clean boot:

1. Run msconfig.
2. Go to Services tab, check "Hide all Microsoft services", then click "Disable all".
3. Go to Startup tab, open Task Manager, and disable everything.
4. Reboot. Try the app. If it works, enable services one-by-one to find the culprit.

Also check the registry at HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations. Delete any entries that reference the problem app — leftover rename operations can hose manifest loading.

When to Give Up and System Restore

If you've gone through all three and the error is still there, you're looking at a deeper corruption. Roll back to a restore point from before the problem started. Open System Restore from the start menu, pick a point dated before the error showed up. Takes about 10 minutes.

If no restore point exists, consider a repair install (in-place upgrade) using the Windows Media Creation Tool. It keeps your files and apps but replaces all system files. That's a last resort, but it works.

One more thing: If you're on Windows 11 22H2 or later, check for the KB5023706 update. That patch specifically addressed SXS manifest parsing issues on some systems. Install it if missing.

That's it. Start with SFC, hit DISM, then nuke the app. You'll be done in under 20 minutes, most likely at step one.