New Signatures

  • Thread starter Thread starter Tom Emmelot
  • Start date Start date
T

Tom Emmelot

Hi Bill,

I read about new signatures, but my autoupdate was a hour ago, so no new
sign. for me, but as you know I make a change in the registry, that WD
looks for update at startup! So i did a reboot and yes when the reboot
was final, I look to WD, and yes there where the new signatures! First
time without a problem! :) ;)

Regards >*< TOM >*<
 
Reading about the new definitions, I tried a couple of times via help,
about, check for updates. I got a balloon "checking" and I got another
balloon "change to advpack" but I never got a completion balloon.

Looking at WindowsUpdate history--I see one successful update via autoupdate
and 2 more via "other"--but the main UI of the program still shows the old
definitions.

MicrosoftUpdate has just offered it, after an express scan--lets see if that
works.....OK--there's another change to advpack.dll notice from Windows
Defender. MicrosoftUpdate claims success..and, indeed, when I run Windows
Defender--the def version now reads correctly.

Wierd. Off to forward logs...
 
my update went fine , like always , i have windows update on "ask before
downloading and installing updates " and the balloon always tells me there is
an update and then i do a windows update manually to see te updates , and
that went very good , like always.

But only downside the new engine 1440.0 does not solve the symantec log
problem...
 
Hi Engel,

The point was that I set WD to look for Updates at startup and that give
me both sig. and def. after reboot, so that worked for me this time.
The other times, only ones i got the update automatic. The PC at my work
never had any problems with updates or else. Is XP pro, here XP Home.
The strange thing is that the setting is there in the registry, but not
in the program!
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Defender\Signature
Updates\UpdateOnStartUp
Make dword 1, default = 0

Regards >*< TOM >*<


Engel schreef:
 
I believe this setting is used internally by the program--perhaps in
situations where definitions are badly out of date, or perhaps just on first
run--not sure--somebody should do a clean install with REGMON running. I'm
also somewhat suspicious that this may be at the root of the occasional
message here about Windows Defender using excessive CPU at startup, although
now that I think of it, this could also be cleanup work after a scan and
removal--but nobody's mentioned that possibility, that I can recall.

--
 
Back
Top