MSASCui cannot access msvcp80.dll.msvcr80.dll-Can Defender work?

[Guest]

Symantec one button checkup and win doctor produce the following messages:
"C:\Program Files\Windows Defender\MSASCui.exe" cannot access a necessary
file,
"msvcp80.dll."
"C:\Program Files\Windows Defender\MSASCui.exe" cannot access a necessary
file,
"msvcr80.dll."

Windows Defender gets updates and looks like it is running correctly.
Does the fact that Defender cannot find these dlls cause Defender to NOT
work correctly?

There is no manifest file in the Windows Defender directory.
The dlls are located in C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT...

Is there anything I can do to fix this problem?

Windows XP Professional SP2 is fully updated.
Windows Defender Version: 1.1.1347.0
Engine Version: 1.1.1372.0
Definition Version: 1.14.1408.8

Thank you,
B

 

[Guest]

Hi B,
I noted the same problem, both in One Button CheckUp and WinDoctor. I have
16 of those entries related to .Net Framework 2.0 and SQL 2005 express.
It was reviewed on another website, and felt to be a problem with Symantec's
code, but felt it probably won't be corrected since it has to do with WD, now
a competor. MSvcp80.dll is there where it should be.
The best thing to do when you run One Button CheckUp next time, in the
Program Integrety Section, mark them to be ignored, and it will clear up the
entries in both OBC & WinDoctor when you run them. Problem solved.

Then, if Symantec ever does correct the code, you can just remove them from
the ignored section. One of the MVP's did write a manafest file to be placed
in the OBC directory, but you would have to have a separate one for the
WinDoctor directory. Probably not the safest way to solve the issue, since
there is a solution already built into SystemWorks.
Hope that helps -

 

[Guest]

Hello B,

Delete c:\program files\windows defender\MSASCui.exe.manifest

I hope this post is helpful.

Please , rate the pºsts.

Еиçеl

 

[Bill Sanderson MVP]

I believe that Windows Defender is working correctly for you. I have no
idea where Symantec is getting the info that leads to this display. I'd
thought perhaps it was from the manifest, but if that's already gone.....

I agree with John Van Kirk.

 

[Guest]

Thank you.

I now feel confident that Windows Defender is doing its job.
I will take John Van Kirk's advice and ignore the messages about the dlls in
OBC and WinDoctor.
I also periodically get a message relating to the dotnetinstaller in OBC and
WinDoctor.

B.

 

[Bill Sanderson MVP]

Sometimes issues like this take a while for the vendors to resolve. I would
expect them to be fixed, but perhaps not until after Windows Defender is
released--i.e. the beta period is over. It costs Symantec real $ to make
changes to their software, and they are probably loath to do that before
Microsoft's product is final, and not changing.


--