Applying Update for Windows Defender

[Guest]

Something is "wacked" in applying updates. Try this until updates are fixed.
I removed Windows Defender, cleaned the registery with Registry Mechanic,
rebooted, download todays (2/16) version of Windows Defender and am now up
to date with signatures. Let's sSee how the next update applies!

 

[Bill Sanderson]

I hope folks will do some reading and try to keep an open mind. The various
incantations, workarounds and genuine fixes that helped with beta1 are
likely to be completely irrelevant in beta2, which is completely different
code, written with different tools.

So--you did a remove and a reinstall, and now update works. This KB is
relevant in that situation, but it doesn't explain what was wrong that
prompted the remove, of course:
http://support.microsoft.com/default.aspx?scid=kb;en-us;915105

 

[Guest]

Bill, thankyou for bringing the KB to my attention. I was unable to install a
signature update from 1.13.1272.4 to 1.13.1276.3 using Windows Update site or
by clicking on the Windows Update notfication icon in my Task Bar.

I used the information in the link to successfully remove the old signature
and then the new signature installed without any problems.

Thankyou for your time in posting this link.

Julien

:
This KB is

 

[Bill Sanderson]

This one is now posted in the Known Issues page at the web site. Along with
several other top issues

http://www.microsoft.com/athome/security/spyware/software/about/releasenotes.mspx
--

 

[Guest]

Hi Bill...just checking to see if you are about to run this past you, or
anyone else for that matter?

I've just had a repeat of the update issue...this time I got the 'task bar
update icon' saying a sig update was available. Clicking on it instigated the
download and install of sig# 1.13.1276.16 - which failed to install -
attempting via Windows Update also had same result.

The Event Viewer Application logs don't give much away only saying
'configuration failed' and 'no additional info available'.

I am wondering why, [when as you will know from further up this thread I did
infact successfully install sig#1.13.1276.3, which was from the first 'icon
alert' that a sig. update was available] the seemingly backwards issueing of
sig # ?

I know I can try and use the 'delete sig fix' again...but reinstalling a
lower numbered sig, hmmm{{{{looks puzzled}}}

Any clues or observations yourself?

 

[Bill Sanderson]

And I also know you've read Mike Treit's explanation. Excellent job in
finding the fix for the cycling sig update issue so quickly, and now you
understand the numbering system!

--

Hi Bill...just checking to see if you are about to run this past you, or
anyone else for that matter?

I've just had a repeat of the update issue...this time I got the 'task bar
update icon' saying a sig update was available. Clicking on it instigated
the
download and install of sig# 1.13.1276.16 - which failed to install -
attempting via Windows Update also had same result.

The Event Viewer Application logs don't give much away only saying
'configuration failed' and 'no additional info available'.

I am wondering why, [when as you will know from further up this thread I
did
infact successfully install sig#1.13.1276.3, which was from the first
'icon
alert' that a sig. update was available] the seemingly backwards issueing
of
sig # ?

I know I can try and use the 'delete sig fix' again...but reinstalling a
lower numbered sig, hmmm{{{{looks puzzled}}}

Any clues or observations yourself?

 

[Guest]

Hi Bill

Thanks for the compliment...I have started posting the 'fix' around various
computer forums....but really you must take credit also for posting the
'fix' for the reinstall of WD [beta2] in the firat place ; )

One thing that's caught me out is the fact that after successfully
installing a new sig update via WD[Beta2] 'update' window [the one under Help
Options] the signature update # isn't updated itself until WD[beta2] is
closed and restarted. I found myself doing a double take thinking the 'fix'
hadn't worked.

See you around the boards as and when...

And I also know you've read Mike Treit's explanation. Excellent job in
finding the fix for the cycling sig update issue so quickly, and now you
understand the numbering system!

--

Hi Bill...just checking to see if you are about to run this past you, or
anyone else for that matter?

I've just had a repeat of the update issue...this time I got the 'task bar
update icon' saying a sig update was available. Clicking on it instigated
the
download and install of sig# 1.13.1276.16 - which failed to install -
attempting via Windows Update also had same result.

The Event Viewer Application logs don't give much away only saying
'configuration failed' and 'no additional info available'.

I am wondering why, [when as you will know from further up this thread I
did
infact successfully install sig#1.13.1276.3, which was from the first
'icon
alert' that a sig. update was available] the seemingly backwards issueing
of
sig # ?

I know I can try and use the 'delete sig fix' again...but reinstalling a
lower numbered sig, hmmm{{{{looks puzzled}}}

Any clues or observations yourself?

:
This KB is
relevant in that situation, but it doesn't explain what was wrong that
prompted the remove, of course:
http://support.microsoft.com/default.aspx?scid=kb;en-us;915105

 

[Bill Sanderson]

One thing that's caught me out is the fact that after successfully
installing a new sig update via WD[Beta2] 'update' window [the one under
Help
Options] the signature update # isn't updated itself until WD[beta2] is
closed and restarted. I found myself doing a double take thinking the
'fix'
hadn't worked.

Thanks--hadn't spotted that yet. There are three different apps
involved---mpcmdrun is what is doing the updating, having been told to do so
by msascui.exe, which is what you run to see the UI. The signature are
actually used by msmpeng.exe, the Windows Defender service--so when the
msascui.exe gets updated to see the new definition version is a
question--closing and reopening is one, I hope there's some poll or other
trigger as well.