Fix ERROR_SXS_CANT_GEN_ACTCTX 0X000036B1 Side-by-Side Configuration

Cause #1: Missing or Corrupted Visual C++ Redistributables

I can't count how many times I've walked into a client's office — usually a small accounting firm or a dental practice — and seen that dreaded 0X000036B1 error pop up on some critical line-of-business app. Nine times out of ten, it's the Visual C++ runtime libraries that got hosed. These are the DLLs that almost every Windows program depends on, and they love to break during Windows updates or when someone uninstalls something they shouldn't.

The fix is boring but effective: wipe and reinstall all the Visual C++ redistributables. Don't just install the latest one — older apps often need the 2005, 2008, 2010, 2013, or 2015-2022 versions. I keep a flash drive with all of them for this exact reason.

1. Open Control Panel > Programs and Features.
2. Uninstall every entry that says "Microsoft Visual C++ Redistributable." Reboot.
3. Go to Microsoft's official download page and grab the combined x86 and x64 redistributables for 2015-2022 (it's one package now). Also grab 2005, 2008, 2010, and 2013 if the app is old. Run them all.
4. Reboot again, then try launching the app.

I had a client last month whose entire print queue died because of this — turns out a Windows patch nuked the 2013 redistributable. Reinstalled it, and the app came right back. If that doesn't work, check the Application Event Log in Event Viewer. Look for SideBySide errors — they'll tell you which exact DLL and version is missing.

Cause #2: Corrupted System Files (SFC / DISM)

If reinstalling the runtimes didn't fix it, the next suspect is deeper corruption in Windows itself. I've seen this happen most often after a failed Windows update or a disk error. The side-by-side (SxS) store — where Windows keeps all the manifest files for these runtimes — can get hinky.

Run these two commands in an elevated command prompt (right-click Command Prompt, Run as administrator):

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

SFC scans and repairs protected system files. DISM fixes the component store that SFC relies on. Run DISM first if you want to be thorough — I do it that way. Let both finish fully. They can take 15-20 minutes on an older machine. Reboot after, then test the app again.

A word of caution: if DISM says it can't find the source files, you might need a Windows installation media. Insert a USB with the same Windows version and run:

DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess

Replace the path with your USB drive letter. I've pulled a few machines back from the brink this way.

Cause #3: Manifest File Corruption Inside the App Folder

Less common, but I've seen it — especially with older software that's been copied from machine to machine, like custom business apps for inventory or scheduling. The app itself has a .manifest file (usually embedded or sitting next to the .exe) that defines what runtimes it needs. If that manifest is garbled, missing, or pointing to a version you don't have, you'll get this exact error.

Check the app's installation folder — typically C:\Program Files\YourApp\ or C:\Program Files (x86)\YourApp\. Look for any file ending in .manifest. If you find one, open it in Notepad. You'll see XML like this:

<dependency>
  <dependentAssembly>
    <assemblyIdentity type="win32" name="Microsoft.VC90.CRT" version="9.0.21022.8" />
  </dependentAssembly>
</dependency>

That version="9.0.21022.8" is the exact version of the 2008 runtime it expects. Compare it against what you have installed. If the version doesn't match, you have two choices:

• Find and install that specific version — tricky but possible via Microsoft Update Catalog.
• Reinstall the app from its original installer, which should bring the correct manifest and matching runtimes.

I had a case with an old QuickBooks version where the manifest pointed to 9.0.30729.1 but the client had 9.0.21022.8. Reinstalled QuickBooks and it fixed itself.

Quick-Reference Summary Table