Windows 10: The application has failed to start because its side-by-side configuration is incorrect

Discus and support The application has failed to start because its side-by-side configuration is incorrect in Windows 10 BSOD Crashes and Debugging to solve the problem; I've successfully installed SuperPro Designer v9.0 on my Windows 10, however every time I want to open the app it shows "The application has failed to... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Karen Geraldine, Apr 4, 2019.

  1. The application has failed to start because its side-by-side configuration is incorrect


    I've successfully installed SuperPro Designer v9.0 on my Windows 10, however every time I want to open the app it shows "The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail"


    I have tried installing these on my laptop:

    1. Microsoft Visual C++ 2005 Redistributable
    2. Microsoft Visual C++ 2008 Redistributable
    3. Microsoft Visual C++ 2010 Redistributable

    However, none of them worked and it still shows the same problem.


    Here is the content of my sxstrace.exe file:


    =================

    Begin Activation Context Generation.

    Input Parameter:

    Flags = 0

    ProcessorArchitecture = Wow32

    CultureFallBacks = en-US;en

    ManifestPath = C:\Users\Karen Geraldine\AppData\Local\Programs\Intelligen\SuperPro Designer\v9.0\Designer.exe

    AssemblyDirectory = C:\Users\Karen Geraldine\AppData\Local\Programs\Intelligen\SuperPro Designer\v9.0\

    Application Config File =

    -----------------

    INFO: Parsing Manifest File C:\Users\Karen Geraldine\AppData\Local\Programs\Intelligen\SuperPro Designer\v9.0\Designer.exe.

    INFO: Manifest Definition Identity is Microsoft.Windows.Designer,processorArchitecture="X86",type="win32",version="1.0.0.0".

    INFO: Reference: Microsoft.Windows.Common-Controls,language="*",processorArchitecture="x86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0"

    INFO: Reference: Microsoft.VC90.MFC,processorArchitecture="x****",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8"

    INFO: Reference: Microsoft.VC90.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8"

    INFO: Resolving reference Microsoft.Windows.Common-Controls,language="*",processorArchitecture="x86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0".

    INFO: Resolving reference for ProcessorArchitecture WOW64.

    INFO: Resolving reference for culture en-US.

    INFO: Applying Binding Policy.

    INFO: No publisher policy found.

    INFO: No binding policy redirect found.

    INFO: Begin assembly probing.

    INFO: Did not find the assembly in WinSxS.

    INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls\6.0.0.0_en-US_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL.

    INFO: Did not find manifest for culture en-US.

    INFO: End assembly probing.

    INFO: Resolving reference for culture en.

    INFO: Applying Binding Policy.

    INFO: No publisher policy found.

    INFO: No binding policy redirect found.

    INFO: Begin assembly probing.

    INFO: Did not find the assembly in WinSxS.

    INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls\6.0.0.0_en_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL.

    INFO: Did not find manifest for culture en.

    INFO: End assembly probing.

    INFO: Resolving reference for culture Neutral.

    INFO: Applying Binding Policy.

    INFO: No publisher policy found.

    INFO: No binding policy redirect found.

    INFO: Begin assembly probing.

    INFO: Did not find the assembly in WinSxS.

    INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls\6.0.0.0__6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL.

    INFO: Did not find manifest for culture Neutral.

    INFO: End assembly probing.

    INFO: Resolving reference for ProcessorArchitecture x86.

    INFO: Resolving reference for culture en-US.

    INFO: Applying Binding Policy.

    INFO: No publisher policy found.

    INFO: No binding policy redirect found.

    INFO: Begin assembly probing.

    INFO: Did not find the assembly in WinSxS.

    INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls\6.0.0.0_en-US_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL.

    INFO: Did not find manifest for culture en-US.

    INFO: End assembly probing.

    INFO: Resolving reference for culture en.

    INFO: Applying Binding Policy.

    INFO: No publisher policy found.

    INFO: No binding policy redirect found.

    INFO: Begin assembly probing.

    INFO: Did not find the assembly in WinSxS.

    INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls\6.0.0.0_en_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL.

    INFO: Did not find manifest for culture en.

    INFO: End assembly probing.

    INFO: Resolving reference for culture Neutral.

    INFO: Applying Binding Policy.

    INFO: Auto Servicing Policy redirected assembly version.

    INFO: Post policy assembly identity is Microsoft.Windows.Common-Controls,processorArchitecture="x86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.17134.48".

    INFO: Begin assembly probing.

    INFO: Attempt to probe manifest at C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.17134.48_none_fc5f584151310644.manifest.

    INFO: Manifest found at C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.17134.48_none_fc5f584151310644.manifest.

    INFO: End assembly probing.

    INFO: Resolving reference Microsoft.Windows.Common-Controls.mui,language="*",processorArchitecture="x86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.17134.48".

    INFO: Resolving reference for ProcessorArchitecture WOW64.

    INFO: Resolving reference for culture en-US.

    INFO: Applying Binding Policy.

    INFO: No publisher policy found.

    INFO: No binding policy redirect found.

    INFO: Begin assembly probing.

    INFO: Did not find the assembly in WinSxS.

    INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls.mui\6.0.17134.48_en-US_6595b64144ccf1df\Microsoft.Windows.Common-Controls.mui.DLL.

    INFO: Did not find manifest for culture en-US.

    INFO: End assembly probing.

    INFO: Resolving reference for culture en.

    INFO: Applying Binding Policy.

    INFO: No publisher policy found.

    INFO: No binding policy redirect found.

    INFO: Begin assembly probing.

    INFO: Did not find the assembly in WinSxS.

    INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls.mui\6.0.17134.48_en_6595b64144ccf1df\Microsoft.Windows.Common-Controls.mui.DLL.

    INFO: Did not find manifest for culture en.

    INFO: End assembly probing.

    INFO: Resolving reference for ProcessorArchitecture x86.

    INFO: Resolving reference for culture en-US.

    INFO: Applying Binding Policy.

    INFO: No publisher policy found.

    INFO: No binding policy redirect found.

    INFO: Begin assembly probing.

    INFO: Did not find the assembly in WinSxS.

    INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls.mui\6.0.17134.48_en-US_6595b64144ccf1df\Microsoft.Windows.Common-Controls.mui.DLL.

    INFO: Did not find manifest for culture en-US.

    INFO: End assembly probing.

    INFO: Resolving reference for culture en.

    INFO: Applying Binding Policy.

    INFO: No publisher policy found.

    INFO: No binding policy redirect found.

    INFO: Begin assembly probing.

    INFO: Did not find the assembly in WinSxS.

    INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.Windows.Common-Controls.mui\6.0.17134.48_en_6595b64144ccf1df\Microsoft.Windows.Common-Controls.mui.DLL.

    INFO: Did not find manifest for culture en.

    INFO: End assembly probing.

    INFO: Resolving reference Microsoft.VC90.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.30729.6161".

    INFO: Resolving reference for ProcessorArchitecture WOW64.

    INFO: Resolving reference for culture Neutral.

    INFO: Applying Binding Policy.

    INFO: No publisher policy found.

    INFO: No binding policy redirect found.

    INFO: Begin assembly probing.

    INFO: Did not find the assembly in WinSxS.

    INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.VC90.MFC\9.0.30729.6161__1fc8b3b9a1e18e3b\Microsoft.VC90.MFC.DLL.

    INFO: Did not find manifest for culture Neutral.

    INFO: End assembly probing.

    INFO: Resolving reference for ProcessorArchitecture x86.

    INFO: Resolving reference for culture Neutral.

    INFO: Applying Binding Policy.

    INFO: No publisher policy found.

    INFO: No binding policy redirect found.

    INFO: Begin assembly probing.

    INFO: Did not find the assembly in WinSxS.

    INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_32\Microsoft.VC90.MFC\9.0.30729.6161__1fc8b3b9a1e18e3b\Microsoft.VC90.MFC.DLL.

    INFO: Attempt to probe manifest at C:\Users\Karen Geraldine\AppData\Local\Programs\Intelligen\SuperPro Designer\v9.0\Microsoft.VC90.MFC.DLL.

    INFO: Attempt to probe manifest at C:\Users\Karen Geraldine\AppData\Local\Programs\Intelligen\SuperPro Designer\v9.0\Microsoft.VC90.MFC.MANIFEST.

    INFO: Attempt to probe manifest at C:\Users\Karen Geraldine\AppData\Local\Programs\Intelligen\SuperPro Designer\v9.0\Microsoft.VC90.MFC\Microsoft.VC90.MFC.DLL.

    INFO: Attempt to probe manifest at C:\Users\Karen Geraldine\AppData\Local\Programs\Intelligen\SuperPro Designer\v9.0\Microsoft.VC90.MFC\Microsoft.VC90.MFC.MANIFEST.

    INFO: Did not find manifest for culture Neutral.

    INFO: End assembly probing.

    ERROR: Cannot resolve reference Microsoft.VC90.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.30729.6161".

    ERROR: Activation Context generation failed.

    End Activation Context Generation.


    If someone would help, I would appreciate it a lot. Thank you.

    :)
     
    Karen Geraldine, Apr 4, 2019
    #1
  2. Phillip Pio, Apr 4, 2019
    #2
  3. Kapil Arya MVP, Apr 4, 2019
    #3
  4. aumza2525 Win User

    The application has failed to start because its side-by-side configuration is incorrect

    "WINDOWS 10 error The application has failed to start because the side by side configuration is incorrect.

    The application has failed to start because the side by side configuration is incorrect.
     
    aumza2525, Apr 4, 2019
    #4
Thema:

The application has failed to start because its side-by-side configuration is incorrect

Loading...
  1. The application has failed to start because its side-by-side configuration is incorrect - Similar Threads - application has failed

  2. The Application has failed to start because its side-to-side configuration is incorrect...

    in Windows 10 Gaming
    The Application has failed to start because its side-to-side configuration is incorrect...: getting this message when using windows 11 https://answers.microsoft.com/en-us/windows/forum/all/the-application-has-failed-to-start-because-its/de21697e-c87d-4efd-8306-a4082ac24a1b
  3. The Application has failed to start because its side-to-side configuration is incorrect...

    in Windows 10 Software and Apps
    The Application has failed to start because its side-to-side configuration is incorrect...: getting this message when using windows 11 https://answers.microsoft.com/en-us/windows/forum/all/the-application-has-failed-to-start-because-its/de21697e-c87d-4efd-8306-a4082ac24a1b
  4. The application has failed to start because its side-by-side configuration is incorrect....

    in Windows 10 Gaming
    The application has failed to start because its side-by-side configuration is incorrect....: The application has failed to start because its side-by-side configuration is incorrect. Please .see the application event log or use the command-line sxstrace.exe tool for more detail اللغة العربية...
  5. The application has failed to start because its side-by-side configuration is incorrect....

    in Windows 10 Software and Apps
    The application has failed to start because its side-by-side configuration is incorrect....: The application has failed to start because its side-by-side configuration is incorrect. Please .see the application event log or use the command-line sxstrace.exe tool for more detail اللغة العربية...
  6. the application has failed to start because its side-by-side configuration is incorrect

    in Windows 10 Gaming
    the application has failed to start because its side-by-side configuration is incorrect: the application has failed to start because its side-by-side configuration is incorrect https://answers.microsoft.com/en-us/windows/forum/all/the-application-has-failed-to-start-because-its/64c22daf-900b-4e92-9dd4-1dfc3f9677b2
  7. The application has failed to start because its side to side configuration is incorrect...

    in Windows 10 Software and Apps
    The application has failed to start because its side to side configuration is incorrect...: I recently changed over from an Acer laptop running Windows 10 to now Microsoft Surface Pro running windows 10.All I'm trying to do is to get my Logitech M570 mouse "setpoint" program to work like it did on the Acer. Primarily so I can set my mouse buttons to my own...
  8. the application has failed to start because of its side-by-side configuration is incorrect

    in Windows 10 Network and Sharing
    the application has failed to start because of its side-by-side configuration is incorrect: Everytime i open any apps except for system apps it gives me this error 'the application has failed to start because of its side-by-side configuration is incorrect'. i can open my opera browser but not any other apps. all downloaded apps gives this error. i cant download...
  9. This application has failed to start because its side-by-side configuration is incorrect.

    in Windows 10 BSOD Crashes and Debugging
    This application has failed to start because its side-by-side configuration is incorrect.: When opening a file, the error "This application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail" comes up. I tried to download and install the Microsoft...
  10. The application has failed to start because its-side-by-side configuration is incorrect

    in Windows 10 Customization
    The application has failed to start because its-side-by-side configuration is incorrect: Hello, I'm having an issue with my computer, when I try to open almost ANY application I get the following error: "The application has failed to start because its-side-by-side configuration is incorrect" I have tried installing all the reinstalling all c++...