> Error code: 0x80508007
> Error description: Your computer is low on memory. Close some programs and
> try again, or search Help and Support for information about preventing low
> memory problems
Could your computer be low on memory? Try running Disk Cleanup & then
reboot.
Can you update Defender manually via
http://www.microsoft.com/security/portal/ ??
[Did you also post this in WinXP General?]
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/
Tried stopping all other programs and retrying - still failed.
Sysinternals Process Explorer shows plenty of free memory (I have 2GB of RAM
with 1.3GB free) - what else could it be?
I have recently installed XP SP3, but previous Windows Defender updates and
several other updates installed successfully since that.
This failure seems to be exclusive to the latest version of KB915597
(Definition 1.35.716.0). Is there something wrong with that?
NB: Defender will NOT be happy and its "Alert!" icon will continue to appear
in Notification Area until an update is successfully installed. This does
NOT mean that Defender is not working/protecting your machine.
I have alerted MS and the Defender team to this apparent bug via private
channels.
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/
Glad it is not just me.
Thanks.
"PA Bear [MS MVP]" wrote:
>I have reproduced this problem (error 0x80070643). Users may encounter this
>problem when updating Defender via Automatic Update, Windows Update, or from
>within Defender (Check for updates function).
>
>NB: Defender will NOT be happy and its "Alert!" icon will continue to appear
>in Notification Area until an update is successfully installed. This does
>NOT mean that Defender is not working/protecting your machine.
Not necessarily: I uninstalled and reinstalled Windows Defender in an
attempt to fix the problem, and it's now stuck at Definition version
1.0.0.0 2006/01/25, so my machine isn't terribly well protected.
>I have alerted MS and the Defender team to this apparent bug via private
>channels.
I'm frankly stunned that this could get released with such a clear
problem, and that Windows Security Support still doesn't know about it
(as of my call 2 hours ago).
--
Best regards,
John Navas <http:/navasgroup.com>
On Wed, 25 Jun 2008 03:08:00 -0700, Wawa
<Wa...@discussions.microsoft.com> wrote in
<A94D61DF-112F-44D2...@microsoft.com>:
--
>I downloaded definition update for windows defender (KB915597) and received
>an error 0x80508007. I've rebooted, but the update install still failed.
>What do I need to do? Thanks
Definition update 1.35.716.0 was defective.
Manual Definition update at Microsoft Malware Protection Center
<http://www.microsoft.com/security/portal/ADL.aspx> is now up to version
1.35.745.0, which works properly, and which isn't yet on Windows Update
or Windows Defender Update. This seems to be the place to go for the
most current update.
It's easy to understand how vulnerabilities get into Microsoft software
when Definition updates aren't even being designed and tested well
enough to install properly.
--
The Security Portal has been the place to go for *daily* updates for almost
a year now (IIRC the Security Portal went live on 01 Jul-07). Automatic
Updates for Defender are only pushed twice a week, usually Tuesday and
Thursday afternoons Pacific Time.
> It's easy to understand how vulnerabilities get into Microsoft software
> when Definition updates aren't even being designed and tested well
> enough to install properly.
I'm no apologist for MS but gimme a break: There have been *daily* updates
for Defender for several years now (though they weren't available to
Consumers until last year) and probably 99.9% of them have installed without
a hitch.
The first indication of the glitch I saw was posted in WinXP General at 1:08
PM PT. Definitions v1.35.740.0 or greater had been tested and made
available less than five (5) hours later.
PS: Tuesday's glitch did not affect Windows Vista, Windows Server 2003, or
Windows Server 2008.
>John Navas wrote:
>> It's easy to understand how vulnerabilities get into Microsoft software
>> when Definition updates aren't even being designed and tested well
>> enough to install properly.
>
>I'm no apologist for MS but gimme a break: There have been *daily* updates
>for Defender for several years now (though they weren't available to
>Consumers until last year) and probably 99.9% of them have installed without
>a hitch.
That's no excuse for one to get pushed out with such an obvious fault.
It suggests that Microsoft isn't doing automated regression testing on
"down level" Windows XP, which I'd call a serious omission, since it's
still the great majority of the market (on the order of 75%). If
Microsoft's actions matched its rhetoric on security and quality this
wouldn't have happened.
>The first indication of the glitch I saw was posted in WinXP General at 1:08
>PM PT. Definitions v1.35.740.0 or greater had been tested and made
>available less than five (5) hours later.
>
>PS: Tuesday's glitch did not affect Windows Vista, Windows Server 2003, or
>Windows Server 2008.
Small comfort to the great majority of Windows users.
p.s. I'm resisting the temptation to suggest Microsoft might not be
applying the same level of care to Windows XP as to later OS versions,
so as to incentivize migration to Windows Vista, but others might not be
as charitable. ;)