Fix 0x000036F6: sxs standalone attribute must be yes or no

Cause 1: Typo in the manifest XML — 'standalone' is misspelled or has wrong attribute

What's actually happening here is the Windows side-by-side (SxS) loader is parsing the application manifest and hitting the <?xml?> processing instruction. The standalone attribute inside that PI can only take "yes" or "no" as values — and it must be spelled exactly standalone, lowercase, no hyphens, no extra characters.

The exact error code 0x000036F6 translates to ERROR_SXS_XML_E_INVALID_STANDALONE. The error message literally says: "The stand-alone attribute must have the value 'yes' or 'no'" — note that Microsoft's own error message uses a hyphen, but the actual attribute in XML is standalone (no hyphen). That mismatch has confused a lot of people. Don't trust the hyphen in the error text; the attribute name in the XML file is standalone.

This usually happens when someone hand-edited a manifest file, or a third-party installer patched it badly. I've seen this most often after running a game mod installer or a cracked DLL wrapper on Windows 10 22H2 and Windows 11 23H2.

Fix: Locate and repair the manifest file

1. Find the application that's crashing. Right-click its shortcut → Open file location.
2. Look for a .manifest file with the same base name as the .exe. Example: for game.exe, look for game.exe.manifest in the same folder.
3. Open the manifest with Notepad (or any text editor). Don't use Word or WordPad — they can add invisible BOM characters that break things.
4. Look at the very first line. It should look like:
   
   Or with standalone="no". Both are valid.
5. Check for these common mistakes:
   • stand-alone="yes" — hyphen is wrong
   • standlone="yes" — missing 'a'
   • stand alone="yes" — space is wrong
   • standalone=yes — missing quotes (must have double quotes)
   • standalone="true" — must be 'yes' or 'no', not 'true' or 'false'
6. Correct the attribute and save. Restart the application.

If you can't find a standalone .manifest file, the manifest might be embedded inside the .exe as a resource. That's trickier — you'll need a resource editor like Resource Hacker. But 90% of the time, it's an external manifest file.

Cause 2: Corrupted manifest from a failed update or disk write error

The reason Cause 1 is most common is that humans make typos. But sometimes the manifest file gets corrupted at the byte level — a power loss during a write, a failing hard drive, or a bad sector can flip a byte. In that case, the manifest might have looked correct when you opened it in Notepad, but the file on disk contains a null byte or a garbled character that the XML parser rejects.

Fix: Check file integrity and replace with a known-good copy

1. Open Command Prompt as Administrator.
2. Run sfc /scannow to check system files. This won't touch third-party manifests, but it's worth ruling out system corruption.
3. If the manifest belongs to a program you installed, reinstall the program. The installer should overwrite the messy manifest with a clean one.
4. Alternatively, download a fresh copy of the manifest from the software publisher's site — if they provide it separately.

I've also seen this happen when antivirus software (looking at you, McAfee) quarantines part of the manifest and leaves a stub file that's only half-written. In that case, disable real-time scanning temporarily, reinstall the app, then re-enable the AV.

Cause 3: Manifest references a missing or broken XML declaration entirely

Less common, but I've seen it: the manifest file starts with a blank line, or with a comment, before the <?xml?> declaration. XML standards are strict — the declaration must be the very first thing in the file. No BOM, no whitespace, no blank line before it.

Fix: Strip leading bytes

1. Open the manifest in a hex editor (like HxD, free).
2. Check the first three bytes. For UTF-8 without BOM, they should be 3C 3F 78 — that's the ASCII for . If you see EF BB BF at the start, that's a UTF-8 BOM. Some XML parsers choke on it.
3. If you see a BOM, delete those three bytes and save as UTF-8 without BOM.
4. If the file starts with a newline (0D 0A or 0A), delete those too.