Windows 10: side-by-side configuration is incorrect.

Discus and support side-by-side configuration is incorrect. in Windows 10 Installation and Upgrade to solve the problem; Getting error message after running command "B2BServer.exe /regserver " The application has failed to start because its side-by-side configuration is... Discussion in 'Windows 10 Installation and Upgrade' started by Sachin Kumar Dubey (SACD), Oct 24, 2018.

  1. SACHIN KUMAR DUBEY (SACD)
    Sachin Kumar Dubey (SACD) Win User

    side-by-side configuration is incorrect.


    Getting error message after running command "B2BServer.exe /regserver " The application has failed to start because its side-by-side configuration is in
    correct. Please see the application event log or use the command-line sxstrace.exe tool for more detail.


    I ran the below command and got the below logs and not able to understand the problem. Please assist.

    sxstrace trace -logfile:sxstrace.et1



    =================
    Begin Activation Context Generation.
    Input Parameter:
    Flags = 0
    ProcessorArchitecture = AMD64
    CultureFallBacks = en-US;en
    ManifestPath = C:\TEMP\B2BServer.exe
    AssemblyDirectory = C:\TEMP\
    Application Config File =
    -----------------
    INFO: Parsing Manifest File C:\TEMP\B2BServer.exe.
    INFO: Manifest Definition Identity is commanifests.exe,type="win32",version="1.0.0.0".
    INFO: Reference: Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762"
    INFO: Reference: Microsoft.VC80.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762"
    INFO: Resolving reference Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762".
    INFO: Resolving reference for ProcessorArchitecture x86.
    INFO: Resolving reference for culture Neutral.
    INFO: Applying Binding Policy.
    INFO: Find publisher policy at C:\Windows\WinSxS\manifests\x86_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_516ac2a30f4be7a6.manifest
    INFO: Publisher Policy redirected assembly version.
    INFO: Post policy assembly identity is Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.8428".
    INFO: Begin assembly probing.
    INFO: Attempt to probe manifest at C:\Windows\WinSxS\manifests\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_d08a11e2442dc25d.manifest.
    INFO: Manifest found at C:\Windows\WinSxS\manifests\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_d08a11e2442dc25d.manifest.
    INFO: End assembly probing.
    INFO: Resolving reference Microsoft.VC80.CRT.mui,language="*",processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.8428".
    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.VC80.CRT.mui\8.0.50727.8428_en-US_1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.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.VC80.CRT.mui\8.0.50727.8428_en_1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.mui.DLL.
    INFO: Did not find manifest for culture en.
    INFO: End assembly probing.
    INFO: Resolving reference Microsoft.VC80.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762".
    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.VC80.MFC\8.0.50727.762__1fc8b3b9a1e18e3b\Microsoft.VC80.MFC.DLL.
    INFO: Attempt to probe manifest at C:\TEMP\Microsoft.VC80.MFC.DLL.
    INFO: Attempt to probe manifest at C:\TEMP\Microsoft.VC80.MFC.MANIFEST.
    INFO: Attempt to probe manifest at C:\TEMP\Microsoft.VC80.MFC\Microsoft.VC80.MFC.DLL.
    INFO: Attempt to probe manifest at C:\TEMP\Microsoft.VC80.MFC\Microsoft.VC80.MFC.MANIFEST.
    INFO: Did not find manifest for culture Neutral.
    INFO: End assembly probing.
    ERROR: Cannot resolve reference Microsoft.VC80.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762".
    ERROR: Activation Context generation failed.
    End Activation Context Generation.

    =================
    Begin Activation Context Generation.
    Input Parameter:
    Flags = 0
    ProcessorArchitecture = Wow32
    CultureFallBacks = en-US;en
    ManifestPath = C:\TEMP\B2BServer.exe
    AssemblyDirectory = C:\TEMP\
    Application Config File =
    -----------------
    INFO: Parsing Manifest File C:\TEMP\B2BServer.exe.
    INFO: Manifest Definition Identity is commanifests.exe,type="win32",version="1.0.0.0".
    INFO: Reference: Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762"
    INFO: Reference: Microsoft.VC80.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762"
    INFO: Resolving reference Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762".
    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.VC80.CRT\8.0.50727.762__1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.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: Find publisher policy at C:\Windows\WinSxS\manifests\x86_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_516ac2a30f4be7a6.manifest
    INFO: Publisher Policy redirected assembly version.
    INFO: Post policy assembly identity is Microsoft.VC80.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.8428".
    INFO: Begin assembly probing.
    INFO: Attempt to probe manifest at C:\Windows\WinSxS\manifests\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_d08a11e2442dc25d.manifest.
    INFO: Manifest found at C:\Windows\WinSxS\manifests\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_d08a11e2442dc25d.manifest.
    INFO: End assembly probing.
    INFO: Resolving reference Microsoft.VC80.CRT.mui,language="*",processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.8428".
    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.VC80.CRT.mui\8.0.50727.8428_en-US_1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.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.VC80.CRT.mui\8.0.50727.8428_en_1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.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.VC80.CRT.mui\8.0.50727.8428_en-US_1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.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.VC80.CRT.mui\8.0.50727.8428_en_1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.mui.DLL.
    INFO: Did not find manifest for culture en.
    INFO: End assembly probing.
    INFO: Resolving reference Microsoft.VC80.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762".
    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.VC80.MFC\8.0.50727.762__1fc8b3b9a1e18e3b\Microsoft.VC80.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.VC80.MFC\8.0.50727.762__1fc8b3b9a1e18e3b\Microsoft.VC80.MFC.DLL.
    INFO: Attempt to probe manifest at C:\TEMP\Microsoft.VC80.MFC.DLL.
    INFO: Attempt to probe manifest at C:\TEMP\Microsoft.VC80.MFC.MANIFEST.
    INFO: Attempt to probe manifest at C:\TEMP\Microsoft.VC80.MFC\Microsoft.VC80.MFC.DLL.
    INFO: Attempt to probe manifest at C:\TEMP\Microsoft.VC80.MFC\Microsoft.VC80.MFC.MANIFEST.
    INFO: Did not find manifest for culture Neutral.
    INFO: End assembly probing.
    ERROR: Cannot resolve reference Microsoft.VC80.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762".
    ERROR: Activation Context generation failed.
    End Activation Context Generation.

    :)
     
    Sachin Kumar Dubey (SACD), Oct 24, 2018
    #1
  2. BLACKYLAD
    blackylad Win User

    Side by side configuration incorrect


    Hi
    I'm attempting to install some software (namely sage accounts ) on a fresh install of windows 10 pro.
    After installation (which appears to be successful) I receive the "error side by side configuration incorrect " when trying to run the app ..
    I have googled the hell out of this and only find threads suggesting deleting all c++ versions and re installing.
    Like this guide here :

    Side by Side Configuration Is Incorrect Error in Windows 10 [FIXED] - Driver Easy
    I have tried several re installs of the software and following the above guide to no avail.. can anyone suggest a fix for this please ??
    TIA
     
    blackylad, Oct 25, 2018
    #2
  3. PHILLIP PIO
    Phillip Pio Win User
    Phillip Pio, Oct 25, 2018
    #3
  4. SOLARIS17
    Solaris17 Win User

    side-by-side configuration is incorrect.

    is there any demand for a system configurator?

    Processor(V) <--drop down arrow
    -AMD(V)
    --Socket(V)
    ---AM2(V)
    ----List of cpu's
    ---939(V)
    ----List of CPU's
    -Intel(V)
    --Socket(V)
    ---775(V)
    ----List of cpu's
    ---771(V)
    ----List of CPU's


    etc etc.
     
    Solaris17, Oct 25, 2018
    #4
Thema:

side-by-side configuration is incorrect.

Loading...

  1. side-by-side configuration is incorrect. - Similar Threads - side side configuration

  2. Side by Side configuration is incorrect

    in Windows 10 Network and Sharing
    Side by Side configuration is incorrect: I recently downloaded an application, that being a game off of M.U.G.E.N which is a game engine, I downloaded it and tried opening it however I keep getting an error that says the side by side configuration is incorrect. I have no clue what that means or how to fix it and if...

  3. Side by Side Configuration is incorrect

    in Windows 10 Gaming
    Side by Side Configuration is incorrect: Hi All,I have just down loaded a new program and when I went to open it and use it I got the following The application has failed to start because its side to side configuration is incorrect see the application event log or use the command-line sxstrace.exe tool for more...

  4. Side by Side Configuration is incorrect

    in Windows 10 Software and Apps
    Side by Side Configuration is incorrect: Hi All,I have just down loaded a new program and when I went to open it and use it I got the following The application has failed to start because its side to side configuration is incorrect see the application event log or use the command-line sxstrace.exe tool for more...

  5. side-by-side configuration is incorrect

    in Windows 10 BSOD Crashes and Debugging
    side-by-side configuration is incorrect: whenever I try to open anything that is not: Microsoft office, mail and google/Firefox/edge, it says "the application has failed to start because the side-by-side configuration is incorrect." I tried googling it and none of it helps. please can somone help me....

  6. Side by side configuration is incorrect

    in Windows 10 BSOD Crashes and Debugging
    Side by side configuration is incorrect: On nearly every application I get a side by side error. Can't reinstall c++ redist because the installer gives the same error. I checked the registry to make sure the values matched. SFC finds issues but can't fix them. DISM sipts out errors no matter how I try to run it,...

  7. side by side configuration is incorrect

    in Windows 10 BSOD Crashes and Debugging
    side by side configuration is incorrect: I have had several apps Microsoft Office 2007, Origin, Steam suddenly stop working, all with the same message "This app has failed to launch because the side-by-side configuration is incorrect. Please see the application event log or use the command line sxstrace.exe tool...

  8. side by side configuration is incorrect

    in Windows 10 Customization
    side by side configuration is incorrect: I have been using Windows 10 from long time ago . But recently , almost all my applications except google chrome & I Tunes are not starting and a message shown is : the application has failed to start because its side-by-side configuration is incorrect . Please see the...

  9. Side-By-Side configuration is incorrect

    in Windows 10 BSOD Crashes and Debugging
    Side-By-Side configuration is incorrect: Hi there. For the past couples of months whenever I try to open an app such as steam or League of Legends on my MSI Laptop with Microsoft 10 OS I am met with an error that says the Side-by-side configuration is incorrect. I understand that this is a pretty common problems and...

  10. "Side-by-side configuration is incorrect"

    in Windows 10 Support
    "Side-by-side configuration is incorrect": Does anyone know anything about this error message that I'm getting when I'm trying to start Logitech Setpoint in Windows 10 64 bit? Apparently it's relatively common for all sorts of applications. 56309

Users found this page by searching for:

  1. windows/assembly/gac_32/microsoft.vc80.crt.mui

    ,

  2. microsoft.vc80.crt.mui

    ,

  3. side by side configuration incorrect