Win7 x64 Audacity 2.1.3 Side by Side Conflict Errors

[Sirandar]

On my system Event Viewer identified a Side by Side conflict with Visual Studio 2010 Tools for Office Runtime.

I didn't need VS2010 anymore so I uninstalled it and the error went away.

Audacity seemed to work OK even with VS2010 but I didn't test every feature.

[Gale Andrews]

Do you mean you could not launch Audacity with VS 2010 installed?

If you ever want to build Audacity you should use Visual Studio 2013.


Gale

[sevendy]

I am also getting a sidebyside error that does not occur with 2.1.2:

Activation context generation failed for "C:\Program Files (x86)\Audacity\audacity.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.7601.18837_none_fa3b1e3d17594757.manifest. Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_41e855142bd5705d.manifest.

Error occurs on launch, however, program seems to run fine. Reverted to 2.1.2, no more errors. (Win 7 x64)

[Gale Andrews]

I am also getting a sidebyside error that does not occur with 2.1.2:

Activation context generation failed for "C:\Program Files (x86)\Audacity\audacity.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.7601.18837_none_fa3b1e3d17594757.manifest. Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_41e855142bd5705d.manifest.

Thank you for the report.

It is good that you monitor Windows so closely, but I am unclear what the practical problem is if Audacity launches. I sometimes see this error too (it is not repeatable), but I see no ill-effects.

I have noticed the embedded manifest changed between 2.1.2 and 2.1.3. This is probably because a different computer was used to build 2.1.3 than 2.1.2. This points to a possible solution that a testing build could be provided with no embedded manifest but with the 2.1.2 manifest shipped with the application. This has not been tried out or commented on yet by a developer.


Gale

[Gale Andrews]

At the moment, it looks like on the machine being used for building, codesigning the 2.1.3 release so that there is a named publisher causes the change in the manifest. Without codesigning, the embedded manifest in 2.1.3 is the same as in 2.1.2.

Obviously the codesigning is desirable because it improves security. So this may point to re-examining/updating the tools used to do the signing.


Gale

[Sirandar]

As a further note, Even when I remove Visual Studio for Office tools, if you run any MS Office 2010 office app, Visual Studio Tools automagically re installs after boot.

This error occurs on both my Win10 laptop and my Win7 X64 desktop.

I have yet to see any actual issues associated with this.

[ad98]

It is good that you monitor Windows so closely, but I am unclear what the practical problem is if Audacity launches.

On my machine, the "practical problem" is:

An Audacity SxS error is logged multiple times in each Windows session even when Audacity is not launched, so Event Log fills up with errors. It is a nuisance to constantly clear those errors just to read other events which may appear in the log.

[Gale Andrews]

An Audacity SxS error is logged multiple times in each Windows session even when Audacity is not launched

Where exactly does that get logged in Event Viewer? What is the Event ID and is it the same ID as when launching Audacity?

I would go back to 2.1.2 if Windows monitoring is important to you, or try recompiling Audacity 2.1.3 with the 2.1.2 manifest embedded. The developers will not reissue 2.1.3 for this.


Gale

[Lint]

An Audacity SxS error is logged multiple times in each Windows session even when Audacity is not launched

Where exactly does that get logged in Event Viewer? What is the Event ID and is it the same ID as when launching Audacity?

I would go back to 2.1.2 if Windows monitoring is important to you, or try recompiling Audacity 2.1.3 with the 2.1.2 manifest embedded. The developers will not reissue 2.1.3 for this.

Its in 'Windows Logs:Application. The Event ID is 78. Oddly in my case its showing up in my log. even tho I have not run audacity in some time, as such it was very surprising to me to see an Audacity related error.

[ad98]

Where exactly does that get logged in Event Viewer? What is the Event ID

Log Name: Application
Source: SideBySide
Event ID: 80
Level: Error

Description: Activation context generation failed for "C:\Program Files (x86)\Audacity\audacity.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.7601.18837_none_fa3b1e3d17594757.manifest. Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_41e855142bd5705d.manifest.

<EventData>
C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_fa3b1e3d17594757.manifest
C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_41e855142bd5705d.manifest

Note: This error has been logged 14 times in the current session.

and is it the same ID as when launching Audacity?

Yes. The same event was logged 3 times upon first launch of Audacity during the current Windows session.

The developers will not reissue 2.1.3 for this.

I only use it on rare occasions and do not expect an immediate resolution. Just documenting the issue so it will be addressed in future releases, thanks.