Fix STATUS_SXS_MANIFEST_FORMAT_ERROR 0XC0150005

Quick Answer for Advanced Users

Run these two commands from an elevated Command Prompt, in this order: DISM /Online /Cleanup-Image /RestoreHealth then sfc /scannow. Restart. If that doesn't fix it, reinstall the latest Visual C++ Redistributable packages from Microsoft's official site.

What This Error Actually Means

Error code 0XC0150005 shows up when Windows can't read a side-by-side (SxS) manifest file. These manifest files tell Windows what DLL versions and dependencies an application needs. When the file is missing, has the wrong encoding, or starts with garbage instead of the proper XML declaration, you get this error.

I've seen this most often after someone installs a game or business app that bundles a broken Visual C++ redistributable, or after a Windows Update that didn't finish correctly. You might see it on launch of programs like Adobe Reader, older Autodesk products, or even some Steam games. The app crashes immediately with that error code in the Event Viewer.

Fix Steps (Try These in Order)

Run DISM and SFC
Press Windows key, type cmd, right-click Command Prompt, select "Run as administrator".
Type this and press Enter: DISM /Online /Cleanup-Image /RestoreHealth
Wait — it takes 5 to 15 minutes. You'll see a progress bar. Let it finish completely.
After that, type: sfc /scannow and press Enter. This scans and fixes corrupted system files.
When it's done, restart your PC.
Reinstall Visual C++ Redistributables
Go to Microsoft's official download page for Visual C++ Redistributable packages. Download both the x86 and x64 versions of the latest (2022) package. Uninstall the old ones first: go to Settings > Apps > Installed Apps, look for "Microsoft Visual C++ Redistributable", uninstall every version you see. Then install the fresh downloads. Restart.
Check the Application's Own Files
If the error only happens with one app, right-click that app's shortcut, select "Open file location". Look for a file named app.manifest or yourapp.exe.manifest. If it's there, open it with Notepad. The very first line should look like . If you see anything else — like text that says "error" or the file is empty — the manifest is corrupted. Reinstall that specific app.
System Restore to Before the Problem Started
Type "system restore" in the Windows search, select "Create a restore point". Click "System Restore...", then choose a point from before the error first appeared. Follow the prompts. This reverts system files without touching your personal data.

Alternative Fixes If the Above Doesn't Work

Fix the Windows Component Store Manually
If DISM failed because it couldn't find the source files, you can point it to a Windows installation media. Insert a Windows 10 or 11 USB drive, note the drive letter (say D:). Run this command: DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\sources\install.wim /LimitAccess. Replace D: with your drive letter.

Reinstall the Problem Application
Uninstall the app completely using Revo Uninstaller (free version is fine) to scrub leftover registry entries. Then download a fresh copy from the official source. Don't reuse the installer that caused the error — it might be corrupt.

Enable the Windows Modules Installer Service
Press Windows+R, type services.msc, press Enter. Find "Windows Modules Installer". Double-click it. Set Startup type to "Manual", click Start. Then run DISM and SFC again.

How to Prevent This From Happening Again

Don't download installers from third-party sites. Always get them from the software maker or Microsoft. Keep Windows Update turned on — many manifest format bugs get patched in cumulative updates. If you uninstall Visual C++ redistributables, don't remove all of them at once; some old apps need specific versions. Uninstall only the ones causing trouble.

Also, avoid editing manifest files manually unless you know exactly what you're doing. One wrong character breaks the entire thing. I've seen people open manifest files in WordPad and save them with extra formatting — that kills the XML structure.

Real-world scenario I fixed last month: A user on Windows 10 22H2 got this error launching a 2016-era accounting program. DISM fixed the corrupt manifest along with a half-broken .NET Framework installation. Total time: 10 minutes.