Fixing SXS XML Multiple Roots Error 0X000036E6

First thing: check the manifest file for extra root elements

Most of the time this error shows up because someone—or some installer—messed up the XML in a manifest file. The error literally says: only one top-level element is allowed. So if you see 0X000036E6, grab a copy of Notepad++ or any text editor that shows line numbers.

Start by figuring out which application or component is triggering the error. Look in the Windows Application Event Log—Event ID 33 or 59 from source SideBySide. The log entry usually includes the path to the bad manifest file. Had a client last month whose entire print queue died because of a corrupted printer driver manifest.

Once you have the file path, open it. Look for something like:

<assembly>...</assembly><assembly>...</assembly>

That's two root elements. Delete everything after the first closing tag and before the second opening tag. Save and test. If the manifest was supposed to have only one assembly element, you're done.

If you're not sure what the file should look like, check the original from a working machine or the application's installer. Don't guess—I've seen people delete the wrong part and break the app completely.

Second most common culprit: a corrupted or partially downloaded installer

If the error happens right after you install something, the installer itself might be bad. I've seen this with older Visual C++ redistributables and .NET framework installers. They download a bunch of files including manifests, and if one download gets cut short, you get a truncated XML file with multiple roots.

The fix: uninstall the offending program completely. Use Settings > Apps > Installed apps or the classic Control Panel. Then re-download the installer from the official source. Do not reuse the cached installer in your Downloads folder—delete it first.

For Visual C++ redistributables specifically, I've had luck running the vcredist_x86.exe /uninstall command from a command prompt to fully nuke it, then reinstalling fresh. The official Microsoft download pages have the latest versions.

Third scenario: a corrupted Windows component store (SxS)

Sometimes the manifest error comes from Windows itself—like when you're trying to run an old app and the side-by-side assembly store is borked. This tends to happen after a failed Windows update or a disk corruption.

Run these commands in an elevated command prompt:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

The DISM command checks the component store and fixes corrupted manifests. SFC then checks all protected system files. Let both finish—they take a while. After that, restart your machine and try the app again.

If DISM fails, you might need a Windows installation media to run DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess. I keep a USB stick with the latest Windows 10 ISO for exactly this reason.

One more thing: if the app in question is a custom in-house tool from a small business, the developer might have shipped a manifest with multiple roots. That's a code fix, not something you can patch on your own. Tell them to fix the XML.

Quick-reference summary table

That's it. Start with the manifest file—it's the most common and fastest fix. If that doesn't help, move to the installer, then to the component store. You'll have this error sorted in under an hour.