Multiple SideBySide Errors

Checking in the Event Viewer, I found 7 of these errors occurring within 15 minutes of each other. At the time that they occurred, the system was idle and doesn't have anything to do with rebooting. They originate from totally different programs, and happened at a times hours apart from the time of any scans scheduled by Outpost Security Suite. Here is a list of the errors:

Activation context generation failed for "C:\Program Files (x86)\BurMan\Nero 8\Nero Toolkit\DiscSpeed.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16385_none_fa645303170382f6.manifest. Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16385_none_421189da2b7fabfc.manifest.

3 instances in a row of:

Activation context generation failed for "C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\bin\ia64\pgocvt.exe". Dependent Assembly Microsoft.VC90.CRT,processorArchitecture="ia64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",versi on="9.0.21022.8" could not be found. Please use sxstrace.exe for detailed diagnosis.


Activation context generation failed for "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll" on line 3. The value "MAJOR_VERSION.MINOR_VERSION.BUILD_NUMBER_MAJOR.BUILD_NUMBER_MINOR" of attribute "version" in element "assemblyIdentity" is invalid.

Activation context generation failed for "c:\program files (x86)\SysMan\protection\Spy\Spybot 1.62\DelZip179.dll".Error in manifest or policy file "c:\program files (x86)\SysMan\protection\Spy\Spybot 1.62\DelZip179.dll" on line 8. The value "*" of attribute "language" in element "assemblyIdentity" is invalid.

Maybe I should just look at these separately, but the timing suggests a commonality...can anyone suggest what this may be?

EDIT: I attempted to run sxstrace as suggested in some, but what appeared to be a DOS window just appeared for a flash and disappeared. How should it be used?

Hey SM,

Here's some instructions for running sxstrace:
Junfeng Zhang's Windows Programming Notes : Diagnosing SideBySide failures

I'm seeing the same errors in my event log. I followed the instructions and created the .etl file but when I ran the converter to create the text file it was empty. I tried a few times. Sorry I wasn't much help. Maybe you'll have better luck.

First I ran the first sxstrace comand to enable sxstrace (as in the instructions) then I tried to run pgocvt.exe from both the command line and win explorer while the trace was enabled. Then I stopped the trace and saw it generated a .etl file, then I ran the sxstrace parse command to convert it to text, but as I said, the txt file was empty????

I noticed these events started about 4 days ago - at about this time I upgraded lavasoft AdAware and noticed during the install it said it would install new vc runtimes - I didn't think anything of it at the time but now I'm wondering if I hosed my machine. I haven't seen any side effects other than the event logs and my machine isn't the IA64 version, it's the amd64 so maybe it's no problem. One of the erorrs mentioned a problem with Windows Live Movie Maker but I just ran it and it seems OK.

Let me know if you find anything & good luck.

I restored to the day before all the MS updates. I just had my first reboot without any sidebyside errors since those updates had been installed.

Seems to have addressed my issues with sidebyside, but it is a shame I don't know which of the 24 updates caused it.

Now for the Wininit warnings. Not causing a problem, but annoying.

I sure wish someone had found the true source of these errors. After the restore my HTPC continues to work fine again. No sidebyside errors and no issues of the cursor becoming unresponsive.

I don't think a solution would be for me to shutdown all MS updates forever.

Sorry for the thread necromancy, but I was just wondering if anyone ever found out what was going on with this. It seems weird that it is running a program in a bin\ia64 directory, which would suggest that the programs are built for the Itanium architecture. As far as I know, they haven't even built Windows 7 for IA64 (which is not the same thing as x64, the 64-bit extensions to x86 which most PC's use now.)