cannot install/run WD

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi all,

I posted below about the prog locking up and I had to run the installer
cleanup and then tried to reinstall. It seemed to install okay, but did not
place an icon on the desktop. The prog is listed under START>PROGRAMS, but
when I try to start I get an error msg 'failed to start because could not
find MSVCR80.dll" .

Any suggestions to correct this?

Thanks,

John
 
I mentioned my Defender installation/update issues a couple of days back,
then stumbled across this fix by hacking around on my own. I suspect this to
be a malformed XML stylesheet. Is that a fair assessment?

Anyway, once I had managed to install Defender (and after being asked to
remove .NET 2.0 by MS support), OneCare is now behaving badly. .NET 2.0 will
not re-install now. As near as I can tell, however, all modules of OneCare
load, except that it is impossible to bring up the user interface. No error
messages, but no interface either.

Defender is now functioning swimmingly, but apparently the "cure" is worse
than the disease. Any clues on that one?
 
I don't know the detail about how to describe what's wrong with
Defender--you could well be right.

With OneCare, the recipe for fixing things seems to be to remove and
reinstall. In certain resistant cases, their support folks have a
particular removal routine which works when some others don't.

I think that I have this in a message from another user--if you want to
shoot me an email, I can pass it on--not sure whether I should post it live.
Remove everything past COM in the posting address.



--
 
Bill may i ask you a question, why is it when I install WD I do not get the
file c:\program files\windows defender\MSASCui.exe.manifest, I see deleting
this file helps others to get the program to work but I do not have that
file, Thanks.
 
I can't answer with certainty, but I believe that not seeing the .manifest
file is good--having it appear, and needing to remove it to get proper
functionality was a bug, which I think is long since fixed.

Are you haveing trouble with Defender? What version of Windows?

--
 
Back
Top