You're staring at a dialog box that says something like "The application has failed to start because its side-by-side configuration is incorrect" and buried in the event log you find ERROR_SXS_XML_E_UNEXPECTEDEOF (0x000036EA). This usually happens right after you install a new piece of software, run a Windows update, or try to launch an older app that's been sitting on your system for years. I've seen it most often when a program's manifest file is truncated—maybe the installer got interrupted, or a disk write glitched.
The root cause is simple: the manifest file—an XML file that tells Windows which DLLs and versions your app depends on—ends before it's supposed to. It's like reading a recipe that stops mid-ingredient list. The XML parser hits the end of file and throws a fit. This isn't a hardware failure or a sign your system is dying. It's a bad file, and you can usually pin it down in minutes.
Find the Culprit
First, you need to know which application is triggering the error. Check the Windows Application event log. Here's how:
- Press Win + R, type
eventvwr.msc, and hit Enter. - Go to Windows Logs → Application.
- Look for red error entries with source SideBySide.
- Read the message. It'll name the executable and often list the manifest path.
In my experience, the manifest path is usually something like C:\Program Files\SomeApp\app.exe.manifest or embedded in the EXE itself. If it's an embedded manifest, you'll see "Manifest file embedded in the executable" in the details.
Fix the Broken Manifest
Once you know the app, try these steps in order. Don't skip ahead—start with the quickest fix.
Step 1: Reinstall the Application
This sounds obvious, but I'm surprised how often people skip it. Uninstall the program completely, reboot, then reinstall. Make sure you download a fresh copy of the installer—don't use the one you already have, because it might be corrupt too.
If the problem started after a Windows update, try a system restore point from before the update. You'd be amazed how often that solves it.
Step 2: Run System File Checker
If reinstalling doesn't work, or you don't want to go nuclear yet, run SFC. This checks Windows system files, not third-party ones, but it's worth the two minutes.
sfc /scannow
Run that from an elevated Command Prompt (right-click → Run as administrator). It'll take a while. If it finds issues and fixes them, reboot and try the app again. If it says it couldn't fix something, move on.
Step 3: Manually Inspect the Manifest
If you're dealing with a standalone manifest file (not embedded), you can open it in Notepad and see if it's cut off. Look for a final closing tag like </assembly>. If you don't see it, that's your problem.
You can also use the Microsoft XML Editor or just validate it with any XML parser. But honestly, if the file is missing the end, you're better off reinstalling the app than trying to piece it together—unless you know exactly what you're doing.
Step 4: Clear the Component Store
Sometimes the Windows side-by-side cache gets corrupted. That's the WinSxS folder. You can't just delete it, but you can use DISM to fix the component store.
DISM /Online /Cleanup-Image /RestoreHealth
Again, elevated Command Prompt. This will take 10-15 minutes. Then run sfc /scannow again. Reboot and test.
What If It Still Fails?
If you've done all of the above and the error won't go away, you're likely dealing with a deeper issue. Check the event log again—if the error is appearing for multiple apps, the problem might be a corrupted shared manifest or a broken Windows update. In that case, I'd try a repair install of Windows using the Media Creation Tool. That keeps your files and apps but replaces all system components. It's a last resort, but it works.
Also, check if you have any security software that might be blocking or quarantining manifest files. I've seen a rogue antivirus quarantine a program's manifest because it looked suspicious. Add an exception or disable the AV temporarily to test.
One trick that's saved me a few times: if the app is 32-bit and you're on 64-bit Windows, check the SysWOW64 folder for missing system DLLs. Sometimes the manifest is fine but the DLL it references is missing. Install the Visual C++ Redistributable packages (all of them—2015, 2017, 2019, 2022). That fixes a surprising number of SxS errors.
Bottom line: this error is almost always a botched install or a corrupted file. Don't waste time tweaking registry keys or messing with permissions. Reinstall, run SFC/DISM, then escalate. You'll get it sorted.