Windows SXS Manifest Error 0X000036F0 Fix

You're installing some old software — maybe a POS system, a printer driver from 2015, or a company-specific app that hasn't been updated in years. Halfway through, you get that ugly dialog: "A declaration was not closed" with error code 0X000036F0. The install fails. Or worse, the app crashes on launch with a side-by-side configuration error.

I've seen this twice this year. Once with a QuickBooks 2013 installer on Windows 10. Another time with a custom database client some warehouse had been limping along with since 2012. The pattern's always the same: the software's manifest file — a tiny XML document that tells Windows which DLLs or runtime versions it needs — has a syntax error. Specifically, an XML declaration that wasn't closed. Something like <?xml version="1.0"?> is fine, but if a character got mangled and the ?> is missing, Windows rejects the whole thing.

Root Cause

The manifest file (app.manifest or embedded in the EXE/DLL) has a malformed XML declaration. The declaration must start with <?xml and end with ?>. If it's missing the closing ?> — or if that combination got corrupted (like ?> became ?> or just plain ?) — Windows' SXS parser throws error 0X000036F0. This isn't a real problem with the software's logic. It's a typo in a config file.

Step-by-Step Fix

This fix involves editing the manifest file. Back it up first. You're on your own if you mess it up.

Step 1: Locate the manifest file

If it's an installer, the manifest is often in the same folder as the setup.exe. Look for files named app.manifest, setup.exe.manifest, or something.exe.manifest. If it's an installed app, check the program's install folder (usually C:\Program Files\AppName\). You might need to enable hidden files to see it.

Step 2: Open the manifest in Notepad

Don't use Word or anything that adds formatting. Just Notepad. Right-click the file, choose Open with, pick Notepad.

Step 3: Scan for the XML declaration

The first line should look like this:

<?xml version="1.0" encoding="UTF-8"?>

Check if the line ends with ?>. If it's missing, add it. If the line is broken — like <?xml version="1.0" encoding="UTF-8"?!> — fix the closing sequence. If there's extra garbage after ?> on the same line, remove it. The declaration must be the very first thing in the file, no spaces or newlines before it.

Step 4: Save and test

Save the file. Try running the installer or app again. If it works, you're done. If not, continue.

If It Still Fails

Check the rest of the manifest for other XML errors. Look for unclosed tags — <dependency> without </dependency>. A stray > in the middle of a line can also cause this. Use an XML validator online (paste the content) to find the exact line. If you can't edit the manifest (maybe it's embedded in the EXE), your only real option is to find a newer version of the software or run it in compatibility mode with an older Windows version that's less strict about manifest syntax.

Had a client last month whose entire print queue died because of this — their old label printer software had a corrupted manifest from a bad update. Fixed it by uninstalling and reinstalling from the original disk, not the patched version.