Defender corruption

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

Guest

When Vista release version was first installed, Defender was shown as ON in
C.P.|SECURITY|MALWARE. It would auto-scan as it should.

Several days later the security dialog indicated "Defender is not running" -
with a TURN ON button. When that was clicked, a search for the latest
definition file would be made. Once done, Defender was still not running
though services confirmed that it was.

UAC was off long before the time Defender stopped auto-updating. It can be
updated and run manually. Any thoughts as to what caused this corruption?
How would it be overcome?
 
The only thought I have is that you need to tell us if your also running
Microsoft's Windows Live OneCare, which by default disables a standalone
Defender as the anti-spyware component of WLOC eliminates the need for a
separate Windows Defender. Once you've eliminated that possibility,
perhaps there will be some additional ideas.
 
Dave M said:
The only thought I have is that you need to tell us if your also running
Microsoft's Windows Live OneCare, which by default disables a standalone
Defender as the anti-spyware component of WLOC eliminates the need for a
separate Windows Defender.
Click to expand...

Nope, no LOC.
I restored an old image, when Defender was shown as ON...and it scanned at
the appointed time yesterday - but not today. Defender IS running, it's
still ON, but it appears that auto-scan is still not reliable. I truly do
not care that much about Defender, but am annoyed when processes inexplicably
go awry.
 
....I understand that annoyance, thanks for letting us know you're not
running WLOC. We recently had a suggestion from dean-dean to repair
Vista's version of Defender which is an integral part of Vista using the
sfc /scannow integrity check command, since the online download is for the
XP and Windows Server 2003 versions. We never heard back from the OP as to
if it was successful or not, but as dean-dean says it shouldn't hurt to
try, here's his quote if you'd like to give that a run:

It might be worthwhile to do this:

While holding down the Windows key on your keyboard, push the "R" key. In
the Run box type

sfc /scannow

Click on OK. The System File Checker checks all the current system files
and can restore the cached approved copies. For more information regarding
the System File Checker with Vista, see:

http://vistasupport.mvps.org/system_file_checker.htm
 
Dave M said:
....I understand that annoyance, thanks for letting us know you're not
running WLOC. We recently had a suggestion from dean-dean to repair
Vista's version of Defender which is an integral part of Vista using the
sfc /scannow integrity check command, since the online download is for the
XP and Windows Server 2003 versions. We never heard back from the OP as to
if it was successful or not, but as dean-dean says it shouldn't hurt to
try, here's his quote if you'd like to give that a run:

It might be worthwhile to do this:

While holding down the Windows key on your keyboard, push the "R" key. In
the Run box type

sfc /scannow

Click on OK. The System File Checker checks all the current system files
and can restore the cached approved copies. For more information regarding
the System File Checker with Vista, see:

http://vistasupport.mvps.org/system_file_checker.htm
Click to expand...

No problems there, and thanks for the tip. Defender has auto-updated for
the past two days, so it appears to be back on track.

Why it broke remains a puzzlement. UAC was disabled long before that
occurred - back in RC1 days. Now it is enabled. Annoying as UAC is to some
users, it apparently is necessary for compatibility as well as security
concerns...

http://www.dcr.net/~w-clayton/Vista/Vista_Information.htm
 
John Barnett's site is quite correct about the reference to the SFC /scannow
command in Windows Vista it does resolve issues. This post should receive 5
stars for validity and accuracy. I am going to try it on my laptop which has
been experiencing error code 0x80240029, even after the update method used by
Robert531 worked Defender still did not accept the new cahnges even after a
restart. I will return with news on how this fix attempt works/or what ever!

Fireplug1
 
fireplug1;
I performed the "SFC /scannow" command and found no integrity violations in
Vista, still Defender is corrupt, and no way to fix YET, have opted out of
auto updates and cleared both other check blocks, and found the downloads
every one spoke of, they were successfully installed according to the
installed list, but defender doesn't recognize the change,and still error
code 0x80240029 even after restart and repeating steps two times. Nothing
worked for me to fix the Defender, has anyone else come up with similar
conclusion? Please respond and I will check to receive responses. Thanks
Robert531, andJohn Barnett for your imput, but my problem still exists. error
code 0x80240029 lives on, unfortunately!!!
 
Thanks for the update fireplug1. It's indeed unfortunate that this isn't a
fix for the Vista 0x80240029, perhaps Bill can pass this along to his Ms
contacts, although I suspect that they're already painfully aware of the
problem.
 
Back
Top