SXS Manifest Too Big (0x00003719) – 3 Quick Fixes

You've got ERROR_SXS_MANIFEST_TOO_BIG with code 0x00003719. I see this most often when somebody installs a program that ships a bloated manifest file—or when a Windows update smashes a manifest to pieces and it keeps getting duplicated. The manifest itself has a hard 2MB limit. Once it crosses that, Windows just says nope.

Had a client last month whose entire print queue died because of this. Turned out a printer driver installer dumped a 2.4MB manifest into C:\Windows\WinSxS. Every print job that tried to load that manifest failed. We trimmed it down and everything worked again.

Let’s go through the fixes in order of how often they work. Start with #1.

1. Bloated Manifest from a Third-Party App

The most common cause: a program or driver installer adds a manifest that’s way too big. Usually it’s an application manifest that includes tons of unnecessary dependencies, or a driver that bundles its own side-by-side assembly with a massive dependency list.

Real-world trigger: An accounting software update added a manifest for a PDF generator that pulled in every Visual C++ redistributable ever made. Manifest was 3.1MB. Every time the software tried to launch, it crashed with 0x00003719.

How to fix it:

1. Find the culprit. Open Event Viewer (eventvwr.msc). Look under Windows Logs > Application for events with source SideBySide and event ID 33 or 59. These point directly to the manifest file path and the app that’s trying to load it.
2. Check file size. Navigate to that manifest file (usually in C:\Program Files\AppName\ or C:\Windows\WinSxS\). Right-click > Properties. If it’s over 2MB, that’s your problem.
3. Edit it down. Open the manifest in Notepad. Look for <assemblyIdentity> sections. Remove references to unnecessary dependencies—especially <dependentAssembly> blocks for redistributables your app doesn’t actually use. Only do this if you know what you’re doing. Wrong edit can break the app completely.
4. If you can’t edit it, reinstall the app with the latest version from the vendor. Many have fixed these bloated manifests by now.

Alternative: Use Process Monitor (procmon.exe) filtered on path *.manifest to see which file is being read right before the error pops up.

2. Corrupted System File Caching

Sometimes the manifest itself isn’t too big—it’s that Windows cached a broken copy of it. The cache can duplicate entries, making the effective size bigger than the file on disk. This happens after a failed Windows update or disk corruption.

Real-world trigger: A Windows 10 update to 22H2 failed halfway through, leaving a half-baked manifest cache in C:\Windows\WinSxS. Every subsequent attempt to load any app using that assembly failed with 0x00003719.

How to fix it:

1. Run System File Checker. Open Command Prompt as admin and run:

sfc /scannow

This checks and repairs system files, including manifest caches. Let it finish—could take 15 minutes.

2. Run DISM after SFC. SFC pulls good files from the Windows image, but if the image itself is busted, DISM fixes that:

DISM /Online /Cleanup-Image /RestoreHealth

This downloads clean files from Windows Update. Takes 20–30 minutes.

3. Reboot and check Event Viewer again. If the error’s gone, you’re done. If it’s still there, move to fix #3.

3. Registry Corruption Causing Manifest Size Overflow

Rare but nasty: the registry key that tracks manifest sizes gets corrupted. Windows reads a garbage value that says the manifest is way bigger than it actually is. This usually happens after a hard crash while a program was writing to the registry.

Real-world trigger: A blue screen during a Visual Studio 2022 install. The registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\ had an entry showing a manifest as 8GB. Real file was 500KB.

How to fix it:

1. Back up the registry first. Open Regedit, right-click on Computer, choose Export. Save the whole thing somewhere safe.
2. Navigate to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\

3. Look for values named like ManifestSize_*. If you see one with a number over 2000000 (2MB in bytes), double-click it and set it to 2000000. But really, you want to delete any corrupted entries. Right-click and delete the whole value that’s wrong.
4. If you’re not sure which one is bad, you can recreate the whole SideBySide key. Not for the faint of heart. Better: run a system restore to a point before the issue started.

Disclaimer: Messing with the registry can brick your system. Only do this if you’re comfortable recovering from a live boot USB.

Quick-Reference Summary Table

If none of these work, you’re looking at a corrupt Windows image that needs a repair install (in-place upgrade) or a fresh install. I’ve only had to go that far once in ten years. Try these first—they fix 99% of cases.