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!!!
"Dave M" wrote:
> ....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
>
> --
>
> Regards, Dave
>
>
> xotyl wrote:
> > "Dave M" wrote:
> >
> >> 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.
> >
> > 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.
>
>
>