• Side-by-Side Configuration Incorrect post-Upgrad

    Home » Forums » AskWoody support » Windows » Windows 7 » Questions: Windows 7 » Side-by-Side Configuration Incorrect post-Upgrad

    Author
    Topic
    #468933

    Bottom line on top: I suspect a problem with a manifest added by Win7 Ultimate during the upgrade. I consider myself an experienced power user and did a lot of research myself. I think that I’ve identified the error, but need assistance from a knowledgeable software engineer to fix the problem created by the upgrade process. Hopefully, someone here will be generous with their time and help. I hope to return the favor someday. Thank you.

    Immediately after upgrading from Vista Ultimate to Win7 Ultimate, I receive the following error message when trying to run various applications, such as Quicken, Adobe Acrobat, SnagIt, and ShadowProduct among other applications.

    ——————-
    C:Program FilesQuickenqw.exe
    The application has failed to start because the side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more details.
    ——————-

    These applications ran fine before the upgrade. Some other applications run fine after the upgrade.

    The critical error in the event log for all applications that fail to start is always the same. The only difference is the path and filename of the application that failed to start. Here is an example:
    ——————-
    Activation context generation failed for “C:Program FilesQuickenqw.exe”. Dependent Assembly Microsoft.VC80.MFC,processorArchitecture=”x86″,publicKeyToken=”1fc8b3b9a1e18e3b”,type=”win32″,version=”8.0.50727.762″ could not be found. Please use sxstrace.exe for detailed diagnosis.

    ——————-

    Here is the result of the sxstrace.txt log (also included as an attachment)

    ——————-
    =================
    Begin Activation Context Generation.
    Input Parameter:
    Flags = 0
    ProcessorArchitecture = x86
    CultureFallBacks = en-US;en
    ManifestPath = C:Program FilesQuickenqw.exe
    AssemblyDirectory = C:Program FilesQuicken
    Application Config File =
    —————–
    INFO: Parsing Manifest File C:Program FilesQuickenqw.exe.
    INFO: Manifest Definition Identity is (null).
    INFO: Reference: Microsoft.VC80.CRT,processorArchitecture=”x86″,publicKeyToken=”1fc8b3b9a1e18e3b”,type=”win32″,version=”8.0.50727.762″
    INFO: Reference: Microsoft.VC80.MFC,processorArchitecture=”x86″,publicKeyToken=”1fc8b3b9a1e18e3b”,type=”win32″,version=”8.0.50727.762″
    INFO: Resolving reference Microsoft.VC80.CRT,processorArchitecture=”x86″,publicKeyToken=”1fc8b3b9a1e18e3b”,type=”win32″,version=”8.0.50727.762″.
    INFO: Resolving reference for ProcessorArchitecture x86.
    INFO: Resolving reference for culture Neutral.
    INFO: Applying Binding Policy.
    INFO: Find publisher policy at C:WindowsWinSxSmanifestsx86_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4927_none_516ad11f0f4bdafe.manifest
    INFO: Publisher Policy redirected assembly version.
    INFO: Post policy assembly identity is Microsoft.VC80.CRT,processorArchitecture=”x86″,publicKeyToken=”1fc8b3b9a1e18e3b”,type=”win32″,version=”8.0.50727.4927″.
    INFO: Begin assembly probing.
    INFO: Attempt to probe manifest at C:WindowsWinSxSmanifestsx86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4927_none_d08a205e442db5b5.manifest.
    INFO: Manifest found at C:WindowsWinSxSmanifestsx86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4927_none_d08a205e442db5b5.manifest.
    INFO: End assembly probing.
    INFO: Resolving reference Microsoft.VC80.CRT.mui,language=”*”,processorArchitecture=”x86″,publicKeyToken=”1fc8b3b9a1e18e3b”,type=”win32″,version=”8.0.50727.4927″.
    INFO: Resolving reference for ProcessorArchitecture x86.
    INFO: Resolving reference for culture en-US.
    INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
    INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at C:WindowsassemblyGAC_32Microsoft.VC80.CRT.mui8.0.50727.4927_en-US_1fc8b3b9a1e18e3bMicrosoft.VC80.CRT.mui.DLL.
    INFO: Did not find manifest for culture en-US.
    INFO: End assembly probing.
    INFO: Resolving reference for culture en.
    INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
    INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at C:WindowsassemblyGAC_32Microsoft.VC80.CRT.mui8.0.50727.4927_en_1fc8b3b9a1e18e3bMicrosoft.VC80.CRT.mui.DLL.
    INFO: Did not find manifest for culture en.
    INFO: End assembly probing.
    INFO: Resolving reference Microsoft.VC80.MFC,processorArchitecture=”x86″,publicKeyToken=”1fc8b3b9a1e18e3b”,type=”win32″,version=”8.0.50727.762″.
    INFO: Resolving reference for ProcessorArchitecture x86.
    INFO: Resolving reference for culture Neutral.
    INFO: Applying Binding Policy.
    INFO: Find publisher policy at C:WindowsWinSxSmanifestsx86_policy.8.0.microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.4053_none_49ef489714173a89.manifest
    INFO: Publisher Policy redirected assembly version.
    INFO: Post policy assembly identity is Microsoft.VC80.MFC,processorArchitecture=”x86″,publicKeyToken=”1fc8b3b9a1e18e3b”,type=”win32″,version=”8.0.50727.4053″.
    INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at C:WindowsassemblyGAC_32Microsoft.VC80.MFC8.0.50727.4053__1fc8b3b9a1e18e3bMicrosoft.VC80.MFC.DLL.
    INFO: Attempt to probe manifest at C:Program FilesQuickenMicrosoft.VC80.MFC.DLL.
    INFO: Attempt to probe manifest at C:Program FilesQuickenMicrosoft.VC80.MFC.MANIFEST.
    INFO: Attempt to probe manifest at C:Program FilesQuickenMicrosoft.VC80.MFCMicrosoft.VC80.MFC.DLL.
    INFO: Attempt to probe manifest at C:Program FilesQuickenMicrosoft.VC80.MFCMicrosoft.VC80.MFC.MANIFEST.
    INFO: Did not find manifest for culture Neutral.
    INFO: End assembly probing.
    ERROR: Cannot resolve reference Microsoft.VC80.MFC,processorArchitecture=”x86″,publicKeyToken=”1fc8b3b9a1e18e3b”,type=”win32″,version=”8.0.50727.762″.
    ERROR: Activation Context generation failed.
    End Activation Context Generation.

    —————————————–

    I know that manifests were designed at least in part to resolve DLL hell. But, when they don’t work correctly, I don’t know how to fix. Please help. Thanks.

    Viewing 3 reply threads
    Author
    Replies
    • #1224048

      Did you do an In Place Upgrade or Clean (Custom) Install over Vista? Also 32 Bit or 64 Bit (Appears 32 Bit from your post)? Some very strange problems have occured with In Place Upgrades. If this is your case, the Clean (Custon) Install option may have been a better choice. Yes it does require a reinstall of apps, but gives a cleaner install in my opinion. Sorry I can not tell you how to fix this. It appears this is a problem with incorrect or corrupt dll system files which could be the result of Upgrade versus Clean install.

      Run sfc /scannow from an elevated command prompt, might find the problem. Here is explanation from Microsoft.

      A reinstall using the Clean (Custom) install may be in order, sorry.

    • #1225275

      You might try a reinstall of any applications that no longer function as they did before the upgrade.

      Always create a fresh drive image before making system changes/Windows updates; you may need to start over!
      We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.
      We were all once "Average Users".

    • #1227237

      I found the same issue today on a new Win7 64 laptop being setup. One of the programs installed was Alwil Software Avast5. Called it up this morning to set it up ans received the same message regarding side-by-side configuration.

      I accept the suggestion by bbearren as the way to best deal with this problem BUT.

      Avast5 is not showing in the programs so is not available to be removed and I cannot find a way to remove it. Should I attempt to install over it again? I would rather remove it first but don’t know how to do it. HELP please and thanks a lot.
      ……….
      Ray/FL
      Polk County

    • #1227259

      Searched for and found installers and fixed the problem. Removed the troubled program and reinstalled. Everything is fine now and thanks very much. I used Revo and it is good.
      ………
      Ray/FL

    Viewing 3 reply threads
    Reply To: Side-by-Side Configuration Incorrect post-Upgrad

    You can use BBCodes to format your content.
    Your account can't use all available BBCodes, they will be stripped before saving.

    Your information: