Fix SXS Root Manifest Dependency Not Installed (0x36BF)

What triggers this error?

This usually pops up when you launch an older app—like a game from 2012 or a corporate tool—on Windows 10 or 11. The app's manifest says it needs a specific version of a system assembly, like VC++ 2008 SP1 or a .NET Framework version, but that assembly isn't installed properly. You'll see a dialog box with the code 0x000036BF and the message about a dependent assembly not being installed.

Fix 1: Reinstall the application (30 seconds)

I know this sounds too simple, but it works about 60% of the time. The installer usually checks for missing dependencies and pulls them down. Uninstall the app from Settings > Apps > Apps & features, then restart your PC. Download the latest version from the official source—don't use an old setup.exe you found in a folder. Install it fresh. If the error disappears, you're done.

If the error persists, move to Fix 2.

Fix 2: Run SFC and DISM (5 minutes)

System File Checker can fix corrupted system components that the manifest relies on. DISM repairs the system image—do both.

1. Open Command Prompt as Administrator (right-click Start, select "Command Prompt (Admin)" or "Terminal (Admin)").
2. Type sfc /scannow and press Enter. Let it finish—it might take 10-15 minutes. Don't close the window.
3. If SFC finds corrupted files but can't fix them, run DISM /Online /Cleanup-Image /RestoreHealth. This downloads clean files from Windows Update. Make sure you're online.
4. After DISM completes, run sfc /scannow again. It should repair anything left over.

Restart your PC and try launching the app.

Fix 3: Reinstall the specific VC++ runtime (5 minutes)

The most common missing assembly is a Visual C++ Redistributable. Your app might need a specific version—like 2005, 2008, 2010, 2012, 2013, or 2015-2022. Don't guess. Check the app's install folder for a file called vcredist_x86.exe or vcredist_x64.exe. If you see one, run it. If not, download the all-in-one pack from Microsoft's site.

My advice: Install ALL VC++ redistributables from 2005 through 2022, both x86 and x64. They don't conflict. I've seen apps silently fail because they needed the 2008 x86 version and only the 2015 one was present. Grab the official Microsoft Visual C++ Redistributable Runtimes All-in-One from a trusted source—or get each individually from Microsoft's download center.

After installing, reboot and test.

Fix 4: Manually register the missing assembly (15+ minutes)

This one's trickier. If you know which assembly is missing—the error message might name it—you can try to register it manually. For example, if it's Microsoft.VC80.CRT, you'd do:

1. Open Command Prompt as Administrator.
2. Navigate to the side-by-side assemblies folder: cd C:\Windows\WinSxS
3. Find the correct folder, like cd x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d0917697e2f10d0d
4. Run regsvr32 msxml6.dll or whatever the specific DLL is—but honestly, this rarely works because the issue is a missing manifest reference, not a missing DLL.

A better approach: Use the Process Monitor tool from Sysinternals. Filter for the app's executable, then look for NAME NOT FOUND entries in the WinSxS folder. That tells you exactly which assembly is missing. Then download and install the corresponding VC++ redistributable or .NET Framework version.

Fix 5: Use the Windows Update Troubleshooter (10 minutes)

Sometimes the assembly is part of a KB update that didn't install properly. Run the Windows Update troubleshooter:

1. Open Settings > Update & Security > Troubleshoot > Additional troubleshooters.
2. Select Windows Update and run the troubleshooter.
3. Let it scan and apply fixes.
4. After that, manually check for updates and install any pending ones.

Reboot and test the app.

Fix 6: System Restore (20 minutes)

If the error started after a recent update or software install, roll back. Open System Restore from the Start menu, choose a restore point from before the issue began, and let it revert your system. This won't touch your personal files, but it will uninstall apps installed after that point. Warning: Make sure you know what you're losing—like a new driver or a game you just installed.

Fix 7: In-place upgrade (1 hour, last resort)

If nothing works, do a repair installation of Windows. Download the Media Creation Tool from Microsoft, run it, and select "Upgrade this PC now." This reinstalls Windows while keeping your apps and files. It's the nuclear option, but it fixes deep corruption in the side-by-side component store.

Pro tip: Before you go nuclear, check Event Viewer under Windows Logs > Application for SideBySide errors. The details often reveal the exact assembly name and version. Copy that into a search engine; you'll find the right redistributable.

I've seen this error stump people for hours. Start with the reinstall, then SFC/DISM, then VC++ runtimes. You'll likely have it fixed within 10 minutes. Good luck.