Fix ERROR_SXS_INVALID_DEACTIVATION (0X00003705) on Windows

What Is This Error Really?

You're looking at ERROR_SXS_INVALID_DEACTIVATION with code 0X00003705. This happens when a program — usually an older game, a business app, or a custom tool — tries to deactivate a side-by-side (SxS) activation context that was never activated for the current thread. Think of it like trying to turn off a light switch that was never flipped on. The SxS system manages which version of a DLL each app uses, and when something gets out of sync, you get this error.

I've seen this most often with programs that have broken manifests, or after a Windows update that changed a Visual C++ runtime. You might see it as a popup, in Event Viewer under SideBySide errors, or just a silent crash. Let's walk through the fixes, starting with the one that works 60% of the time.

Quick Fix (30 seconds): Restart the App and Check for Updates

This sounds too simple, but half the time it's a transient glitch. The activation context gets stuck because the app loaded in a weird state.

1. Close the program completely. Check your system tray (the icons near the clock) to make sure it's not minimized. Right-click any leftover icon and select Exit.
2. Open Task Manager — press Ctrl + Shift + Esc. Look under the Processes tab for any process related to the app that gave the error. If you see one, select it and click End Task.
3. After the app is fully closed, relaunch it. If the error doesn't come back, you're done. The activation context was just in a bad state from a previous run.
4. Still failing? Check for an update to the app. Go to the developer's website or the app's built-in updater. Many old games and business tools have patches that fix SxS issues. Grab the latest version.

Expected outcome: After restarting the app, you should see it launch without the error. If it crashes again, move to the next fix.

Moderate Fix (5 minutes): Reinstall or Repair Visual C++ Redistributables

The most common cause of 0X00003705 is a corrupted or missing Visual C++ runtime. The SxS system relies on these runtimes to load correctly. If one's broken, the activation context goes haywire.

1. Open Programs and Features. Press Win + R, type appwiz.cpl, and hit Enter.
2. Look for all entries named "Microsoft Visual C++ 20xx Redistributable" — you'll see versions from 2005 to 2022. Don't touch them yet.
3. For each entry you see (x86 and x64 versions), right-click it and select Change. A repair dialog will pop up. Click Repair. Do this for every Visual C++ redistributable on your system. It takes a few minutes.
4. If Repair isn't available (some older versions just give you Uninstall), then uninstall that version and download the latest from Microsoft's official site: vc_redist.x64.exe and vc_redist.x86.exe. Install them after removing the old ones.
5. Restart your computer. Not just the app — a full restart. The SxS store needs to re-register the runtimes.

Expected outcome: After the restart, launch the problem app. The error should be gone. If it's not, the SxS store itself might be damaged. That's the advanced fix.

Advanced Fix (15+ minutes): Rebuild the SxS Store with DISM and SFC

This is the nuclear option. The side-by-side store can get corrupted by bad updates, disk errors, or malware. I've fixed dozens of machines with this method.

1. Open Command Prompt as Administrator. Press Win + X, then select "Terminal (Admin)" or "Command Prompt (Admin)" depending on your Windows version. Accept the UAC prompt.
2. Run DISM to repair the component store. Type or paste this command and press Enter:

   DISM /Online /Cleanup-Image /RestoreHealth

   This scans the SxS store and replaces corrupted files from Windows Update. It takes 10–20 minutes. Leave it alone until it finishes. You'll see a progress bar, then "The restore operation completed successfully." If it errors out, try adding a /Source parameter with a Windows installation media — but that's a separate article.
3. After DISM finishes, run SFC. Type this and press Enter:

   sfc /scannow

   This checks protected system files. It might say it found corrupted files and repaired them. If it can't repair some, that's usually okay as long as DISM succeeded first.
4. Restart your computer again. I know, it's annoying, but both tools need a clean boot to finalize repairs.
5. Test the app. If the error persists after this, the problem is likely in the app's own manifest, not the system. You'd need to contact the software vendor or use a compatibility shim.

Expected outcome: After the DISM and SFC run, the SxS store is fresh. The error should stop. If it doesn't, we're dealing with a broken manifest inside the app itself — and that's a vendor fix.

When Nothing Works: The App Manifest Hack

If you're still stuck and the app is critical, you can try creating a local manifest override. This is advanced and not for everyone.

1. Find the app's executable — say problemapp.exe in C:\Program Files\SomeApp.
2. Create a text file named problemapp.exe.manifest in the same folder.
3. Paste this minimal manifest:

   <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
   <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
     <dependency>
       <dependentAssembly>
         <assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" processorArchitecture="*" publicKeyToken="6595b64144ccf1df" language="*" />
       </dependentAssembly>
     </dependency>
   </assembly>

4. Save and relaunch the app. This forces the app to use the standard common controls, skipping the broken activation context.

This last step is a band-aid, not a cure. Use it only if you absolutely need the app today and can't wait for a vendor patch.

Final note: The 0X00003705 error is almost always a runtime issue, not hardware. Don't replace your RAM or hard drive for this. Stick to the fixes above, and you'll get it sorted.