Fix 0xC0150013: SXS Process Termination Requested

Windows kills an app when a side-by-side component requests termination. Usually a corrupted Visual C++ Redistributable or a broken install. Reinstall the VC++ runtimes.

Quick answer: Reinstall all Visual C++ Redistributable packages (both x86 and x64) and repair .NET Framework 4.8. If that doesn't work, do a clean boot to rule out third-party interference.

Here's the deal. The error code 0xC0150013 shows up when the Windows Side-by-Side (SxS) isolation facility explicitly asks Windows to terminate a process. This isn't a crash from your app's own code — the SxS layer is the part of Windows that loads shared DLLs with specific versions. When a component inside that layer decides something is so wrong that the process can't continue, it requests termination. Common triggers: a freshly installed program that overwrote a shared runtime, a botched Windows update, or an old game that depends on a specific Visual C++ version that got removed. You'll typically see a dialog that says 'A component used by the isolation facility has requested that the process be terminated' with the code 0xC0150013. It kills the app instantly, no chance to save work.

The usual culprit is a mismatched or corrupted Visual C++ Redistributable. Those packages are the backbone for half of third-party software. When one version gets overwritten by an installer that bundles an older or broken runtime, the SxS subsystem throws this error. Start there.

Fix 1: Reinstall Visual C++ Redistributables

Open a browser and go to the official Microsoft download page for Visual C++ Redistributable. The easiest way is to search for 'Visual C++ Redistributable latest supported downloads' on Microsoft's site.
Download both the x64 and x86 versions. Yes, even if your system is 64-bit, many apps still use 32-bit components. Missing either can trigger this error.
Before installing, go to Control Panel → Programs and Features. Look for any entry with 'Microsoft Visual C++ 2015-2022' or older versions. For each one you find, right-click and select Uninstall. Do this for all of them.
Restart your PC. You should see the list of installed programs shrink — that's normal.
Run the x64 installer you downloaded, then the x86 installer. Accept the defaults, click Install. Wait for each to finish — it can take a couple of minutes. After each install, you'll see a 'Setup Successful' message.
Restart again. Then try launching the app that was failing. If the error is gone, you're done — that was the fix.

Fix 2: Repair .NET Framework 4.8

If reinstalling VC++ doesn't cut it, .NET Framework is the next suspect. The SxS subsystem often works with .NET assemblies, and a corrupt .NET install can cause the same termination request.

Download the .NET Framework 4.8 offline installer from Microsoft's official site. It's a small file (~100 MB).
Run it. You won't see a repair option right away — the installer will say 'The .NET Framework 4.8 is already installed.'
That's fine. Look for a 'Repair' button on the welcome screen or after the success message. Click it. If you don't see one, run the installer with the command line flag /repair. Open a Command Prompt as Administrator and type:

ndp48-x86-x64-allos-enu.exe /repair

Replace the filename with the actual one you downloaded. The repair takes about ten minutes. When it's done, restart and test the app.

Fix 3: Clean Boot to Isolate Third-Party Interference

Sometimes a third-party service (like an antivirus or a system utility) hooks into the SxS subsystem and causes the crash. A clean boot starts Windows with only Microsoft services, so you can test if that's the issue.

Press Win + R, type msconfig, press Enter.
On the Services tab, check 'Hide all Microsoft services'. Click 'Disable all'.
On the Startup tab, click 'Open Task Manager'. Disable every startup item you see there.
Close Task Manager, go back to System Configuration, click OK, and restart.
After the restart, try launching the app. If it works, a third-party service is the culprit. Use System Configuration again to re-enable services in batches until you find the one that breaks it.

Alternative Fix: Check Event Viewer for Specifics

If the above fixes don't help, dig into Event Viewer. The error message is generic, but the event log often names the exact DLL or app that triggered the termination.

Press Win + X and select Event Viewer.
Expand Windows Logs → Application.
Look for events with Source 'SideBySide' or 'Application Error' around the time the crash happened. Double-click each one.
Read the General tab. It might say something like 'Activation context generation failed for C:\Program Files\SomeApp\app.exe. Dependent Assembly Microsoft.VC90.CRT could not be found.' That tells you the exact VC++ version you need — install that specific redistributable.

Prevention Tip

Once you've fixed it, avoid future headaches. When you install new software, don't let the installer overwrite existing VC++ runtimes without asking. Some installers bundle old runtimes and replace newer ones. Always choose 'Repair' or 'Install' rather than 'Overwrite' if you're given a choice. Also, set Windows Update to automatically install updates — a recent cumulative update often includes SxS fixes. And if you're a gamer, keep the latest DirectX runtime updated; it's tied to the same subsystem.