Side by side configuration is incorrect

Anonymous
2015-08-06T16:50:47+00:00

WINDOWS 10 Pro error The application has failed to start because the side by side configuration is incorrect please see the application event log or use the command line sxstrace.exe tool for more detail.

I am getting the error "

"WINDOWS 10 error The application has failed to start because the side by side configuration is incorrect please see the application event log or use the command line sxstrace.exe tool for more detail." for every application that i try to launch.

I can't Install Quick Time App

Please help 

***Post moved by the moderator to the appropriate forum category.***

*Modified title for accuracy*

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

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2015-08-09T20:24:51+00:00

Hi,

Thank you for posting on Microsoft Community. I understand the inconvenience you are facing. I apologies for the delay in reply. I will certainly help you with this.

This error may happen due to system file corruption or Visual C++ redistributable package corruption. I suggest you to follow the below given methods:

Method 1:

Kindly download and install Microsoft Visual C++ 2013 Redistributable Packagefrom below given link and check if it helps:

Visual C++ Redistributable Packages for Visual Studio 2013

http://www.microsoft.com/en-in/download/details.aspx?id=40784

Method 2:

I suggest you to run System file checker. System File checker (SFC) scan is done to check if there are any corrupted system files that could be causing this issue. Kindly follow the below given steps:

  • Press Windows key + X, select Command prompt (Admin) to bring up elevated Command prompt.
  • In Command prompt type sfc/scannow and press enter.
  • Restart the computer.

If no corrupted system files were found in the previous state, then I suggest you to try the following steps: 

  • Open command prompt by pressing Windows key + X and selecting “Command prompt admin”.
  • In command prompt, type the following commands and press Enter after each command:

                DISM.exe /Online /Cleanup-image /Scanhealth

DISM.exe /Online /Cleanup-image /Restorehealth

  • Close the command prompt and restart the PC and check if it works.

Hope this information helps. Please post back with the results, we will be glad to assist you further.

Thank you.

Was this answer helpful?

1100+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2016-08-25T01:24:13+00:00

The problem was corrupted Google Chrome, my default browser.  I deleted the program and installed a new one.  It works now.

Was this answer helpful?

600+ people found this answer helpful.
0 comments No comments

196 additional answers

Sort by: Most helpful
  1. Anonymous
    2018-02-26T03:39:16+00:00

    .......

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-02-26T00:29:22+00:00

    Hi,

    Thank you for posting on Microsoft Community. I understand the inconvenience you are facing. I apologies for the delay in reply. I will certainly help you with this.

    This error may happen due to system file corruption or Visual C++ redistributable package corruption. I suggest you to follow the below given methods:

    Method 1:

    Kindly download and install Microsoft Visual C++ 2013 Redistributable Packagefrom below given link and check if it helps:

    Visual C++ Redistributable Packages for Visual Studio 2013

    http://www.microsoft.com/en-in/download/details.aspx?id=40784

    Method 2:

    I suggest you to run System file checker. System File checker (SFC) scan is done to check if there are any corrupted system files that could be causing this issue. Kindly follow the below given steps:

    • Press Windows key + X, select Command prompt (Admin) to bring up elevated Command prompt.
    • In Command prompt type sfc/scannow and press enter.
    • Restart the computer.

    If no corrupted system files were found in the previous state, then I suggest you to try the following steps: 

    • Open command prompt by pressing Windows key + X and selecting “Command prompt admin”.
    • In command prompt, type the following commands and press Enter after each command:

                    DISM.exe /Online /Cleanup-image /Scanhealth

    DISM.exe /Online /Cleanup-image /Restorehealth

    • Close the command prompt and restart the PC and check if it works.

    Hope this information helps. Please post back with the results, we will be glad to assist you further.

    Thank you.

    Here are the error lines I received:

    2018-02-25 18:58:10, Error                 DISM   DISM Package Manager: PID=17800 TID=18024 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80070570)

    2018-02-25 18:58:10, Error                 DISM   DISM Package Manager: PID=17800 TID=18024 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x80070570)

    2018-02-25 18:58:10, Error                 DISM   DISM Package Manager: PID=17800 TID=18024 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x80070570)

    2018-02-25 18:58:10, Error                 DISM   DISM Package Manager: PID=17800 TID=18024 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80070570)

    2018-02-25 18:58:10, Info                  DISM   DISM Package Manager: PID=17800 TID=18024 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine

    2018-02-25 18:58:10, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80070570

    2018-02-25 19:25:16, Info                  CSI    00000002 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0x9012cfd850

    2018-02-25 19:25:16, Info                  CSI    00000003 Poqexec successfully registered in [l:12 ml:13]'SetupExecute'

    2018-02-25 19:25:16, Info                  CSI    00000004 CSI Store 2303194431136 initialized

    2018-02-25 19:25:16, Info                  CSI    00000005 StoreCorruptionRepair transaction begun. WcpVersion: [l:37]'10.0.16299.245 (WinBuild.160101.0800)'.

    2018-02-25 19:25:16, Info                  CSI    00000006@2018/2/26:00:25:16.138 Starting corruption detection (InnerFlags=5)

    2018-02-25 19:25:16, Info                  CBS    FLOW: Entering stage: CheckCsi

    2018-02-25 19:25:22, Info                  CSI    00000007 Hashes for file member [l:26]'requirePath-config-core.js' do not match.

     Expected: {l:32 b:74bf5b1a8c3a85881d9445b2d0fc76ad24357ce9acf16ac5f7eed286fff3c1d8}.

     Actual: {l:32 b:9688ec46af8fa56e8423a06a9e420db47500eb701e44ba3855faf7984ed1a0a6}.

    2018-02-25 19:25:51, Info                  CSI    00000008 Hashes for file member [l:7]'SOS.dll' do not match.

     Expected: {l:32 b:fcb331ef4aef793a5a4820990bafa87dc29215521722223c2f27b29fcf48b045}.

     Actual: {l:32 b:24633ff93f6f4fd8c61c17330b457346ea7c00fc1557bdd1ae8fe09b7d600d1d}.

    2018-02-25 19:26:30, Info                  CSI    00000009 Hashes for file member [l:17]'msmqtrcRemove.mof' do not match.

     Expected: {l:32 b:8ced38793420a7f2e85fadd4fdcaa1ab6c64dda8f0ba2c100b33f379b7acd350}.

     Actual: {l:32 b:83d771db873e3c4eb3c0bfd3272d33220f6216a850711f261e753525d775c970}.

    2018-02-25 19:26:30, Info                  CSI    0000000a Hashes for file member [l:17]'msmqtrcRemove.mof' do not match.

     Expected: {l:32 b:8ced38793420a7f2e85fadd4fdcaa1ab6c64dda8f0ba2c100b33f379b7acd350}.

     Actual: {l:32 b:83d771db873e3c4eb3c0bfd3272d33220f6216a850711f261e753525d775c970}.

    2018-02-25 19:26:30, Info                  CSI    0000000b Hashes for file member [l:12]'mqlogmgr.dll' do not match.

     Expected: {l:32 b:20b3678d1b4ab8c793d6fcc295cc33984bdfd16e3d10cd8b507c577115820596}.

     Actual: {l:32 b:93fd4a46ac18f9ca8879b7760cbd62b78e18c228f770dfe6c1b1774184c592e6}.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-02-26T00:21:28+00:00

    Hi,

    Thank you for posting on Microsoft Community. I understand the inconvenience you are facing. I apologies for the delay in reply. I will certainly help you with this.

    This error may happen due to system file corruption or Visual C++ redistributable package corruption. I suggest you to follow the below given methods:

    Method 1:

    Kindly download and install Microsoft Visual C++ 2013 Redistributable Packagefrom below given link and check if it helps:

    Visual C++ Redistributable Packages for Visual Studio 2013

    http://www.microsoft.com/en-in/download/details.aspx?id=40784

    Method 2:

    I suggest you to run System file checker. System File checker (SFC) scan is done to check if there are any corrupted system files that could be causing this issue. Kindly follow the below given steps:

    • Press Windows key + X, select Command prompt (Admin) to bring up elevated Command prompt.
    • In Command prompt type sfc/scannow and press enter.
    • Restart the computer.

    If no corrupted system files were found in the previous state, then I suggest you to try the following steps: 

    • Open command prompt by pressing Windows key + X and selecting “Command prompt admin”.
    • In command prompt, type the following commands and press Enter after each command:

                    DISM.exe /Online /Cleanup-image /Scanhealth

    DISM.exe /Online /Cleanup-image /Restorehealth

    • Close the command prompt and restart the PC and check if it works.

    Hope this information helps. Please post back with the results, we will be glad to assist you further.

    Thank you.

    Here are the error lines I received:

    2018-02-25 18:58:10, Error                 DISM   DISM Package Manager: PID=17800 TID=18024 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80070570)

    2018-02-25 18:58:10, Error                 DISM   DISM Package Manager: PID=17800 TID=18024 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x80070570)

    2018-02-25 18:58:10, Error                 DISM   DISM Package Manager: PID=17800 TID=18024 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x80070570)

    2018-02-25 18:58:10, Error                 DISM   DISM Package Manager: PID=17800 TID=18024 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80070570)

    2018-02-25 18:58:10, Info                  DISM   DISM Package Manager: PID=17800 TID=18024 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine

    2018-02-25 18:58:10, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80070570

    Was this answer helpful?

    0 comments No comments