Side-by-side incorrect error & not able to install VC++2005

[MichelMylos]

Hi everyone,


I have a problem on my parent's PC (running W7 pro 64 bits). I don't know if it's due to an update error or a forced reboot of someone but, suddenly one day, for almost every program they started they got the error message "The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail...". So I've first tried to restore the PC to a previous state but it failed...


Looking on the internet I've found that it was a common problem often caused by the C++ language interpreter and that is was necessary to have a correct installation of the C++redistributable packages.
Not knowing at this time how to know which version of C++ was problematic (I didn't go in the event viewer...), I've tried to uninstall all the C++ packages. It was not easy because the Windows function used to uninstall programs ended up with an error for each package...
However I slowly achieved to do it with the"MicrosoftProgram_Install_and_Unistall.meta.diagcab" program.


After that I've tried to reinstall the last versions of the C++ packages (from 2005 to 2017). But again it was not simple because I've got the side-by-side error for each vcredist***.exe I wanted to install...
After decompressing them though, using the .msi files, I managed to install the packages x86 and x64 of 2008, 2010, 2012, 2013, 2017 (I can see them in the list of the installed programs).
The only one I cannot install is the 2005 version (x86 and x64) because of an 1719 error (message "Windows installer service could not be accessed").
I've tried many things to address this problem (such as the solutions proposed for example here error 1719 windows installer service could not be accessed .... - Microsoft Community by "Nithyananda J", i.e. restarting the Windows installer service, restarting Windows in minimal mode to reinstall the packages, editing the registry, doing scans and even repairing W7...) but without success/change.


For information the sfc scan shows no problem (View attachment CBS.log at the end of the log it's written "repairing 0 components") no more than the command DismCheckHealth...


The few 64bits programs that I've tried to run currently work perfectly but almost all the 32 bits don't work. When I'm looking at the Windows event viewer, the description of side-by-side errors are always (excuse me it's in french):
"La création du contexte d’activation a échoué pour « System Default Context ». Assembly dépendant Microsoft.Windows.IsolationAutomation,language="*",processorArchitecture="x86",publicKeyToken="6595b64144ccf1df",type="win32",version="1.0.0.0" introuvable. Utilisez sxstrace.exe pour un diagnostic détaillé."
or
"La création du contexte d’activation a échoué pour « C:\ nom du programme exécuté .exe ». Assembly dépendant Microsoft.Windows.Common-Controls,language="*",processorArchitecture="X86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0" introuvable."


And the log of the sxstrace command gives for example (long version here View attachment SXSTrace.txt):
=================
Information : résolution de la référence Microsoft.Windows.SystemCompatible,version="6.0.0.0",type="win32",publicKeyToken="6595b64144ccf1df",processorArchitecture="x86".
Information : résolution de la référence pour l’architecture ProcessorArchitecture Unknown.
Information : résolution de la référence pour la culture Unknown.
Information : application de la stratégie de liaison.
Information : la stratégie de traitement automatique a redirigé la version de l’assembly.
Information : l’identité d’assembly de la stratégie de publication est Microsoft.Windows.SystemCompatible,processorArchitecture="x86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.7600.16385".
Information : début de la recherche d’assemblys.
Information : fin de la recherche d’assemblys.
Information : analyse du fichier manifeste System Default Context.
Information : l’identité de la définition du manifeste est Microsoft.Windows.SystemCompatible,processorArchitecture="x86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.7600.16385".
Information : référence : Microsoft.Windows.IsolationAutomation,language="*",processorArchitecture="x86",publicKeyToken="6595b64144ccf1df",type="win32",version="1.0.0.0"
Information : référence : Microsoft.Windows.GdiPlus,language="*",processorArchitecture="x86",publicKeyToken="6595b64144ccf1df",type="win32",version="1.1.0.0"
Information : référence : Microsoft.Windows.Common-Controls,language="*",processorArchitecture="x86",publicKeyToken="6595b64144ccf1df",type="win32",version="5.82.0.0"
Information : résolution de la référence Microsoft.Windows.IsolationAutomation,language="*",processorArc


Can anyone confirm me that the problem is coming from VC++ 2005 and help me to find a solution to bypass its installation problem ?

Thanks a lot !

 

[xilolee]

Hi MichelMylos. :welcome:

I'd first try the Microsoft .NET Framework Repair Tool (click).

Direct download (click).

It seems it could also be used through the windows command line, aka command prompt (started as administrator).
Maybe it's quicker to use it with this command (you should first reach the path/directory/folder in which the tool was downloaded and copied):

NetFxRepairTool /q

(explanation: /q OR /quiet ---> Quiet mode. No user interaction is required and the tool tries all fixes/repairs and saves the log file)

 

[MichelMylos]

Hi xilolee,

yes I've tried this tool but I'm not able to open it due to the side-by-side error (it's a vicious circle !)

 

[xilolee]

Re-try from another windows account.

If it still won't work, try to download and run MS SURT - System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [October 2014] (click).

If it will work and the checksur.log (in c:\windows\Logs\CBS) will show errors not automatically fixed by the tool, open a new topic in sysnative windows update sub-forum.

 

[MichelMylos]

Changing account doesn't solve anything, nor installing the KB947821.
The last checksur log (from 2 week ago but after the begin of side-by-side problems) indicates no error but today I have:


=================================
Checking System Update Readiness.
Binary Version 6.1.7601.23471
2017-11-18 19:46


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store
(f) CSI Manifest Missing 0x00000002 amd64_policy.9.0.microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_3da38fdebd0e6822.manifest amd64_policy.9.0.microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_3da38fdebd0e6822
(f) CSI Payload File Missing 0x00000000 msvcr90.dll amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_99b61f5e8371c1d4


Summary:
Seconds executed: 1019
Found 2 errors
CSI Manifest Missing Total count: 1
CSI Payload File Missing Total count: 1


Unavailable repair files:
winsxs\manifests\amd64_policy.9.0.microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_3da38fdebd0e6822.manifest

 

[xilolee]

Then, this is a job for windows update experts. Open a new topic there. ;-)

 

[MichelMylos]

Hi xilolee, the CheckSUR errors are solved (https://www.sysnative.com/forums/wi...-sur-unavailable-repair-files.html#post200285)
but I still have the side-by-side errors (and impossible to install VC++ 2005). Any idea ?