SXS XML_E_UNEXPECTEDENDTAG (0x36E3) Manifest Fix

The 30-Second Fix: Re-run the Installer or Update

Nine times out of ten, this error shows up during an install or a Windows update that got interrupted. The manifest file (usually app.manifest or a system file in C:\Windows\WinSxS) got cut off mid-write. Don't overthink it.

1. Close any open installers.
2. Reboot your machine. Not a restart from the Start menu — a full shutdown and power-on. This clears temp files locked by the OS.
3. Re-run the installer or Windows Update that triggered the error.

If the error vanishes, you're done. If it comes back, the manifest itself is corrupted — move to the next step.

The 5-Minute Fix: Check Common Manifest Locations

This error often hits when you're installing something that includes a side-by-side (SxS) assembly — think Visual C++ redistributables, .NET framework installers, or driver packages. The culprit here is almost always C:\Windows\WinSxS\Manifests.

1. Open an elevated Command Prompt (right-click CMD, Run as Administrator).
2. Run sfc /scannow. This checks system file integrity, including manifests. Let it finish — takes about 5 minutes on an SSD.
3. If SFC finds corrupt files but can't fix them, run DISM /Online /Cleanup-Image /RestoreHealth. DISM is more thorough and can pull fresh manifests from Windows Update.

Most users see this error when installing Microsoft Visual C++ 2015-2022 Redistributable. If that's your case, uninstall all Visual C++ redistributables via Programs and Features, reboot, then reinstall the latest version from Microsoft's official site. Don't use third-party download sites — they've got mangled manifests.

Still seeing the error? Time to dig into the raw XML.

The Advanced Fix (15+ Minutes): Manual Manifest Edit

This is for when the error is pinned to a specific app or driver, and you know the manifest file path from the error log. Check Event Viewer under Windows Logs > Application for the exact file. The error message usually says something like "Manifest parse error: End tag was not expected" and gives a file path.

1. Locate the manifest file. Common paths:
• C:\Program Files\YourApp\app.manifest
• C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-...
• C:\Program Files (x86)\Common Files\Merge Modules\
2. Back up the file first: copy original.manifest original.manifest.bak.
3. Open the .manifest file in Notepad++ or VS Code — not regular Notepad, it hides line breaks. Look for mismatched tags like <assembly> without a closing </assembly>, or a stray </dependency> where no <dependency> exists.
4. XML is strict. Every opening tag must have a closing tag, and they must nest properly. Common screw-ups: missing <assemblyIdentity> tags, or an extra </trustInfo> at the end.
5. Fix the tag structure. If you're not sure, compare the file against a known-good manifest from a working version of the same app — or use the Windows SDK's mt.exe (manifest tool) to validate: mt.exe -validate_manifest -manifest:yourfile.manifest.

Pro tip: If the manifest is in WinSxS, you can't edit it directly without taking ownership. Use takeown /f "C:\Windows\WinSxS\Manifests\yourfile.manifest" then icacls to grant yourself Full Control. Be careful — one wrong edit and you'll break the component store. If that happens, you're looking at a repair install or DISM /ResetBase.

Quick Reference: XML Manifest Structure

After editing, save the file and re-run the installer. If the error changes to a different SXS error, you've got another bad tag. Repeat the validate-fix cycle. If everything looks correct and the error persists, the manifest file isn't your problem — it might be a corrupted installer package. Download a fresh copy from the software vendor's official site.

I've seen this error most often with Visual Studio redistributables and .NET Framework 3.5 installers. For those, the fastest path is often DISM + SFC + fresh download — skip the manual edit unless you're sure the manifest is in a non-system location.