Fix ERROR_SXS_XML_E_MISSINGQUOTE (0X000036CE) Manifest Error

Quick Answer for Advanced Users

Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth in an admin command prompt. That fixes most cases. If that fails, check the Application event log for the exact manifest path and fix the missing double quote in the XML.

What This Error Actually Means

The ERROR_SXS_XML_E_MISSINGQUOTE (0X000036CE) error is a Windows Side-by-Side (SxS) manifest parsing failure. The OS is loading an XML manifest for an app or system component, and it hits a string literal without an opening quote. This isn't some deep mystery — it's a simple XML syntax error. The culprit is almost always a corrupted manifest file left behind by a botched Windows Update, a third-party installer that wrote bad XML, or an app that was manually tweaked. You'll see it as an app crash on startup with "The application was unable to start correctly (0xc000007b)" or similar, or as Event ID 33 in the System log with this error code. Most common on Windows 10 22H2 and Windows 11 Pro after the KB5034441 update, but I've seen it on Server 2019 and 2022 too.

Fix Steps (Start Here)

Don't bother reinstalling Windows or the app yet. Try these in order. They work 90% of the time.

1. Run System File Checker — Open cmd as admin, type sfc /scannow. Let it finish. It'll replace corrupted system files, including manifests in C:\Windows\WinSxS. Reboot when done.
2. Run DISM — If SFC finds issues it can't fix, run DISM /Online /Cleanup-Image /RestoreHealth. This pulls clean files from Windows Update. It can take 15-20 minutes. Don't cancel it.
3. Check the Event Log for the Exact File — Open Event Viewer, go to Windows Logs > Application. Look for events with source SideBySide and ID 33. The Details tab will show the manifest path, like C:\Program Files\SomeApp\app.exe.manifest or a system path under WinSxS.
4. Fix the Manifest Manually — Open the manifest file from step 3 in Notepad++. Look for a missing double quote — usually it's something like name=Value instead of name="Value". Add the quote and save. You'll need admin rights to write to system folders.
5. Reinstall the Affected Application — If it's a third-party app, uninstall it cleanly (use Revo Uninstaller if you're paranoid), reboot, and reinstall the latest version from the vendor.

If the Main Fixes Don't Work

Sometimes the manifest is deep in a protected system component and SFC/DISM can't fix it. Here are the options:

• Check for Pending Updates — Run dism /online /cleanup-image /startcomponentcleanup to flush the update cache, then re-run Windows Update. I've seen old update binaries ship bad manifests that SFC ignores.
• Restore from a Known Good Backup — If you have a system restore point from before the first crash, roll back. The error usually starts right after a specific update.
• Manual Replacement from Another Machine — Copy the same manifest file from an identical Windows version (same build, same update level). Compare the file version in Properties > Details. If they match, replace the bad one. High risk — don't do this unless you're comfortable with recovery options.
• In-Place Repair Install — Last resort. Download the latest Windows ISO, run setup.exe from within Windows, choose "Keep personal files and apps." This rebuilds the WinSxS store without nuking your data. Takes about an hour.

How to Prevent This from Coming Back

This error screams "bad update" or "sketchy software." You can't stop every bad manifest from ship, but you can reduce the odds:

One more thing — if you see this error after a .NET Framework update, run the .NET Framework Repair Tool from Microsoft. Those updates love to break manifests on 64-bit systems. I've fixed over a dozen workstations with that tool alone.