Fix ERROR_SXS_INVALID_ACTCTXDATA_FORMAT (0X000036B2)

What's the Deal with 0X000036B2?

This error usually pops up when Windows can't parse an application's manifest file or activation context—the XML data that tells the system which DLLs and assemblies the app needs. I've seen it most often after a botched Windows update, a partial uninstall of an old app (like Visual C++ redistributables), or a malware scan that quarantined a system file. The exact message: "The application binding data format is invalid."

Here's the fix sequence. Start with the quick check, then escalate. Stop when the app opens.

Simple Fix: 30 Seconds – Restart and Check the Event Log

1. Reboot your PC. Not a shutdown/start—actually restart. Windows often clears transient SXS state on a full restart.
2. If that doesn't work right away, open Event Viewer (eventvwr.msc) and go to Windows Logs > Application. Look for any events with Source "SideBySide" or "MsiInstaller" from around the time the error happened. They'll tell you which manifest file is corrupt. Write down the file path.

Most times, a restart fixes it. If not, move on.

Moderate Fix: 5 Minutes – Clean the SXS Cache and Check the Registry

This is where I've fixed it for a dozen clients. The SXS cache can get corrupt entries from partial installations.

Step 1: Clear the Windows Temporary Files

• Press Win + R, type %windir%\temp, and delete everything inside. You'll need admin rights. Skip files that say they're in use.
• Then do the same for %temp% (your user temp folder).

Step 2: Check the Registry for Stale Activation Contexts

WARNING: Edit the registry at your own risk. Export a backup first.

1. Open Regedit (regedit.exe).
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide.
3. Look for a key named Compatibility or PreferExternalManifest. If you see any subkeys with gibberish names or missing values, right-click and delete them. I once had a client whose Adobe app kept crashing because a leftover manifest from an ancient .NET framework install was pointing to a non-existent file.

Step 3: Repair the Visual C++ Redistributables

Since 0X000036B2 often ties back to a missing or corrupt VC++ runtime, uninstall and reinstall them all. Go to Control Panel > Programs and Features, uninstall every version of Microsoft Visual C++ Redistributable. Then download the latest from Microsoft's direct link (not a third-party site) and reinstall them.

Advanced Fix: 15+ Minutes – System File Checker and DISM Deep Repair

If the error persists, the SXS store itself is likely corrupt. Had a client last month whose entire print queue died because of this—turns out a disk sector went bad.

Step 1: Run DISM to Restore Health

Open Command Prompt as Admin. Run this first:

DISM /Online /Cleanup-Image /RestoreHealth

This rebuilds the component store. Takes 10–15 minutes. If it hangs at 62% (common on slow networks), wait—it usually finishes.

Step 2: Run System File Checker

After DISM finishes, run:

sfc /scannow

This checks Windows system files against the fresh store. Let it finish, even if it finds errors and fixes them.

Step 3: Check for Disk Errors

If SFC found corrupt files it couldn't fix, run:

chkdsk c: /f /r

Reboot—it'll scan before Windows loads. This catches bad sectors that might corrupt manifest files silently.

Step 4: Reinstall the Failing Application

If none of the above works, uninstall the problem app completely, restart, and reinstall from a fresh download. Use a tool like Revo Uninstaller to wipe leftover registry entries. I've seen Office 365 setup break the SXS store because it leaves orphaned activation contexts behind—a clean install of the app fixes it.

When to Give Up and Reset Windows

If you've done all these and the error still shows, you're looking at a deeply corrupted Windows installation. Use the "Reset this PC" feature (Settings > Update & Security > Recovery) but choose "Keep my files". You'll keep your data but lose installed apps. Less than 5% of cases need this—but it's a clean slate.

"Had a small biz client who couldn't launch their accounting software for three days. The DISM + SFC combo fixed it in 20 minutes. Don't skip the temp file cleanup—that's where the corruption often hides."