Jump to content

chrome the application has failed to start side-by-side configuration is incorrect

kennysarmy

By kennysarmy
in Windows 10

 Share

Recommended Posts

kennysarmy

kennysarmy

Posted
Posted

We're being plagued by this error on school laptops.

 

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

 

Capture.JPG

 

It's not happening at all on normal PC's.

 

Has anyone seen anything similar?

kennysarmy

kennysarmy

Posted
  • Author
Posted

I followed some information here: https://windows10skill.com/the-application-has-failed-to-start/

 

and Generated a trace!

 

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

Begin Activation Context Generation.

Input Parameter:

Flags = 0

ProcessorArchitecture = AMD64

CultureFallBacks = en-GB;en;en-US

ManifestPath = C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

AssemblyDirectory = C:\Program Files (x86)\Google\Chrome\Application\

Application Config File =

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

INFO: Parsing Manifest File C:\Program Files (x86)\Google\Chrome\Application\chrome.exe.

INFO: Manifest Definition Identity is (null).

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

INFO: Reference: 72.0.3626.121,language="*",type="win32",version="72.0.3626.121"

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

INFO: Resolving reference for ProcessorArchitecture AMD64.

INFO: Resolving reference for culture en-GB.

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_64\Microsoft.Windows.Common-Controls\6.0.0.0_en-GB_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL.

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

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_64\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 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_64\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 Neutral.

INFO: Applying Binding Policy.

INFO: Auto Servicing Policy redirected assembly version.

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

INFO: Begin assembly probing.

INFO: Attempt to probe manifest at C:\windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.14393.953_none_42151e83c686086b.manifest.

INFO: Manifest found at C:\windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.14393.953_none_42151e83c686086b.manifest.

INFO: End assembly probing.

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

INFO: Resolving reference for ProcessorArchitecture AMD64.

INFO: Resolving reference for culture en-GB.

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_64\Microsoft.Windows.Common-Controls.mui\6.0.14393.953_en-GB_6595b64144ccf1df\Microsoft.Windows.Common-Controls.mui.DLL.

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

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_64\Microsoft.Windows.Common-Controls.mui\6.0.14393.953_en_6595b64144ccf1df\Microsoft.Windows.Common-Controls.mui.DLL.

INFO: Did not find manifest for culture en.

INFO: End assembly probing.

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_64\Microsoft.Windows.Common-Controls.mui\6.0.14393.953_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 72.0.3626.121,language="*",type="win32",version="72.0.3626.121".

INFO: Resolving reference for ProcessorArchitecture 72.0.3626.121,language="*",type="win32",version="72.0.3626.121".

INFO: Resolving reference for culture en-GB.

INFO: Applying Binding Policy.

INFO: No binding policy redirect found.

INFO: Begin assembly probing.

INFO: Did not find the assembly in WinSxS.

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

INFO: End assembly probing.

INFO: Resolving reference for culture en.

INFO: Applying Binding Policy.

INFO: No binding policy redirect found.

INFO: Begin assembly probing.

INFO: Did not find the assembly in WinSxS.

INFO: Did not find manifest for culture en.

INFO: End assembly probing.

INFO: Resolving reference for culture en-US.

INFO: Applying Binding Policy.

INFO: No binding policy redirect found.

INFO: Begin assembly probing.

INFO: Did not find the assembly in WinSxS.

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

INFO: End assembly probing.

INFO: Resolving reference for culture Neutral.

INFO: Applying Binding Policy.

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:\Program Files (x86)\Google\Chrome\Application\72.0.3626.121.DLL.

INFO: Attempt to probe manifest at C:\Program Files (x86)\Google\Chrome\Application\72.0.3626.121.MANIFEST.

INFO: Attempt to probe manifest at C:\Program Files (x86)\Google\Chrome\Application\72.0.3626.121\72.0.3626.121.DLL.

INFO: Attempt to probe manifest at C:\Program Files (x86)\Google\Chrome\Application\72.0.3626.121\72.0.3626.121.MANIFEST.

INFO: Did not find manifest for culture Neutral.

INFO: End assembly probing.

ERROR: Cannot resolve reference 72.0.3626.121,language="*",type="win32",version="72.0.3626.121".

ERROR: Activation Context generation failed.

End Activation Context Generation.

Arthur

Arthur

Posted
Posted (edited)
We're being plagued by this error on school laptops.

According to this, Google Chrome requires the Visual C++ 2005 redistributable (although it seems to work fine with just the 2013 redists installed). :confused:

Edited by Arthur
kennysarmy

kennysarmy

Posted
  • Author
Posted
According to this, Google Chrome requires the Visual C++ 2005 redistributable (although it seems to work fine with just the 2013 redists installed). :confused:

 

installed both the x64 and x86 versions of the Visual C++ 2005 redistributable and error remains :(

 

- - - Updated - - -

 

I've also tried installing the 2010 and 2017 versions with on success

kennysarmy

kennysarmy

Posted
  • Author
Posted
Strange. Does uninstalling and reinstalling Chrome again make any difference?

 

Chrome is pushed out as an MSI - when we've had this issue before, taking the PC off the domain and re-joining seems to fix it (that will force a Chrome uninstall/reinstall) - but I was trying to figure out a way to fix it without doing that :(

 

I'd also like to get to the bottom of why it occurs just on our laptops!

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing


×
×
  • Create New...