Fix ERROR_SXS_SECTION_NOT_FOUND (0x000036B0) on Windows

Quick answer for pros: Run sfc /scannow then DISM /Online /Cleanup-Image /RestoreHealth in an admin command prompt. If that doesn't fix it, delete and reinstall the specific app or use System Restore to roll back recent updates.

I know this error is infuriating. You click an app—maybe it's an old game, a business tool, or even something from Microsoft—and all you get is a cryptic error: ERROR_SXS_SECTION_NOT_FOUND (0x000036B0). No other context. The app won't open. The first time I hit this on a Windows 10 machine running a legacy accounting app, I nearly pulled my hair out. The error comes from the Windows Side-by-Side (SxS) assembly system. When a program starts, Windows looks for a manifest that tells it which DLLs and runtimes to load. If that manifest is missing the right section, or the manifest itself is corrupted, you get this error. Common triggers: a partial Windows update, a bad driver install, or a program's own update that got interrupted.

The fix usually comes down to repairing system files or the app's own manifest. Here's how I'd tackle it, step by step.

Step-by-Step Fixes for ERROR_SXS_SECTION_NOT_FOUND

1. Run System File Checker

This is my first stop because it's fast and often catches corrupted Windows files that mess with the SxS store.

1. Open Command Prompt as Administrator. Hit Windows Key + X, then select 'Command Prompt (Admin)' or 'Terminal (Admin)'.
2. Type sfc /scannow and press Enter. Let it run—it'll take 10-15 minutes.
3. After it finishes, restart your PC and see if the error is gone.

If SFC says it found corrupt files but couldn't fix them, don't panic. The next step usually handles that.

2. Run DISM to Fix the System Image

DISM is the heavy hitter. It repairs the component store that SFC relies on. If SFC failed, this is the real fix.

1. Still in the admin command prompt, type: DISM /Online /Cleanup-Image /RestoreHealth
2. Wait. This can take 30 minutes or more. Don't close the window.
3. Once done, run sfc /scannow again to let SFC fix whatever DISM rebuilt.
4. Restart your PC.

3. Reinstall the App That's Failing

The error might not be Windows' fault—the app's own manifest could be broken. I've seen this with older Adobe tools and some game installers.

1. Uninstall the problematic app via Settings > Apps > Apps & features.
2. Delete any leftover folders in C:\Program Files or C:\Program Files (x86) for that app.
3. Reboot, then reinstall the latest version from the official source.

4. Use System Restore

If the error showed up after a Windows update or driver install, roll back to a point before the trouble started.

1. Type 'System Restore' in the Start menu and open 'Create a restore point'.
2. Click 'System Restore…', then choose a point from before the error began.
3. Follow the wizard—your files won't be touched, but apps installed after that date will be removed.

Alternative Fixes for Stubborn Cases

Sometimes the above steps don't cut it. Here's what I try next, in order.

Check the App's Manifest File

This is a bit advanced, but I've fixed errors this way when nothing else worked. You'll need to locate the app's manifest file (usually named app.exe.manifest or inside the app folder). Open it with Notepad. Look for a <dependency> section. If it's missing or empty, you can copy a valid manifest from a working install of the same app version. I know that sounds tedious, but for some legacy apps, it's the only way.

Reinstall the Microsoft Visual C++ Redistributables

Since SxS errors often involve C++ runtimes, reinstalling them can help. Go to Microsoft's site and download the latest all-in-one package for Visual C++ 2015-2022. Also grab older versions if the app needs them (2005, 2008, 2010, 2012, 2013).

Test in Safe Mode

Boot into Safe Mode and try launching the app. If it works there, a driver or startup program is interfering. Clean boot your system to isolate the culprit.

Prevention Tips for Future

Once you've got the app running again, a few habits will keep this error from coming back.

• Keep Windows updated. Microsoft patches SxS issues regularly. Don't skip updates.
• Use the official uninstaller when removing software. Don't just delete folders.
• Avoid interrupting updates. Let Windows updates and software installers finish completely, even if they seem slow.
• Run SFC and DISM monthly. I do this on the first of every month. It catches file corruption before it bites you.

I've seen this error on everything from Windows 7 to Windows 11, and the fix is almost always one of the steps above. If you're still stuck, check the Windows Event Viewer under 'Administrative Events' for more clues—the log often points to exactly which assembly is missing. Don't let this error ruin your day. You've got this.