Answers > Página Inicial dos Fóruns > Performance & Maintenance > Vista 64 nearly commits suicide: "Side-by-Side Configuration is Incorrect..." for every 32-bit Application
Fazer uma PerguntaFazer uma Pergunta
 

RespondidoVista 64 nearly commits suicide: "Side-by-Side Configuration is Incorrect..." for every 32-bit Application

  • sábado, 4 de julho de 2009 10:00Sid_311 Medalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuário
     
    Windows Vista Ultimate 64-bit SP1

    I gotta say, I never thought I'd hate something about Windows more than the Blue Screen of Death, but this problem rivals it....

    Just last night, after the 5th (literaly) BSOD* of the day, my computer restarts, I NEVER let checkdisk run when it restarts, but this time I let it... big mistake.

    Now I get the dreaded "The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail." dialog for every 32-bit application on my system while 64-bit applications work fine.

    Things that I have tried while searching for a solution:

    *sfc /scannow completes at 100% with no corrupt files found.

    *A second (5 stage) chkdsk scan revealed a corrupt file and fixed it, but the problem remained.

    *Downloaded x86 Visual C++ redistributables, both 2005 and 2008, but installers are 32-bit and will not run (SBS dialog).

    *System Restore fails with unspecified error while in normal and safe mode, and with a CRC error while using the install disc. I only have one restore point, a system checkpoint but it is before this problem started to occur.

    *Tried a similar solution found here: Side-By-Side errors on 99% of programs...I need help!   I used a previous version of the file from the "Previous Versions" in the properties dialog but the problem remains.

    Things I'm going to try but pretty sure are going to fail anyway:

    *Virus scan with up to date definitions. Going to fail because even if malware is found, the damage is done, I still need to repair the corrupt files or what not.

    *Downloaded SP2, hoping against hope that it will fix what ever Vista did to itself.

    *Download x64 Visual C++ redistributables, both 2005 and 2008. Probably won't work because, well they're 64-bit, the issue is with 32-bit.

    Other things to consider:

    *This is a multiboot desktop with XP SP3 32-bit, along with some Linux distros and even MacOS X. I never booted into any other OS, but maybe XP has something to do with it (its the only OS that shares the same SATA drive, the other OSs are on a seperate IDE drive )?

    *The only program that I installed ealier that day was TeraCopy, because I needed it to copy files to an external drive. I've had BSODs regularly before and while using this app and everything ran fine when the PC restarted, except of course when I decided to let chkdsk run, then everything went to ____. I can't uninstall it because well the uninstaller is 32-bit.

    I guess what I want to know is why this happened and how to fix it. Most other threads I've been to either are never resolved or have the good old "why don't you just reinstall Vista/ restore from a backup?" solution. Yes I have a backup, but I need to know why this happened and how to fix/prevent it; I can't have Vista castrating itself at every chkdsk (if that is indeed what happened).

    Sorry if I sound bitter, but I've been at this all day and its late/early in the morning.

    Any other suggestions or advice is greatly appreciated. Thanks in advance.


    *PS- the blue screens are due to a driver issue between Vista and an external harddrive that I have. Vista doesn't like my hard drive and my hard drive doesn't like Vista; I've learned to live with it...
    [loc]Before a question is answered, you can use this image to sign up for the answer when it arrives. The more clicks, the faster the question is answered.1 pessoa recebeu esta respostaEu também

Respostas

  • sábado, 11 de julho de 2009 7:01Sid_311 Medalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuário
     Respondido
    Well I got fed up and restored from backup. I guess that was and will always be the answer, but I think deep down inside we all knew it would be. 
    • Marcado como RespostaSid_311 sábado, 11 de julho de 2009 7:01
    •  

Todas as Respostas

  • sábado, 4 de julho de 2009 23:13Jack - Support EngineerMSFT, ModeradorMedalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuário
     

    Hello Sid_311,

    Thank you for posting.  Side by Side architecture uses a trick in a file called a 'manifest' to call a special system file instead of the regular Vista system file (a .dll). The error is saying that finding that special dll written for that application is not working somehow. (side-by-side configuration is incorrect).  Something has changed those special application files. Perhaps disk corruption, perhaps conflict with something new*.  My guess is that when chkdsk ran it discovered a problem on your HDD and corrected, the rub is this was the area where the file that your 32 bit applications wanted to use was stored.  The question then becomes what is the name of the file and how can we get another copy of this file on your system so that your 32 bit applications will be able to run.

    You were on the right track with the C++ idea because there have been some documented instances where reinstalling the redistribution installer is the fix for the side by side configuration error.  Here is a KB on that:

    http://support.microsoft.com/default.aspx/kb/948619

    I am just including this for your reference because I do not think this is the solution for you situation.  I think the key to your problem will be found in the Event Viewer.  If you read through the event logs you should be able to pinpoint the file that is being called by your 32 bit application but isn’t being found.  Once you know the file name we can work towards getting back on your system.  The easiest thing would be that is a file that you recognize and know for sure which application installed it, then you can simply reinstall that app or restore the specific file from your backup.  Rarely though are things that easy.  Let us know what you find in the event logs and if you are able to identify the file in question.

    *I’d like to give a shout out to Mark L Ferguson, MVP for information cited in this post.

    Thanks,

    Jack


    Jack
    Microsoft Answers Support Engineer
    Visit our Microsoft Answers Feedback Forum and let us know what you think.
  • domingo, 5 de julho de 2009 6:41Sid_311 Medalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuário
     
    Jack,

    Thanks for replying.

    Here is what the event viewer says when I try and run Teracopy:

    "Activation context generation failed for "C:\Users\Insidious\Desktop\teracopy.exe". Dependent Assembly Microsoft.Windows.Common-Controls,language="*",processorArchitecture="x86",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0" could not be found. Please use sxstrace.exe for detailed diagnosis."

    Every 32-bit program has the same information for its side-by-side error. Hopefully its really only one fiel I have to replace. I'm just not sure to which file this is referring to or where to find it.

    I've ran a virus scan and it found nothing of great concern, just two cookies and a bug attached to a pdf.

    By the way, would sxstrace.exe be useful? If so, how to use it?

    Thanks again , Happy Fourth.

  • quinta-feira, 9 de julho de 2009 18:13Sid_311 Medalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuário
     
    Yup....

    Still need help.

    If there is anything ELSE I could do or other information I need to post, please advise.

    Thanks.
  • sábado, 11 de julho de 2009 7:01Sid_311 Medalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuárioMedalhas de usuário
     Respondido
    Well I got fed up and restored from backup. I guess that was and will always be the answer, but I think deep down inside we all knew it would be. 
    • Marcado como RespostaSid_311 sábado, 11 de julho de 2009 7:01
    •