This application has failed to start because MSVCR80D.dill was not found

The file is there in c:\windows\winsxs folder.
This happens when I try a to create a simple project to test system and press f5 to bebug it.
The file will create with release set and create the exe but will not debug
I would appreciate any help. I have removed all re-installed all and no matter What I do comes up the same
Thanks
Operating system xp pro
[375 byte] By [whw61] at [2008-2-4]
# 1
I have the same problem with VC++ 20005 EE as you,
I serached the filesystem for msvcr80d.dll,but I had no luck.
recordus at 2007-9-8 > top of Msdn Tech,Visual Studio Express Editions,Visual C++ 2005 Express Edition...
# 2

The file should be in the SxS directory. Check out http://msdn2.microsoft.com/en-us/library/ms235624.aspx for more details.

Thanks,
Ayman Shoukry
VC++ Team

AymanShoukry at 2007-9-8 > top of Msdn Tech,Visual Studio Express Editions,Visual C++ 2005 Express Edition...
# 3
The file is there as I said but it still comes up with the same error when f5 is pressed to debug and run for some reason it does not find it
whw61 at 2007-9-8 > top of Msdn Tech,Visual Studio Express Editions,Visual C++ 2005 Express Edition...
# 4
Could you post what the manifest information contain?

Thanks,
Ayman Shoukry
VC++ Team

AymanShoukry at 2007-9-8 > top of Msdn Tech,Visual Studio Express Editions,Visual C++ 2005 Express Edition...
# 5
no sorry I have binned c++ and gone for the vb as I have more experiance with vb as a user of vb4 pro the vb 2005 works fine there are some database errors to get round with the copy all but at least it works for de-bug etc. might come back to it one day. Thanks for your trouble
whw61 at 2007-9-8 > top of Msdn Tech,Visual Studio Express Editions,Visual C++ 2005 Express Edition...
# 6
I really face such problem! I have installed the VC express edition
last night, but when I debug a simple application, it still showed the
information which is the same as showed above.
I can find the MSVCR80D.DLL in the Win32 diretion. But I still can
not debug my applications.
So how can we do to solve this problem?

Thanks in advance!

Seaston at 2007-9-8 > top of Msdn Tech,Visual Studio Express Editions,Visual C++ 2005 Express Edition...
# 7

It should pick the binraries from the windows\winsxs. Could you post the manifest you are seeing?

http://msdn2.microsoft.com/en-us/library/ms235624.aspx should have more details.

Thanks,

Ayman Shoukry

VC++ TEam
AymanShoukry at 2007-9-8 > top of Msdn Tech,Visual Studio Express Editions,Visual C++ 2005 Express Edition...
# 8

I too have this problem.

The 'release' version works OK but the 'Debug' version produces the 'MSVCR80D.dll not found' message.

Below I have pasted-in the contents of 'x86_Microsoft.VC80.DebugfCRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_f75eb16c.manifest'

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<noInheritable></noInheritable>
<assemblyIdentity type="win32" name="Microsoft.VC80.DebugCRT" version="8.0.50727.42" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>
<file name="msvcr80d.dll" hash="f64e05abe2a26c9aac1be78003b232c83ac24acd" hashalg="SHA1"><asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity"></dsig:Transform></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>xc3tSVeNwebiXgqFqMW9UJVb+48=</dsig:DigestValue></asmv2:hash></file>
<file name="msvcp80d.dll" hash="0b585ae65b4e7a2764e99e088da2fce64c631086" hashalg="SHA1"><asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity"></dsig:Transform></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>SV3cC53+5fUREmKVK+EbIImO+dU=</dsig:DigestValue></asmv2:hash></file>
<file name="msvcm80d.dll" hash="e69bf1c82192ac71e350b84365aba2603c0b50e3" hashalg="SHA1"><asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity"></dsig:Transform></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>N+mu96dg5d1fPArZvRHbb0ULiCQ=</dsig:DigestValue></asmv2:hash></file>
</assembly>

And below here is the contents of 'x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd.manifest'

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<noInheritable></noInheritable>
<assemblyIdentity type="win32" name="Microsoft.VC80.CRT" version="8.0.50727.42" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>
<file name="msvcr80.dll" hash="2a0d797a8c5eac76e54e98db9682e0938c614b45" hashalg="SHA1"><asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity"></dsig:Transform></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>phRUExlAeZ8BwmlD8VlO5udAnRE=</dsig:DigestValue></asmv2:hash></file>
<file name="msvcp80.dll" hash="cc4ca55fb6aa6b7bb8577ab4b649ab77e42f8f91" hashalg="SHA1"><asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity"></dsig:Transform></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>7AY1JqoUvK3u/6bYWbOagGgAFbc=</dsig:DigestValue></asmv2:hash></file>
<file name="msvcm80.dll" hash="55e8e87bbde00d1d96cc119ccd94e0c02c9a2768" hashalg="SHA1"><asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity"></dsig:Transform></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>hWq8zazTsMeKVxWFBa6bnv4hEOw=</dsig:DigestValue></asmv2:hash></file>
</assembly>

Thanks in advance for any help!

willrpberts at 2007-9-8 > top of Msdn Tech,Visual Studio Express Editions,Visual C++ 2005 Express Edition...
# 9
Ok, so the file is in the \WINDOWS\WinSxS folder. So how do I get it

included in my app so that I don't get that problem? Do I just copy it

to my app folder, or is it safe to just copy it in one of the other

libraries if I don't plan to use different version of it? What should I

do when I deploy my app? No wait, I'm not deploying it as a "debug"

version, hehe

So.... this is more like a "developer's computer" related problem,

right? So if I don't need or use different versions of that file, I can

just copy it to an easy-to-find folder, or I can include that folder

(from winsxs) to the list. But how do I do that?

AndiRaicu at 2007-9-8 > top of Msdn Tech,Visual Studio Express Editions,Visual C++ 2005 Express Edition...
# 10
I picked one of those SxS directories which contained the msvcp80d.dll and configured

bin and library paths to include the directory: NO LUCK.

I then copied the .dll into the binary and library directories and received a linking error.

I then downloaded the VC++ express to an iso file and examined the CD to find only the

msvcp80.dll. So, unless the setup program generates an 80d.dll, it is not in the install.

Is there a distribution problem here?

Len Kelly

( I hope you would assume I also got the same .dll error and that's why I have joined here.

There were other posts claiming the use of VFAT32 directories were the cause and that

settings in the vcproj properties should be changed (FAT32 workaround) this did not fix

the problem.)

LenKelly at 2007-9-8 > top of Msdn Tech,Visual Studio Express Editions,Visual C++ 2005 Express Edition...
# 11

Are using the /MDd compiler switch?

Thanks,

Ayman Shoukry

VC++ Team
AymanShoukry at 2007-9-8 > top of Msdn Tech,Visual Studio Express Editions,Visual C++ 2005 Express Edition...
# 12

I had not set the switches. I just selected the template for a console Win32 project.

After receiving your comment I looked at the code generation options and they were for a multi threaded dll. I was "developing" a simple console not too dissimilar to a Hello World program.

I set the code generation to multithreaded debug and it all works.

Thanks

I will watch generated code and project settings in the future.

Len Kelly

LenKelly at 2007-9-8 > top of Msdn Tech,Visual Studio Express Editions,Visual C++ 2005 Express Edition...
# 13
I changed my code generation too. Now t aloow me to compile without erroor, but when i'm trying to run complied prog it gives error again
Vetu at 2007-9-8 > top of Msdn Tech,Visual Studio Express Editions,Visual C++ 2005 Express Edition...
# 14
I too am having this problem but with a different twist.

I was updating a piece of software that was written with an older version of VC++ a while ago and all was well for a while. Then one day, I started getting this error messages whenever I try to run debug builds of my app. (I do not get this error running the release builds) I tried everything looking around on the net and suggestions to make this problem go away, and found one posting that suggested the only way to make this go away was to reinstall windows from scratch and then reinstall VS'05 and the mamoth SP1.

I did that and again all was well, things were working and the builds both worked.

That was until yesterday. Was working fine in the morning, then mid-day made a couple of small changes, recompiled and tried to run and get:

This application has failed to start because MSVCR80D.DLL was not found, Re-installing the application may fix this problem.

Something has clearly gone wrong with the way that VC '05 is building this app, the manifest, etc. I do NOT hve the time to reinstall windows again, that was painful. I hope that someone has a better idea of how to make this go away!

thanks

w_jackson at 2007-9-8 > top of Msdn Tech,Visual Studio Express Editions,Visual C++ 2005 Express Edition...