Windows Side by Side Error please help!

A clean boot of Windows might help by isolating the issue, but it's not guaranteed to remove corrupt manifest files directly. The "SideBySide" error (Event ID 78) in your Event Viewer, specifically stating "Activation context generation failed" due to conflicting component versions, points to a conflict between different versions of the microsoft.windows.common-controls manifest files (one x86 and one amd64).

This often happens when an application tries to load a specific version of a runtime library, but a different, conflicting version is already active or required by another component.

Understanding the Problem

• Side-by-Side (SxS) Assembly: Windows uses a technology called Side-by-Side assembly (WinSxS) to allow multiple versions of the same DLLs (like common-controls) to coexist on the same system without conflicting. Applications can specify which version of a DLL they need in their manifest file.
• The Conflict: Your error indicates that CapCut.exe is trying to use microsoft.windows.common-controls version 6.0.26100.3912, but there's a conflict between the x86 (32-bit) and amd64 (64-bit) versions of this specific common control library. This isn't necessarily about CapCut itself being faulty, but rather an issue with how it's trying to load these system components, or how these components are registered on your system.
• Microsoft Visual C++ Redistributables: While related to application runtimes, the common-controls issue is more about core Windows UI elements and their versions, rather than just the C++ runtime libraries. Uninstalling and reinstalling C++ Redistributables was a good attempt, but it didn't hit the exact root cause of this specific common-controls conflict.

Why a Clean Boot Might Not Be Enough (But Can Be Useful)

A clean boot disables non-Microsoft services and startup programs, which helps in troubleshooting by eliminating third-party software as the cause. If the crashes stop during a clean boot, it means a third-party application or service is interfering. However, it won't directly fix corrupt or conflicting manifest files within the WinSxS store itself.

More Targeted Solutions

Since you've already tried sfc and DISM (which are excellent first steps for system file integrity), let's try some more specific approaches:

1. Re-register the common-controls components: This is a more aggressive step and should be approached with caution, as it involves manipulating system files. It's generally not recommended unless you know what you're doing. Instead of trying to manually re-register, we'll focus on ensuring the WinSxS store is healthy.

2. Verify CapCut's Manifest: While you can't easily edit CapCut's internal manifest, you can sometimes find information.

   • Check CapCut's Installation Folder: Look in the CapCut installation directory for any .manifest files. It's unlikely you'll be able to modify them, but it might give you a clue.
   • Contact CapCut Support: Explain the specific "SideBySide" error message with the conflicting common-controls manifest files. They might have a patched version or a known workaround for this specific issue.

3. Use the sxstrace Tool (Advanced Troubleshooting): This is a built-in Windows tool that can provide very detailed information about Side-by-Side assembly loading failures.

   • Open Command Prompt as Administrator.

   • Start Tracing:

     sxstrace trace -logfile:C:\sxstrace.etl
     

   • Reproduce the Error: While sxstrace is running, launch CapCut and try to trigger the crash/error.
   • Stop Tracing:

     sxstrace stop
     

   • Convert to Readable Format:

     sxstrace parse -logfile:C:\sxstrace.etl -outfile:C:\sxstrace.txt
     

   • Analyze sxstrace.txt: Open sxstrace.txt and look for more specific errors related to the common-controls conflict. This file can be very verbose, but it might point to a specific file that's missing or corrupted, or a policy that's preventing the correct version from loading. Look for lines containing "ERROR" or "FAIL".

4. Reinstall or Repair .NET Framework: Although the error specifically mentions common-controls and not explicitly .NET, many applications, including CapCut, rely on various .NET Framework versions. A corrupted .NET installation can sometimes lead to obscure errors.

   • Go to Control Panel > Programs and Features > Turn Windows features on or off.
   • Uncheck all .NET Framework versions (e.g., .NET Framework 3.5, .NET Framework 4.8 Advanced Services).
   • Restart your computer.
   • Go back to Turn Windows features on or off and re-check the .NET Framework versions. Windows will download and reinstall them.

5. Reinstall All Microsoft Visual C++ Redistributables Correctly

   The key is to install both x86 and x64 versions side-by-side for all major years:

   • Go to this official Microsoft link:
     Microsoft Visual C++ Redistributable Latest Supported Downloads

   • Install both x64 and x86 versions for:

     • 2008

     • 2010

     • 2012

     • 2013

     • 2015–2022

   Don’t skip the older versions. Some modern apps still rely on legacy DLLs.

6. Ensure CapCut Is Using the Correct Architecture

   You have an AMD Ryzen 5700X and Radeon 7600XT, so you're on a 64-bit OS. But CapCut might be launching a 32-bit executable and loading 64-bit manifests.

   Check:

   • Navigate to C:\Users\Bertram\AppData\Local\CapCut\

   • Right-click CapCut.exe > Properties > Details

   • Confirm whether it says 32-bit or 64-bit

   If it's 32-bit:

   • Try installing a 64-bit version of CapCut (if available).

   • Or use Compatibility Mode: Right-click CapCut.exe > Properties > Compatibility tab > Check “Run this program in compatibility mode for Windows 8.”

7. Try Side-by-Side Cleanup via Registry & Folder Purge (Advanced)

   Only if you're comfortable:

   • Navigate to C:\Windows\WinSxS\Manifests\

   • Back up the conflicting manifest files you saw in the Event Viewer.

   • Attempt to remove the incorrect architecture version, but only after registry backup and System Restore point creation.

   But: This is risky, and usually not needed if the issue is with mismatched VC++ versions. Try other steps first.

8. Consider a Repair Install of Windows (In-Place Upgrade): This is a more drastic step but can resolve deeper system file corruption issues without losing your personal files and installed applications.

   • Download the Windows 10/11 Media Creation Tool from Microsoft's official website.
   • Run the tool and choose the option to "Upgrade this PC now" (or create installation media and run setup.exe from within Windows).
   • Follow the prompts, making sure to select "Keep personal files and apps." This will essentially reinstall Windows over your existing installation, often fixing underlying system issues including those in the WinSxS store.

9. Clean Boot ≠ Clean Install

   A Clean Boot disables non-Microsoft services and startup items—it won’t delete or “clean up” WinSxS components. So:

   • A Clean Boot won't fix manifest conflicts.

   • A Clean Install of Windows would, but that’s a last resort.

10. Use Dependency Walker

    You can use Dependency Walker (depends.exe) or Process Monitor to find exactly what DLL CapCut is trying to load and from where.

Regarding your question about a "clean boot of Windows" removing files:

A "clean boot" as a troubleshooting step (disabling startup items and non-Microsoft services) doesn't remove files. It just prevents them from running. If you meant a clean installation of Windows, then yes, that would completely wipe your drive and reinstall Windows from scratch, effectively removing all manifest files (and everything else) and starting fresh. However, a clean installation is a last resort due to the significant effort involved in backing up data and reinstalling all applications.

Recommendation:

1. Start with sxstrace: This is your best bet for diagnosing the precise nature of the common-controls conflict. It provides invaluable diagnostic information.
2. If sxstrace doesn't yield a clear solution, try reinstalling/repairing .NET Framework.
3. Reinstall all VC++ Redistributables (x86 and x64 versions) from 2008 to 2022.
4. Check CapCut architecture and use compatibility mode if it's 32-bit.
5. Avoid deleting WinSxS files manually unless you're very experienced.
6. Clean install of Windows should be considered only if the problem persists and system-wide SxS errors spread to other apps.
7. Contact CapCut Support: Email them at [email protected] and provide them with the sxstrace output if it looks relevant.
8. As a last resort, consider a Repair Install of Windows. This is less disruptive than a clean install but can fix many system-level problems.

Do NOT proceed with a clean installation of Windows unless all other options have been exhausted and you are prepared for the extensive reinstallation process.

Let us know if you want direct links to all redistributable versions or a script to uninstall/reinstall them automatically.