MSVCP100D.dll missing

Question

When I try to debug my C++ application I get the error

The program can\'t start because MSVCP100D.dll is missing from your computer. Try reinstalli

Answer 1

• Find the Visual Studio 2010 install iso file.

• Extract cab44.cab file from the ISO.

• Then extract file "F_REDIST_DLL_APPLOCAL_msvcp100d_x86" from the .cab file using 7z.

• Rename the file to msvcp100d.dll.

For x64 version. The cab file name is cab26.cab and the file name is F_REDIST_DLL_APPLOCAL_msvcp100d_x64.

For similar issue such missing msvcr*d.dll for another visual studio version. Here is the way I used to find the answer:

1. Find the Visual Studio ISO.

2. Extract all the .cab file.

3. 7z.exe t *.cab > filelist.txt

4. gvim filelist.txt

searching for the interested file name. Hope this helps.

Answer 2

This can also occur if Generate Debug info is not set to No

Configuration Properties -> Linker -> Debugging -> Generate Debug info

Answer 3

Usually you don't want MSVCP100D.dll on your system. It's for debugging purposes only. If you get this error for your release build you must make sure that you didn't accidently add a 'Debug'-tagged Project Output to your setup project.

If you really need to debug your software on a remote machine, I suggest you do the following:

Create a new Setup project called 'CRTDebug100Setup' and add the following Merge Modules (found under C:\Program Files\Common Files\Merge Modules):

• Microsoft_VC90_DebugCRT_x86.msm
• policy_9_0_Microsoft_VC90_DebugCRT_x86.msm

Build, and deploy on your computer to be debugged!

Answer 4

Followup on l33t's answer above (tried to revise it but it did not seem to appear).

Added later by gpicher 10 Jan 2012: I believe those .msm packages would be for a 9.x version of the DLL in question, not a 10.x version. I resolved a similar problem I had by making a setup project with Visual Studio 2010 installed on a 64 bit Windows installation, using the merge module Microsoft_VC100_DebugCRT_x86.msm in the folder C:\Program Files (x86)\Common Files\Merge Modules. There's a similar x64 version of the .msm if the application showing the error dialog is a 64 bit application. In this case a third party was providing me a debug build of their application in order to develop and test new plugin code against, so I couldn't change build settings, and wanted the debug functionality.

Answer 5

Reinstalling Visual Studio fixed the problem.