vcredist_x86.dll and version 8.0.50727.4053

visual-studio-2005 msvcrt dll
Paul picture Paul · Oct 17, 2009 · Viewed 28.9k times · Source

Visual C++ 2005 I build on my system use CRT DLLs version 8.0.50727.4053. I believe it is the latest one and was automatically updated by Windows.

On user systems, this version of the DLL is not found. I have used vcredist_x86.exe in the past as a part of our installer to install runtime DLLs. It used to work.

My problem is that even the latest version of vcredist_x86.exe ( Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)) doesn't install this version of the DLL.

So which vcredist_x86.exe file do I need then ?

P.S. Would forcing my app to link to a specific version of the CRT solve the problem ? Is it a prefered method at all ?

Thanks,

Paul

UPDATE: There are other people who observe that vcredist_x86.exe ( Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)) doesn't install 8.0.50727.4053.

UPDATE2: At least one person suggests forcing using the previous version of CRT (http://tedwvc.wordpress.com/). This would however add a significant complexity to our projects.

Answer

mikets picture mikets · Mar 9, 2010

Following the advice of JesperE, I found that there exists "Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package ATL Security Update" which provides these distributables.

Related questions

How can I resolve this link error in Visual Studio (LNK2005)?

I keep having linker errors of the following form: libcmtd.dll msvmrtd.dll some element(ex: _mkdir ) already defined... and I don't know how to resolve them. Here is a complete error message: private: __thiscall type_info::type_info(class …

Read More
Unable to copy file - access to the path is denied

I am using Visual Studio 2005. After taking code from version control first, the c#.net application runs correctly. But, after doing some modifications, when I build I am getting the following error: Error 383 Unable to copy file "..\root\leaf\Bin\…

Read More
How to fix "Referenced assembly does not have a strong name" error?

I've added a weakly named assembly to my Visual Studio 2005 project (which is strongly named). I'm now getting the error: "Referenced assembly 'xxxxxxxx' does not have a strong name" Do I need to sign this third-party assembly?

Read More