Fix 0x000036D6: Missing > in Manifest File

Quick answer (for advanced users): Open the manifest file (usually in the app folder) with a text editor, find the line where the > is missing, add it back, save. Or just reinstall the program.

This error shows up when Windows tries to load a program but can't read its manifest. The manifest is a small XML file that tells Windows what version of the C++ libraries the program needs. Without the closing > on a tag, Windows stops and throws error 0x000036D6. I've seen this most often with old installers from 2010-2015, like some printer drivers or legacy games. The real trigger is a corrupted or badly written XML file inside the program's folder.

How to Fix It Step by Step

Find the program's install folder. Right-click the program shortcut and pick "Open file location." Or check C:\Program Files\[Program Name] or C:\Program Files (x86)\ [Program Name].
Look for files ending with .manifest. You'll see files like program.exe.manifest or setup.exe.manifest. If there are multiple, start with the biggest one.
Make a backup. Copy the manifest file to your desktop. If the fix goes wrong, you can put it back.
Open the manifest in Notepad++ or any plain text editor. Don't use Word or WordPad—they add hidden characters. Notepad++ works great and shows line numbers.
Look for a line that ends without >. The error message might say "Expecting '>'" and give a line number. Scroll to that line. Common spots: tags or tags. You'll see something like without the >.


  Add the missing >. For example, change  to . Check the tag above and below to see how they close.

  Save the file. Press Ctrl+S.
  Run the program again. If the error is gone, you're done. If not, check other manifest files nearby.



After you save, Windows won't complain because the XML is now valid. The program should start normally.

Alternative Fixes If That Doesn't Work


  Reinstall the program. Uninstall it from Control Panel > Programs and Features, then download the latest version from the maker's site. This replaces the bad manifest with a fresh one.
  Run the installer as administrator. Right-click the installer and pick "Run as administrator." Some old installers need admin rights to write the manifest correctly.
  Try compatibility mode. Right-click the program's .exe file, choose Properties, go to the Compatibility tab, check "Run this program in compatibility mode for" and select Windows 7 or Windows XP (Service Pack 3). Click OK.
  Delete the manifest file. If the program works without it, you can delete the .manifest file. Some apps don't actually need it. Back it up first.
  Use SFC and DISM. Open Command Prompt as admin, run sfc /scannow. After it finishes, run DISM /Online /Cleanup-Image /RestoreHealth. This fixes Windows system files if the problem is deeper.


Prevention Tip

The best way to avoid this is to only install programs from official sources. Old shareware sites sometimes host cracked installers with broken manifests. Also, if you edit manifest files manually, always check the XML after saving. A missing > can take 10 minutes to find if you don't use a validator. Use an online XML checker or Notepad++ with XML plugin to catch these mistakes.

One more thing: Windows Update sometimes replaces manifest files for Microsoft programs. If this error pops up after an update, you can roll back the update or run System Restore to before the update installed.