Win7 x64 Audacity 2.1.3 Side by Side Conflict Errors

[Sirandar]

Hi All

https://forums.adobe.com/thread/1304813

This fixed this issue for me ...... note that ProgramFilesX86 has write protection .... you need to copy Audacity.exe to the desktop ....do this and copy the modified version back.

[steve]

Hi All

https://forums.adobe.com/thread/1304813

This fixed this issue for me ...... note that ProgramFilesX86 has write protection .... you need to copy Audacity.exe to the desktop ....do this and copy the modified version back.

Not helpful.
That link goes to a two page topic with no clear resolution.
Also, your first post in this topic says that you solved it.

[Gale Andrews]

https://forums.adobe.com/thread/1304813

This fixed this issue for me ...... note that ProgramFilesX86 has write protection .... you need to copy Audacity.exe to the desktop ....do this and copy the modified version back.

Copy back the modified version of what? Are you referring to changing the manifest?


Gale

[Gale Andrews]

try recompiling Audacity 2.1.3 with the 2.1.2 manifest embedded.

I understand that most users would not want to do that.

There is another method that less sophisticated users could employ which is to use a resources editor like Resource Hacker to change the manifest embedded in 2.1.3 to that for 2.1.2. Here is a version of 2.2.0-alpha that was changed to the 2.1.2 manifest using that method http://gaclrecords.org.uk/bugs/audacity ... nifest.zip.

If anyone wants to try that and see it it gives SxS errors, just extract the file from the zip, place it in your 2.1.3 installation folder and run it instead of audacity.exe. Make sure the original audacity.exe is not running before you test.


Gale

[FiftyCaliber]

So I've been having blue screens and was looking in Event Viewer to figure out the cause. Now I'm 99% sure this has nothing to do with the blue screens but I figured I'd check it out and fix it if possible anyway.

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

I've been getting this exact same error. It was logged 4 times, in the span of 38 minutes without ever having opened Audacity during the session.

try recompiling Audacity 2.1.3 with the 2.1.2 manifest embedded.

I understand that most users would not want to do that.

There is another method that less sophisticated users could employ which is to use a resources editor like Resource Hacker to change the manifest embedded in 2.1.3 to that for 2.1.2. Here is a version of 2.2.0-alpha that was changed to the 2.1.2 manifest using that method http://gaclrecords.org.uk/bugs/audacity ... nifest.zip.

If anyone wants to try that and see it it gives SxS errors, just extract the file from the zip, place it in your 2.1.3 installation folder and run it instead of audacity.exe. Make sure the original audacity.exe is not running before you test.


Gale

This fixed it for me, at least as far as I can tell thus far. No error when opening Audacity with that .exe and no errors so far without having opened Audacity.

[Gale Andrews]

So I've been having blue screens and was looking in Event Viewer to figure out the cause. Now I'm 99% sure this has nothing to do with the blue screens but I figured I'd check it out and fix it if possible anyway.

Audacity can't crash the computer. You can try WhoCrashed which is often able to identify the source of the problem in simple terms.

try recompiling Audacity 2.1.3 with the 2.1.2 manifest embedded.

I understand that most users would not want to do that.

There is another method that less sophisticated users could employ which is to use a resources editor like Resource Hacker to change the manifest embedded in 2.1.3 to that for 2.1.2. Here is a version of 2.2.0-alpha that was changed to the 2.1.2 manifest using that method http://gaclrecords.org.uk/bugs/audacity ... nifest.zip.

If anyone wants to try that and see it it gives SxS errors, just extract the file from the zip, place it in your 2.1.3 installation folder and run it instead of audacity.exe. Make sure the original audacity.exe is not running before you test.


Gale

This fixed it for me, at least as far as I can tell thus far. No error when opening Audacity with that .exe and no errors so far without having opened Audacity.

Thanks for letting us know.


Gale

[FiftyCaliber]

So I ended up solving the blue screen issue and yes it had nothing to do with Audacity of course. Regarding the Audacity error however, it came back when I loaded a project from the actual project file. However that is only because it ran the original audacity.exe (even if I moved or renamed it) but after deleting it and renaming the 2.2.0 alpha one to take its place it works totally fine no errors at all. Judging from what I read in this thread and another I doubt that the error really did anything harmful however its still nice to be error free.

[huckleberrypie]

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)

I can confirm this on Windows 10 Pro x64, version 10.0.15063. For a while I thought Windows was going bonkers again as SxS errors can be a real pain and in some cases require a complete Windows reinstall, but downgrading or modifying the manifest seems to do the trick - rolling back to 2.1.2 got rid of the error log spam.

[nwillis]

I have only just started to use Audacity 213 and have noticed that my event viewer has the side by side error id 8-0 in my event viewer as is mentioned in several tickets. Would I be correct in saying that the bottom line is that this is not an issue for version 212 ?

Thx.

[Melchior]

I just started using Audacity just this past week or so..
and was checking my Windows System Event logs and came across the
SideBySide errors... any time I ran Audacity.. same version v2.1.3

Any word on this issue? bug? fixes?