Fix 0X000036DC: Manifest Missing Parenthesis Error

Quick answer: The error means the XML in a manifest file is broken — missing a closing parenthesis in a <dependency> or <assemblyIdentity> tag. Rebuild the manifest using mc.exe and mt.exe, or reinstall the app that owns the manifest.

I ran into this one a few weeks back with a client running an old inventory management app on Windows 10 22H2. The app worked fine on Windows 7, but after an update, it threw 0X000036DC on launch. The culprit? A third-party installer had mangled the app's manifest file — dropped a closing parenthesis in an XML attribute. The OS side-by-side loader (sxs.dll) couldn't parse it, and the app crashed immediately.

This error pops up when the Windows manifest parser hits an XML element that's missing a closing parenthesis — typically in a version attribute or a publicKeyToken value. It's not a hardware issue. It's not a driver issue. It's a broken XML file inside your app's folder or the system's WinSxS store. Here's how to kill it.

Fix Steps

1. Find the broken manifest. The error message often includes a path. If not, open Event Viewer (eventvwr.msc), go to Windows Logs > Application, and look for the error. It will say something like "Manifest missing parenthesis in 'C:\Program Files\SomeApp\app.exe.manifest'."
2. Backup the manifest. Create a copy of that file before editing. Just in case.
3. Open the manifest in a proper XML editor. Not Notepad — use Notepad++, VS Code, or XML Notepad. Look for tags that are missing a closing ). Common spots: version="1.0.0.0" gets truncated to version="1.0.0.0, or publicKeyToken="abcdef1234567890" missing the last quote.
4. Fix the syntax. Add the missing parenthesis. Save the file.
5. Test the app. If it launches, you're done. If not, the manifest might be signed or embedded.
6. If embedded, rebuild it. Use the Windows SDK tools. First, extract the manifest: mt.exe -inputresource:app.exe;#1 -out:app.exe.manifest. Fix the XML, then re-embed: mt.exe -manifest app.exe.manifest -outputresource:app.exe;#1.
7. Still broken? Uninstall the app completely (use Revo Uninstaller or Geek Uninstaller to nuke leftovers), then reinstall the latest version from the vendor's site.

Alternative Fixes

If it's a system manifest: That's rare but happens after a bad update. Run sfc /scannow and dism /online /cleanup-image /restorehealth. Then reboot. If that doesn't fix it, you may need to restore from a system backup or do a repair install of Windows.

If it's a third-party app: Check the vendor's support site for a patched version. I had a client last month whose print queue management app had this error after a Windows 11 24H2 update — the vendor pushed a fix two days later. No point in hacking the manifest yourself if they've already fixed it.

If you can't edit the manifest: Use Process Monitor (procmon.exe) to see exactly which file is causing the error. Filter for .manifest and Result NOT SUCCESS. You'll see the path. Then copy a working manifest from a known-good installation of the same app (e.g., from a different PC). Overwrite the broken one.

Prevention Tips

• Never edit manifests with Notepad. It doesn't show encoding issues and can corrupt XML. Use a real editor.
• Test app updates in a VM first. This error often comes from botched installers that corrupt manifests during patching.
• Keep backups of C:\Windows\WinSxS before installing major updates. Use a system restore point. If the error comes from a system manifest, you can roll back quickly.
• For developers: Validate your installer's XML generation with xsd.exe /verify before shipping. A missing parenthesis in a manifest can brick the whole app on user machines.

Bottom line: 0X000036DC is a syntax error in XML — not a Windows bug. Find the manifest, fix the missing parenthesis, and you're back in business. If the manifest is embedded, use the SDK tools. If the app is old, upgrade it. You'll waste less time than debugging someone else's bad XML.