Fix ERROR_SXS_MULTIPLE_DEACTIVATION (0x00003706) on Windows

The 30-Second Fix: Restart the Misbehaving App or Service

I know this error is infuriating. It usually pops up when you're in the middle of something—launching a game, opening a Microsoft Office doc, or running a system backup. The quickest way to check if it's a transient glitch: close the app that triggered the error, wait 10 seconds, and relaunch it. If the error doesn't come back, you're done. But if it does, don't waste time—move to the next step.

This error is common after a Windows Update or a driver install. For example, I've seen it on Windows 11 22H2 when opening Adobe Premiere Pro right after a cumulative update. A quick restart of the app fixes it for about 30% of my callers.

The 5-Minute Fix: Clear Side-by-Side Cache and Check Event Log

Still seeing 0x00003706? That activation context problem is likely stuck in the SxS (Side-by-Side) cache. Here's the moderate fix that works for most people.

1. Open Event Viewer – Press Win + R, type eventvwr.msc, hit Enter.
2. Look for the SxS error – Expand Windows Logs > Application. Filter by source SideBySide or look for Event ID 33 or 59. Note the exact application name and module path (like C:\Program Files\SomeApp\app.exe). Jot it down.
3. Delete the SxS activation context cache – This is the real fix. Open an elevated Command Prompt (right-click Start > Command Prompt (Admin) or Terminal Admin). Run:

   del /f /s /q %windir%\system32\config\systemprofile\AppData\Local\Microsoft\Windows\SideBySide\*.*

   Then run:

   del /f /s /q %windir%\syswow64\config\systemprofile\AppData\Local\Microsoft\Windows\SideBySide\*.*

4. Restart the app – Don't reboot yet. Try the app again. If it works, great. If not, proceed to the next step.

This clears the cached activation contexts that Windows reuses. A corrupted cache is the number-one cause of this error in my experience. Skip any registry hacks you see online—they won't help here.

The 15+ Minute Fix: System File Checker and Clean Boot

If the error persists, something deeper is hosed. Maybe a system file is corrupted, or a third-party service is injecting a bad DLL. Let's chase both.

Step 1: Run SFC and DISM

Open an elevated Command Prompt again. Run these commands in order—don't skip DISM, it fixes the store that SFC needs.

dism /online /cleanup-image /restorehealth
sfc /scannow

DISM takes 5-10 minutes. Let it finish. SFC takes another 5. After both complete, restart your PC and test the app. This resolves roughly half of the remaining cases.

Step 2: Clean Boot to Isolate the Culprit

Still broken? That means a non-Microsoft service or a startup program is interfering. A clean boot strips everything down to bare Windows. Here's how:

1. Press Win + R, type msconfig, hit Enter.
2. Go to Services tab, check Hide all Microsoft services, then click Disable all.
3. Go to Startup tab > Open Task Manager. Disable every startup item.
4. Click OK, restart.

Now test the app. If the error is gone, you've got a conflict. Enable services in small batches (5-10 at a time), restarting each time, until the error returns. The last batch you enabled contains the offender. Common suspects: antivirus suites (especially Norton and McAfee), cloud sync tools (Dropbox, Google Drive), or GPU overlay tools like MSI Afterburner. Uninstall or update the troublemaker.

Step 3: Re-register the Side-by-Side Assembly

If the error still shows up and you've identified the app from the Event Viewer, try re-registering its SxS assemblies. For example, if the affected app is MyApp.exe and it uses the Microsoft.VC90.CRT manifest, do this:

cd "C:\Program Files\MyApp"
c:\windows\system32\regsvr32.exe /u "Microsoft.VC90.CRT.manifest"
c:\windows\system32\regsvr32.exe "Microsoft.VC90.CRT.manifest"

Replace the path and manifest filename with whatever you saw in Event Viewer. This forces Windows to re-read the manifest and create a fresh activation context.

What to Do If Nothing Works

If you've gone through all three steps and the error is still there, you're looking at either a deeply corrupted SxS store or a malware infection. Run a full offline scan with Windows Defender (the offline scan, not the quick one). Then, as a last resort, repair-install Windows using the Windows 10 or 11 Media Creation Tool. Choose Keep personal files and apps—it reinstalls the OS but saves your data. This fixes any SxS corruption at the kernel level.

I know the error 0x00003706 is a pain, but 9 times out of 10 it's a cache issue or a third-party conflict. Start with the 30-second fix, skip the registry edits, and you'll be back to work in under 20 minutes. Good luck.