SideBySide Manifests problem & Solution

[KlasN]

I have installed VideoStudio Pro X2, when I'm trying to start the application. I get the error message:

C:\Program Files\Corel\Corel VideoStudio 12\vstudio.exe
"the application has failed to start because its side-by-side configuration is incorrect¡¨ Check the log for more information.

This information I found in the application logfile:

Could not create activation context for C:\Program Files\Corel\Corel VideoStudio 12\vstudio.exe. There is an error in the manifest- or principle file on row . A component version that is required by the application is in conflict with an other component version that is already active.
Followin components is causing the conflict:
Component 1:
C:\Windows\WinSxS\manifests\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.762_none_0c178a139ee2a7ed.manifest.
Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.42_none_d6c3e7af9bae13a2.manifest.

Can you help me solve this please.

Best Regards,

Klas

[sjj1805]

I think the best bet is to uninstall and then re-install VideoStudio to see if this clears the problem.

[KlasN]

Hello SiteAdmin,

I have uninstalled and reinstalled VideoStudio 12 Pro three times. Same problem
I have uninstalled .NET framework 3,5 SP1 and tried older versions of .NET framework.
I have unistalled/installed Microsoft Visual C++ 2005 Redistributable.
I have unistalled/installed Microsoft Visual C++ 2008 Redistributable -x86 9.0.30729.17.

It have not solved the problem.

Klas

[mitchell65]

Have you part of an older version of any Ulead or Corel video software product on your PC. Also have you a Registry Cleanup program. Just a thought!

[sjj1805]

At this stage all I can do is describe what the SxS Manifest is.
Most programs are a pile of Lego Bricks. You grab the Lego bricks you need to build the complete program. These Lego Bricks are smaller programs that perform a particular task.

As an example you want to clear the screen. So you write a routine in your favourite computer language that will clear the screen.
This is quite a common task used by lots of different programs and so instead of writing it over and over again every time you create a new program, you write a stand alone routine (Lego brick) that any program that needs to clear the screen can simply run that small stand alone "clear the screen" program.

Where these small programs (Lego Bricks) are used extensively by lots and lots of programs running on your computer, it was considered a waste of hard drive space to place a copy of that "Lego brick" in every program installation folder.

Lets say you have the following programs on your computer:
VideoStudio
Microsoft Word
Windows Notepad

All 3 programs want to use the "Clear screen" program.
Instead of keeping 3 copies of your "Lego brick" Clear the screen program, you keep one in a common files directory - normally one of the following
C:\Program Files\Common Files
C:\WINDOWS\system32

Sometimes a program may require a specific version of one of those "Lego Bricks" - every now and then someone will modify one of those little programs. Where this situation occurs a specific version is placed in the SxS folder.

These things I have termed Lego Bricks for ease of understanding are normally DLL files (Dynamic Link Libraries). If you can work out which DLL file is giving you this problem then the work round would be to copy the specific DLL file into the VideoStudio installation directory.

[KlasN]

Hmm...

I'm quite sure it's these dll-files.

mfc80.dll
mfc80u.dll
mfcm80.dll
mfcm80u.dll

There are two versions available.
8.0.50727.42
8.0.50727.762

I copied dll's (ver 8.0.50727.42) to the application folder (same folder as vstudio.exe is in), restarted the computer, and tried to start the application.
But I got the same problem.

Do I have to register these Dll's when I have copied them to the application folder?

[Ken Berry]

Those dll files relate to the (confusing in the circumstances) Microsoft Visual Studio (unrelated, of course to Corel Video Studio!). And it seems to be a known problem: see http://support.microsoft.com/default.aspx/kb/961894 . However, you might need to do further research since that knowledge base article, while referring to those dll's, refer to different versions of them than the ones you have. Thus the 'hot fix' may not necessarily work.

[KlasN]

Thank you Ken Berry.

You led me right to the solution of the problem. http://support.microsoft.com/default.aspx/kb/961894

[Ken Berry]

Glad it worked!

[sjj1805]

Glad it worked!

Likewise, glad your back in business.