Windows Defender auto-update didn't

  • Thread starter Thread starter Jerry Vaughn
  • Start date Start date
J

Jerry Vaughn

Yesterday I realized that 1.14.1436.4 had not installed. Automatics
update is on but with download and notify option. No notification
occurred.

So...I manually checked for updates via WD and none were found.

Next, Windows Update and lo and behold, there is the patch which, btw,
installed just fine.

I now see the MS is pushing WD out to machines that have MS anti-spyware
on them. Seems a bit early to me to be doing since one works and the
other doesn't.

Jerry
 
Windows Defener Auto-update was pushed to my Windows 2000 machine yesterday
May 9, 2006. Since that update Microsoft Defender fails to start.
Error:

Application failed to initialize: 0x800106ba. A problem caused Windows
Defender Service to stop. To start the service, restart your computer or
search Help and Support on how to start a service manually.

I have uninstalled and reinstalled, uninstalled, downloaded again and
reinstalled and continue to get the same error message. Also have used the
supposed fix at
http://update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=34&ln=en&IsMu=False

but this does not resolve the issue either.
 
Yesterday I realized that 1.14.1436.4 had not installed. Automatics
update is on but with download and notify option. No notification
occurred.

So...I manually checked for updates via WD and none were found.

Next, Windows Update and lo and behold, there is the patch which, btw,
installed just fine.

I now see the MS is pushing WD out to machines that have MS anti-spyware
on them. Seems a bit early to me to be doing since one works and the
other doesn't.

Jerry
Click to expand...
Today with 1.14.1452.3 it was the endless loop of "updates are
waiting..", install the update, "updates are waiting..."

doing Msiexec /x {A5CC2A09-E9D3-49EC-923D-03874BBD4C2C} (which I now
have as a batch file since I ended using it so often) solved the update
loop.

Sighhhhh

Jerry
 
Someone else mentioned resolving this one by changing the credentials for
the service to run under from the original user, to a domain administrator
account, and then back again. Once the credentials were set back to those
which (supposedly) were originally in place, the service ran fine.

--
 
Back
Top