Fix SXS manifest error 0x000036D8 unbalanced parens

You're staring at an error about unbalanced parentheses in a manifest file. Yeah, it's cryptic. But I've fixed this exact 0x000036D8 error for half a dozen small business clients, and you can do it in under 10 minutes.

The Fast Fix: Rebuild the Manifest Cache

1. Open an elevated Command Prompt — right-click Start, choose "Command Prompt (Admin)" or "Terminal (Admin)".
2. Run:

   sfc /scannow

   Let it finish, even if it says it found nothing.
3. Then run:

   DISM /Online /Cleanup-Image /RestoreHealth

   This downloads fresh system files. Takes 5-10 minutes.
4. Reboot. Try the app again.

If that doesn't work, the manifest itself is likely corrupt. You need to find the specific .manifest file. Error message usually shows the path — something like C:\Program Files\SomeApp\app.exe.manifest. Open it in Notepad. Look for mismatched parentheses in the <dependentAssembly> section. A common culprit: missing closing ) in a publicKeyToken attribute. Add it, save, restart the app.

Why This Happens

Windows side-by-side (SxS) manifests are XML files that tell the OS which DLL versions your app needs. When a parenthesis is unbalanced — like an extra ( without a matching ) — the XML parser chokes at load time. The error code 0x000036D8 maps directly to the XML error XML_E_UNBALANCEDPAREN. It's almost always caused by:

• A botched registry cleaner that corrupted the manifest cache
• An installer that wrote a malformed manifest
• A manual edit of a manifest file that went wrong

Had a client last month whose entire print queue died because a printer driver installer left an extra ( in its manifest. Rebuilt the cache with sfc and DISM, and everything came back.

Less Common Variations

1. The Manifest Isn't a File — It's Embedded

Some apps embed the manifest inside the .exe as a resource. You'll need a tool like Resource Hacker to extract the RT_MANIFEST resource, fix the parenthesis, and recompile. Skip this unless you're comfortable with binary editing.

2. The Error Shows Up Only After a Windows Update

Windows Update can replace system manifests. If the error started after KB1234567, roll back the update via Settings > Windows Update > Update history > Uninstall updates. I've seen this happen with cumulative updates that had manifest bugs.

3. The App Works on Another Machine

Copy the manifest from the working machine. Find the .manifest file in the app folder (usually same folder as the .exe). Copy it to the broken machine, overwriting the corrupt one. Reboot. Solved a QuickBooks issue for a client with this exact trick.

Prevention

• Don't run registry cleaners or CCleaner's registry tool. They've caused more problems for my clients than any single virus. Stick to disk cleanup.
• If you edit manifest files manually, use a programmer's editor like Notepad++ that highlights matching parentheses. Avoid Notepad — it won't show you the mismatch.
• Before installing major software, create a system restore point. Takes 30 seconds. Restore point saved me when a dodgy Adobe update broke my own machine last year.
• Keep Windows updates current. Microsoft patches manifest parsing bugs regularly.

That error 0x000036D8 is annoying, but it's rarely fatal. You'll be back up in minutes.