OK--sorry for the misunderstanding. Since I use NNTP (a mail-based
mechanism) to connect to these groups, "page" confused me.
I would re-try the update. You need to get this one in, since it is a Full
update with an Engine upgrade---or successive updates will result in your
being out of synch on the Engine level until the next FE update.
If successive attempts fail, go to a command prompt in the Windows Defender
installation folder and do:
mpcmdrun -RemoveDefinitions -All
and then re-try updating--preferably using Engel's posts giving both the
Full and succeeding differential updates needed to get current from 1.0.0
--
"newhavenr" <(E-Mail Removed)> wrote in message
news:1407F77A-BD0A-4C2E-A4D4-(E-Mail Removed)...
> duh? to the page and post to which I replied!
> Windows Defender x64 definition update 1.14.1929.4
> posted by Dobrin 12/8/2006 12:31 PM PST
>
> My IT unit blocks normal updates for Windows Defender, and blocks direct
> update of other MS updates that they don't push out. So I update Defender
> manually from downloads posted to your web site.
>
> I am running Win XP sp2. current up to, but not including this week's
> patches.
>
>
> "Bill Sanderson MVP" wrote:
>
>> I'm list.
>>
>> What page?
>>
>> What program or update?
>>
>> What version of Windows XP are you running?
>>
>> --
>>
>> "newhavenr" <(E-Mail Removed)> wrote in message
>> news:C87B7AC1-992A-4EA3-B1C5-(E-Mail Removed)...
>> > did not install correctly. first time. other Defender profile updates
>> > from
>> > this page installed fine. received system error that [pgm] was "not a
>> > proper
>> > win32 application".
>> >
>> > "Dobrin" wrote:
>> >
>> >> URL:
>> >> http://www.download.windowsupdate.co...8082b6b4fe.exe
>> >> Size: 3744584 bytes
>> >> MD5: ed22e2241c3a6a8616055db8892df70f
>> >> Engine Version: 1.1.1804.0
>> >> Definition Version: 1.14.1929.4
>> >>
>>
>>
>>