"The application was unable to start correctly (0xc000007b). Click OK to close the application."
I get a title error on a VPS running Windows Server 2008 R2 Enterprise SP1 when trying to open Visual Studio 2010. Everything worked fine at the beginning, even after installing SQL Server 2012 and VS 2013.
In an attempt to resolve this issue, I found others who had this problem, which said that the 32-bit version of the DLLs msvcp100, msvcp100d, msvcr100, msvcr100d and msvcr100_clr0400 in the SysWOW64 folder was somehow overwritten by the 64-bit version. So I downloaded the 32 bit version and replaced them with no luck. I also deleted the versions in the system32 folder. It didn't work, so I put the originals back.
I also did a full cleanup of uninstalling Visual Studio 2010, then reinstalling VS 2010 Shell Integrated; Visual Studio still won't start and gives the same error.
Can anyone help me solve this problem? If it is a DLL issue, does anyone know of a tool to help me narrow down what is causing the DLL (s) issues?
Any help would be greatly appreciated. Thank!!!
source to share
Using the Dependency Walker tool and finding a post that provides a little information on how to use the tool, I figured out that I had the 64-bit version of ATL100.DLL instead of the 32-bit version. This file went missing earlier and I unknowingly downloaded it and replaced it with the 64-bit version.
source to share
I went through this issue in detail and did not find anything convincing. One message from a Microsoft technician states the following:
"From your error 0xc000007b I found that the error means the following:" STATUS_INVALID_IMAGE_FORMAT "".
The error message probably refers to the image file - most likely one of the MS VS SDK DLLs. The exact filename should be in the Windows Event Logs - Application section. If not, they are probably in the log file (in the% temp% area).
Assuming you can't find the filename: Have you tried repairing all VSK versions of VS 2010? If a file has been updated (via MS installer) since MS VS was installed, it will not be rolled back through the installation - even if it is invalid. It will not be removed if you uninstall it because another application has installed / updated it. You need to force this with a repair (under Programs and Features).
Update: MS Repair Tool for .NET Components - Not sure if these are just .NET libraries or if it is a VC ++ / VC # / etc scan. I am still looking for a similar tool for other MS components.
ALSO: If that does not help, try the following:
-Fix the error that occurred and leave a running process (VS 2010) with its error message
-Turn Process Explorer (a utility from Microsoft - sysinternals.com) and select this process
-Enable DLL view for bottom pane
-Look through the DLL and there should be one there with an odd date and possibly an odd location (for example, in the VS 2010 folder, not in System32.)
-Close VS 2010 (and its error message)
-Run any DLL that doesn't live under system32 / syswow64 to a temporary location (don't forget where you got them!)
-Write again VS 2010
LATEST CONTENT:
Try this for better logging - start VS2010 like this:
devenv.exe / Log
The log goes here:
% APPDATA% \ Roaming \ Microsoft \ VisualStudio \\ ActivityLog.xml
More devenv.exe switches to [original web page] .
source to share
For me, I have the same problem. The issue was related to 32/64-bit mismatches of various system DLLs required by Visual Studio. Somehow the dlls it needs was replaced with 64bit versions that it couldn't load. I uninstalled x64 vC ++ 2013 redistribute and install x86 and it started working.
source to share