Fix Side-by-Side Config Error: 7 Proven Methods | Windows

It is 9:42 PM, a deadline is looming, and your primary development tool—or perhaps your favorite game—refuses to launch. Instead of a splash screen, you’re greeted with that infamous dialog box: "The application has failed to start because its side-by-side configuration is incorrect." If you’re feeling frustrated, you’re not alone. This specific error is one of the most common Windows assembly issues I encounter in my 15 years of supporting enterprise desktops and consumer systems alike.

The good news? This isn’t a code bug in your software. It’s a dependency resolution failure. Windows uses a mechanism called "Side-by-Side" (SxS) assemblies to manage shared libraries, and when the system can’t find the exact version of a DLL that an application requests, it throws this error. Often, this points to component store corruption or missing Visual C++ runtimes.

In this guide, we aren’t just listing random commands to try. We’re going to follow a logical decision tree: starting with the most likely culprit (C++ Redistributables), moving to system-level integrity checks (SFC and DISM), and finally addressing app-specific quirks. By the end, you’ll have a permanent fix, whether you’re running Windows 10 or 11.

Understanding the Cause: What Is a Side-by-Side Error?

Before we touch the registry or run admin commands, it helps to understand why Windows behaves this way. Most users assume DLLs are just files sitting in C:\Windows\System32. That was the case in Windows 95/98, leading to the infamous "DLL Hell," where one program’s update would break another’s.

To fix that, Microsoft introduced the Windows Component Store (also known as the WinSxS folder). This is where the OS keeps a pristine backup of every system file and assembly manifest. When an app like Chrome or AutoCAD starts, it doesn’t just grab msvcp140.dll from the system directory. It reads its "windows side-by-side assembly manifest," which specifies exactly which version and architecture (x86 or x64) of that library it needs. The Windows loader then looks into the Component Store to resolve this dependency.

Think of it like a library card system. You don’t just ask for "a book about physics"; you ask for "Newton’s Principia, 1st edition, hardcover." If the library (the Component Store) has lost track of that specific copy, or if the catalog (the manifest) is damaged, the system rejects your request. That rejection is the "side-by-side configuration is incorrect" error.

Common Triggers for Configuration Errors

So, what breaks this delicate system? In my experience, three main triggers account for 90% of these failures:

1. Corrupted Visual C++ Redistributables: This is the big one. Microsoft’s C++ runtime libraries are installed via packages. If an update gets interrupted, or if an older version is left behind while the app expects a newer one, the manifest resolution fails.
2. Interrupted Windows Updates: A failed KB patch can corrupt the integrity of the Component Store. If the store’s index gets out of sync with the actual files on disk, SxS resolution breaks.
3. Incompatible Software Versions: Running legacy software, like AutoCAD 2012 or an older Steam client, on Windows 11 can sometimes trigger this if the system no longer supports the specific SxS activation context required by that older app.

Step 1: Repair the Visual C++ Redistributable Stack

If you’re seeing this error across multiple applications, the root cause is almost certainly a missing or corrupted C++ runtime. Before diving into complex system repair, let’s address the most frequent offender.

Identify Missing or Corrupt C++ Runtimes

Modern Windows applications rely heavily on the Microsoft Visual C++ Redistributable packages. Over the years, Microsoft has released various versions (2005, 2008, 2010, 2013, and the cumulative 2015-2022 package).

Here is the key insight many guides miss: You need both the x86 and x64 versions. Even on a 64-bit system, 32-bit applications (like many older game engines or plugins) will request the x86 runtimes. If you only installed the 64-bit version, your 32-bit apps will fail with a side-by-side configuration error.

• Visual C++ 2015-2022 Redistributable: This is a single cumulative package that includes runtimes for Visual Studio 2015, 2017, 2019, and 2022. If your app is built with a modern compiler, this is what it needs.
• Visual C++ 2008/2010/2013: Older software (like some Autodesk products or legacy Java apps) may still specifically request these.
• Visual C++ 2005: Rare now, but still required for some very old enterprise software.

Advanced Tip: If you’re comfortable using developer tools, you can use sxstrace.exe to trace exactly which manifest or DLL is failing. However, for 95% of users, checking the Control Panel for missing "Microsoft Visual C++ [Year] Redistributable" entries is sufficient.

Clean Reinstallation of Redistributables

If you suspect the C++ stack is broken, don’t just try to install on top of it. A clean reinstall is more effective.

1. Uninstall: Go to Settings > Apps > Installed Apps (or Control Panel > Programs and Features). Find all entries starting with "Microsoft Visual C++" (e.g., Microsoft Visual C++ 2015-2022 Redistributable (x64)). Uninstall them one by one.
2. Download: Head to the official Microsoft Developer Network (MSDN) Archive or the Visual C++ Redistributable page on Microsoft Learn. Download the latest cumulative vc_redist.x64.exe and vc_redist.x86.exe.
3. Install: Run the x64 installer first, reboot your PC. Then run the x86 installer, and reboot again.

This sequential approach ensures that the system registers the new assemblies correctly without conflicts from leftover files. I recommend rebooting between each step because Windows sometimes locks files during the update process.

Step 2: System File Integrity Checks (SFC & DISM)

If reinstalling the C++ redistributables didn’t work, we need to look at the underlying Windows Component Store. This is where the "system file checker" comes into play.

Running System File Checker Correctly

The sfc /scannow command (System File Checker) is the first line of defense. It scans the protected operating system files and verifies their integrity. If it finds discrepancies, it replaces the damaged files with clean copies from the Component Store.

1. Press the Windows key + S, type cmd, right-click on "Command Prompt," and select Run as administrator.

2. Type the following command and press Enter:

   sfc /scannow
   

3. Wait. This process can take 15 to 30 minutes. Do not close the window.

4. When it finishes, you’ll get one of three results:

   • Windows Resource Protection did not find any integrity violations. (Good, but doesn’t explain the error.)
   • Windows Resource Protection found corrupt files and successfully repaired them. (Reboot and test your app. This often fixes SxS errors.)
   • Windows Resource Protection found corrupt files but was unable to fix some of them. (You need to move to the next step.)

If SFC says it found corrupt files but couldn't fix them, it usually means the source of the repair (the Component Store itself) is damaged. This is where DISM steps in.

Advanced Repair with DISM Commands

DISM (Deployment Image Servicing and Management) is a command-line tool that repairs the Windows image and, crucially, the Component Store. Before running the heavy repair, we scan the health of the image.

1. In the same administrator Command Prompt window, run:

   DISM /Online /Cleanup-Image /ScanHealth
   

   This will scan the Component Store for corruption. It’s read-only and relatively fast.

2. If the scan reports issues, or even if it looks clean but SFC failed, run the repair command:

   DISM /Online /Cleanup-Image /RestoreHealth
   

   This command pulls fresh files from Windows Update to replace corrupted data in the Component Store. Note: You must be connected to the internet for this to work, and it can take a long time (sometimes 30+ minutes) depending on how many files need repair. Watch the "Percent Complete" bar; it might stall at 41% or 61% for a while—that’s normal.

3. Once DISM completes successfully, reboot your PC.

4. Re-run sfc /scannow. Now that the Component Store is repaired, SFC should be able to fix the remaining file corruption.

This sequence—SFC, then DISM, then SFC again—is the gold standard for fixing component store corruption.

Step 3: App-Specific Fixes (Chrome, Games, & Autodesk)

Sometimes, the error is isolated to a single application. This happens when the app’s local manifest is corrupted, or it’s requesting a very specific version of a library that isn’t installed.

Fixing Browser Configuration Errors

I frequently see this error when launching Google Chrome or Edge. In my experience, this is often caused by a corrupted installation of the browser itself, not the system.

• For Chrome: Go to Settings > Apps > Installed Apps, find Google Chrome, and look for the Repair option (three vertical dots next to it). If "Repair" isn't available or fails, uninstall Chrome completely, restart your PC, and reinstall the latest version from google.com/chrome.
• For Edge: Since Edge is a system component in Windows 10/11, you can’t uninstall it normally. Instead, go to Windows Settings > Apps > Optional features > Manage optional features, find "Microsoft Edge," and run the Repair option. Alternatively, open PowerShell as admin and run Get-AppxPackage MicrosoftEdge | Reset-AppPackage.

Gaming Launchers (Riot, Steam, MikuMikuDance)

Game launchers like Steam and Riot Client are heavy users of SxS assemblies.

• Run as Administrator: Right-click the launcher icon and select "Run as administrator." Sometimes, permissions issues prevent the launcher from reading the correct manifests.
• Verify Integrity: In Steam, go to Library > Right-click Game > Properties > Installed Files > Verify integrity of game files. This forces Steam to re-download missing or corrupted assembly manifests associated with that specific game.
• DirectX: Ensure you have the latest DirectX runtime installed. Older games rely on older SxS manifests for DirectX 9 or 11 components.

Professional Software (Autodesk & Visual Studio)

Developers and CAD users hit this error most often.

• Visual Studio: Use the Visual Studio Installer. Open the installer, find your installed edition (Community, Professional, Enterprise), click the gear icon, and select Modify. You can also choose Repair if you suspect a specific workload is broken.
• Autodesk (AutoCAD, Revit): These products often bundle their own C++ runtimes. If a side-by-side configuration error occurs with AutoCAD 2016 on Windows 11, it’s likely a compatibility issue. Check Autodesk’s system requirements; older versions may not be fully supported on newer OS versions. For newer versions, use the Modify/Repair option in Control Panel to repair the installation. This reinstalls the specific C++ libraries that Autodesk requires.

Troubleshooting Persistent Errors: Clean Boot & Rebuild

If you’ve tried the C++ reinstall, SFC, and DISM, and the error persists, we need to dig deeper. There are two remaining paths: isolating third-party conflicts or rebuilding the OS foundation.

Performing a Clean Boot

Sometimes, a third-party service (like an antivirus, a virtual machine service, or a hardware driver) is interfering with the Windows SxS activation context. A Clean Boot disables all non-Microsoft services to help you isolate the culprit.

1. Press Windows + R, type msconfig, and hit Enter.
2. Go to the Services tab. Check the box "Hide all Microsoft services" at the bottom.
3. Click Disable all.
4. Go to the Startup tab and click Open Task Manager. Disable all startup items.
5. Restart your PC.

Now, try launching the failing application. If it works, the issue is with a third-party service. Re-enable services one by one (or use binary search) to find the conflicting program. In one case I handled, a corrupted antivirus definition was causing SxS failures for a specific engineering software. Disabling that antivirus resolved it.

Remember to return msconfig to normal settings (normal startup services and re-enable startup items) when you’re done diagnosing.

Rebuilding the Component Store

If a Clean Boot doesn’t help, and SFC/DISM reported errors they couldn’t fix, you may have deep-seated component store corruption.

• In-Place Upgrade: This is the nuclear option for system files. Download the Windows 10/11 installer from the Microsoft site, run it, and choose Upgrade now. This reinstalls the OS over itself without losing your data or apps (usually). It forces a complete rebuild of the Component Store and all system manifests.
• Warning: This takes 1-2 hours. Back up your critical data to an external drive before starting, just in case. After the upgrade, the "side-by-side configuration is incorrect" error is almost always resolved.

Frequently Asked Questions

What is a side-by-side configuration error?

It is a failure in Windows’ dependency resolution system where an application cannot find the correct version of a shared DLL (assembly). This is usually due to corruption in the Component Store or missing Visual C++ runtime packages. It’s a "missing file" error disguised as a "configuration" error.

How do I repair the Windows component store?

The standard sequence is to run sfc /scannow first. If that fails to fix all issues, run DISM /Online /Cleanup-Image /RestoreHealth to pull fresh files from Windows Update, then run sfc /scannow again. You need an active internet connection and Administrator privileges for this process.

Which Visual C++ redistributable version do I need?

Most modern applications (2015 onwards) require the Visual C++ 2015-2022 Redistributable package. This single package includes the runtimes for 2015, 2017, 2019, and 2022. However, legacy software might specifically need the 2005, 2008, or 2010 versions. For the broadest compatibility, install both the x86 and x64 versions of the latest cumulative package.

Does reinstalling the application fix this side-by-side error?

It works sometimes, particularly if the error is isolated to that specific app’s local manifest. However, if you’re seeing the error across multiple apps (e.g., both Chrome and Steam fail), the root cause is system-wide. Reinstalling one app won’t fix the underlying C++ runtime or Component Store corruption. You must perform the system-level fixes (SFC/DISM/C++ reinstall) first.

Conclusion

Dealing with "side-by-side configuration is incorrect" errors can feel like pulling teeth, especially when your primary tools are down. But as we’ve seen, it follows a predictable pattern. The three main pillars of resolution are:

1. C++ Runtime Repair: Ensuring the right versions of Visual C++ Redistributables (x86 and x64) are installed and intact.
2. System File Checks: Using SFC and DISM to heal the Windows Component Store.
3. App-Specific Repairs: Using the "Repair" function in Settings or the app’s own installer for isolated cases.

If the error persists after all these steps, it likely indicates deeper OS corruption that requires an In-Place Upgrade. To prevent future issues, keep your Windows updates current and ensure you’re installing C++ redistributables from official Microsoft sources.

Found this guide helpful? If you successfully fixed your side-by-side error, share your specific fix in the comments below. It helps others who might be facing the same unique variation of the problem. And if you want to proactively check your system’s health, check out our related article on How to Check if Windows Component Store is Healthy.