msvcr80.dll Problem

msvcr80.dll Problem

• V3M4

  I am having the same problem... I even uninstalled it.. and it didnt show a problem then I reinstalled the update and it showed up as a problem in the Windoctor again... any ideas as to what is wrong with this update Im sure its a simple fix but I cant seem to get it..
  

• Thieme

  Hi Martin, can you clarify on what you mean when you say, "Are you sure that WinDoctor is right ".... I know its installed correctly, up to date and functioning properly if that's what you meant.
  

• Mandhadi

  If your application works as expected then the owenrs of WinDoctor might have more details.

  Thanks,

  Ayman Shoukry

  VC++ Team

  
  
  

• Dickin

  But if this fixes the problem WinDoctor works wrong with the side by side repsoitory!
  
  

• yuvald

  Thank you for sharing the solution to this msvcr80.dll problem.  I had the exact same problem as everyone else and when I followed your instructions, my Norton Win Doctor found no more probems, and my machine is back to normal.

  You have really helped some people with your posting, including me!

  Sincerely,

  John Allen

   

   

  
  

• shongalolo

  hello delta579!

  You are a genius!I have been trying for months to locate the solution to this problem.well weeks.Anyways the techs at verizon and msn were absolutely no help. finally an answer to a question!Thanks.it is nice to run windoctor and only get 1 error for a change that related to hpqgreg32.dll. my  c:program files \hp\digital imaging \bin\hpqgrcpy.exe can't find my hpgreg32.dlll it needs to run. This error is causing our usb mass storage device to malfunction.Thanks again, I will try this fix for the HP after trying to add it to firewall permissions first.

   

  
  
  

• Eddy-kun

  Norton WinDoctor is a Symantec product. From my expiriences with Symantec products I wouldn't trust it. Just my two cents.
  
  

• Steve1031

  This works. Thanks delta579.
  

• maniac

  I had the same problem.  I run Windows XP Media Center.  You can "search" with Windows Explorer, and you find MSVCR80.dll on your hard drive, it will not be in your SYSTEM32 folder.  "Copy" it, then open your SYSTEM32 folder and "paste" it there.  This will stop Norton from showing it as an error.  Norton searches the SYSTEM32 folder and no other, that's why you are getting the errors from WinDoctor.  This cured my errors, hope it does the same for you.
  

  [Moderator note: Subsequent discussion on this thread revealed that this is NOT the correct solution. Please keep reading onto the next page for responses from Microsoft's Martyn Lovell which give complete and correct information]

  
  

• LateNightDBA

  Are you sure that WinDoctor is right
  
  

• I Love Burger

  having the same problem, did you get a fix for this
  

• Bharathi Raja

  I haven't found a fix for this issue yet. Has anyone had any luck
  

• SpinWebs

  Thanks much everyone for the feedback. Sounds to me like its an inconsequential error that Norton will need to address in a future update to look for it in the correct dir. I read on an msn blog somewhere (sorry I cant find it again) that one should not put the dll in the system32 dir but from other posts it seems that it's possibly needed there for some progs to work right. The post was made by a supposed MS official so might be true. So far I haven't experienced any software malfunctions other than in windoc relating the the dll needing to be in system32 but I've also heard of it being neded for some. Only thing that bothers me is the new .NET executables that windoc says is looking for it there cant access it, but sounds like it's probably just Norton needing to update where it should be looking for them. I can put up with the windoctor errors as long as I know they mean nothing :-) Many thanks once again and Happy Holidays to each of you!

   

  Naolin

  
  

• Deepakgg

  Maybe WinDoctor simply has no clue about SxS assemblies ...
  
• msvcr80.dll Problem