Microsoft has been trying for a long time to try and resolve DLL hell problems. DLL hell is caused when various DLL files on your Windows system generate system errors, primarily due to conflicts, version problems and file damage. MSVCR80.dll is a Microsoft C runtime library. Although there are many other libraries on your Windows PC, MSVCR80.dll is the default for all DLLs that were compiled using the Visual Studio 2005 compiler and linker.
Version mismatches and other errors in the C runtime library commonly cause application failure on Microsoft systems. To counter this problem, Microsoft has enforced the use of manifest in applications. Manifest helps in identifying the exact version of the dependent file required by the application. This has been done by enabling side-by-side existence of multiple versions of the same file without any conflicts. These shared DLL files are copied to the WinSxS folder (side-by-side cache) instead of the default C:\System32 folder.
However, this solution has its own complications. For instance, not all Windows operating systems support side-by side execution. And on those that do support it, the complex installation process opens up many options for errors.
If an application is unable to reach the dll in its side-by-side execution folder, you may receive an error message similar to the one given below:
This application has failed to start because MSVCR80.dll was not found. Re-installing the application might fix the problem.
This error occurs when an application that needs to use a DLL file from a side-by-side assembly does not comprise an application manifest file-application_name.exe.manifest or application_name.exe-in the WinSxS folder specifying the assembly it uses.
Note: The manifest file is an XML file comprising the full name of the application along with its extension.
If you look for a solution to this error, you may be asked to download the latest version of the MSVCR80.dll file from the Web and copy it to the C:\System32 folder. However, this is not the correct solution. The reason why is because the MSVCR80.dll is already there on your PC. It’s just not in the system32 folder. Instead, it is in the WinSxS side-by-side execution folder. You may be able to resolve your current error by copying the DLL file to system32, but it will only generate other errors on the system.
The MSVCR80.dll file is not distributed centrally by Microsoft. However, it gets installed on your system by the application that requires to use it. And if you have downloaded and installed .NET Framework 2.0 on your PC, then you probably already have the file on your PC.
So how do you resolve the missing MSVCR80.dll error? First check if the manifest for the application is there in the WinSxS folder. If it is there, then chances are that the manifest file is corrupt or damaged. You may try to resolve the error by deleting this file and reinstalling your application.
However, if the file does not exist, then to permanently resolve the error you may have to create a manifest for the application that is causing the error and place it in the correct location. However, creating a manifest requires you to have programming experience. If you do not have that, then it is best that you report the error to the application manufacturer and ask them to provide you with a solution.
