Error 0x80508007 upon attempting first scan

[Guest]

Antispyware was working just fine. Updated to defender. Updated the
definitions. and now Defender on 2 gig Dell Dimension 8300 with XP SP2
reports this error with the further explanation of "Your computer is low on
memory." I've rebooted, reinstalled, etc. Looks like a major step backwards
from my point of view. I was truly impressed with the predecessor product.

 

[Bill Sanderson MVP]

If you've posted the error number accurately, this one is new to me.
Thanks--it's always interesting to find a new problem.

I'm wondering if there will be any additional detail, perhaps, in the System
events log?

Start, run, eventvwr.msc <enter>

Click on System in the left column, then on View, Filter. From the Source
dropdown control, choose WinDefend.

Scroll down in the right pane 'till you find entries associated with the
time of the attempted scan--if you can find one giving that error message,
double click on it, and use the button on the top right, below the arrows,
to cut and paste the details back to a reply here.

There are some scan errors that only happen if you press the "scan now"
button, and don't happen if you choose a scan from the menus--so you might
try that as well.

 

[Guest]

Regardless of where I try to kick off or the type of scan, I get the same error

Windows Defender scan has encountered an error and terminated.
Scan ID: {64F4F432-E9AB-437A-A736-D98564024E0D}
Scan Type: AntiSpyware
Scan Parameters: Full Scan
User: xxxx
Error Code: 0x80508007
Error description: Your computer is low on memory. Close some programs and
try again, or search Help for information about preventing low memory
problems.

and

Windows Defender scan has encountered an error and terminated.
Scan ID: {E2CF6E44-D775-4CEC-83E7-5CD62722E421}
Scan Type: AntiSpyware
Scan Parameters: Quick Scan
User: xxxx
Error Code: 0x80508007
Error description: Your computer is low on memory. Close some programs and
try again, or search Help for information about preventing low memory
problems.

 

[Bill Sanderson MVP]

As you observe the scan in progress--can you spot what is being examined?
Does it appear to hang?

I'm very tempted to ascribe this issue to malware--historically, both
Microsoft Antispyware, and I believe still--Windows Defender, have had some
problems with instances in which malware has changed registry permissions
preventing scanning.

You seem to be doing all the right things, so that makes me retreat a little
from that stance, but it seems worth investigating further.

Thoughts that I have include attempting scanning with Windows restarted in
safe mode. Similarly, if you restart in safe mode with networking, you
could do a scan at safety.live.com (This is a Microsoft site)--which would
give us an independent verification that the machine is clean. Since it is
Microsoft code, there's some chance it would evidence the same behavior, but
it may be worth a try. I'm a little hesitent, since scanning may be rather
slow--but at any rate, a scan with another vendor of your choice, Trend
Micro's housecall.trendmicro.com or any of the major antivirus vendors who
also go for spyware, might also be good choices.

--

 

[Guest]

Bill,
The hang is immediate with no evidence that even the first file gets
scanned.

I ran a Symantec scan (I have a small business corporate license with live
updates) that came up empty. Went to safety.live.com and ran a scan that
essentially came up empty except for some registry work which I allowed it to
do and some fragmentation and offline files--I use roaming profiles.

I'll reboot and see if safe mode yields anything.

<<<SLM>>>

 

[Guest]

Same error in safe mode.

Bill,
The hang is immediate with no evidence that even the first file gets
scanned.

I ran a Symantec scan (I have a small business corporate license with live
updates) that came up empty. Went to safety.live.com and ran a scan that
essentially came up empty except for some registry work which I allowed it to
do and some fragmentation and offline files--I use roaming profiles.

I'll reboot and see if safe mode yields anything.

<<<SLM>>>

 

[Steve Dodson [MSFT]]

What applications are running when you encounter this error? How much
installed memory do you have in your computer?

--
--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

 

[Steve Dodson [MSFT]]

Another quick thought here... what happens if you only run a quick scan?

--
--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

 

[Guest]

I have the same problem as Sam. Quick scan doesn't work. Neither does the
scheduled Scan at 2:00am (when my machine isn't very busy !) It fails
immediately and doesn't appear to attempt any scanning whatsoever.

Another quick thought here... what happens if you only run a quick scan?

--
--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

Same error in safe mode.

 

[Guest]

2 gig RAM

No applicactions running--even killed startup services looking for a conflict.

full scan or quick scan makes no difference--immediate error.

Another quick thought here... what happens if you only run a quick scan?

--
--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

Same error in safe mode.

 

[Bill Sanderson MVP]

Have you tried running chkdsk on any volumes involved in the scan?
(grasping at straws, really, but this seems a sensible thing to check.)

--

2 gig RAM

No applicactions running--even killed startup services looking for a
conflict.

full scan or quick scan makes no difference--immediate error.

Another quick thought here... what happens if you only run a quick scan?

--
--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

Same error in safe mode.

:

Bill,
The hang is immediate with no evidence that even the first file gets
scanned.

I ran a Symantec scan (I have a small business corporate license
with
live
updates) that came up empty. Went to safety.live.com and ran a scan
that
essentially came up empty except for some registry work which I
allowed
it to
do and some fragmentation and offline files--I use roaming profiles.

I'll reboot and see if safe mode yields anything.

<<<SLM>>>

:

As you observe the scan in progress--can you spot what is being
examined?
Does it appear to hang?

I'm very tempted to ascribe this issue to malware--historically,
both
Microsoft Antispyware, and I believe still--Windows Defender, have
had
some
problems with instances in which malware has changed registry
permissions
preventing scanning.

You seem to be doing all the right things, so that makes me retreat
a
little
from that stance, but it seems worth investigating further.

Thoughts that I have include attempting scanning with Windows
restarted
in
safe mode. Similarly, if you restart in safe mode with networking,
you
could do a scan at safety.live.com (This is a Microsoft site)--which
would
give us an independent verification that the machine is clean.
Since
it is
Microsoft code, there's some chance it would evidence the same
behavior, but
it may be worth a try. I'm a little hesitent, since scanning may be
rather
slow--but at any rate, a scan with another vendor of your choice,
Trend
Micro's housecall.trendmicro.com or any of the major antivirus
vendors
who
also go for spyware, might also be good choices.

--

Regardless of where I try to kick off or the type of scan, I get
the
same
error

Windows Defender scan has encountered an error and terminated.
Scan ID: {64F4F432-E9AB-437A-A736-D98564024E0D}
Scan Type: AntiSpyware
Scan Parameters: Full Scan
User: xxxx
Error Code: 0x80508007
Error description: Your computer is low on memory. Close some
programs
and
try again, or search Help for information about preventing low
memory
problems.

and

Windows Defender scan has encountered an error and terminated.
Scan ID: {E2CF6E44-D775-4CEC-83E7-5CD62722E421}
Scan Type: AntiSpyware
Scan Parameters: Quick Scan
User: xxxx
Error Code: 0x80508007
Error description: Your computer is low on memory. Close some
programs
and
try again, or search Help for information about preventing low
memory
problems.

:

If you've posted the error number accurately, this one is new to
me.
Thanks--it's always interesting to find a new problem.

I'm wondering if there will be any additional detail, perhaps, in
the
System
events log?

Start, run, eventvwr.msc <enter>

Click on System in the left column, then on View, Filter. From
the
Source
dropdown control, choose WinDefend.

Scroll down in the right pane 'till you find entries associated
with
the
time of the attempted scan--if you can find one giving that error
message,
double click on it, and use the button on the top right, below
the
arrows,
to cut and paste the details back to a reply here.

There are some scan errors that only happen if you press the
"scan
now"
button, and don't happen if you choose a scan from the menus--so
you
might
try that as well.


--

Antispyware was working just fine. Updated to defender.
Updated
the
definitions. and now Defender on 2 gig Dell Dimension 8300 with
XP
SP2
reports this error with the further explanation of "Your
computer
is
low
on
memory." I've rebooted, reinstalled, etc. Looks like a major
step
backwards
from my point of view. I was truly impressed with the
predecessor
product.

 

[Guest]

Ran chkdsk /F during reboot. Fixed a couple of minor issues. Same symptoms.
I also attempted a custom scan on just the windows directory of the c: drive
to no avail.

More suggestions?

Have you tried running chkdsk on any volumes involved in the scan?
(grasping at straws, really, but this seems a sensible thing to check.)

--

2 gig RAM

No applicactions running--even killed startup services looking for a
conflict.

full scan or quick scan makes no difference--immediate error.

Another quick thought here... what happens if you only run a quick scan?

--
--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
Same error in safe mode.

:

Bill,
The hang is immediate with no evidence that even the first file gets
scanned.

I ran a Symantec scan (I have a small business corporate license
with
live
updates) that came up empty. Went to safety.live.com and ran a scan
that
essentially came up empty except for some registry work which I
allowed
it to
do and some fragmentation and offline files--I use roaming profiles.

I'll reboot and see if safe mode yields anything.

<<<SLM>>>

:

As you observe the scan in progress--can you spot what is being
examined?
Does it appear to hang?

I'm very tempted to ascribe this issue to malware--historically,
both
Microsoft Antispyware, and I believe still--Windows Defender, have
had
some
problems with instances in which malware has changed registry
permissions
preventing scanning.

You seem to be doing all the right things, so that makes me retreat
a
little
from that stance, but it seems worth investigating further.

Thoughts that I have include attempting scanning with Windows
restarted
in
safe mode. Similarly, if you restart in safe mode with networking,
you
could do a scan at safety.live.com (This is a Microsoft site)--which
would
give us an independent verification that the machine is clean.
Since
it is
Microsoft code, there's some chance it would evidence the same
behavior, but
it may be worth a try. I'm a little hesitent, since scanning may be
rather
slow--but at any rate, a scan with another vendor of your choice,
Trend
Micro's housecall.trendmicro.com or any of the major antivirus
vendors
who
also go for spyware, might also be good choices.

--

Regardless of where I try to kick off or the type of scan, I get
the
same
error

Windows Defender scan has encountered an error and terminated.
Scan ID: {64F4F432-E9AB-437A-A736-D98564024E0D}
Scan Type: AntiSpyware
Scan Parameters: Full Scan
User: xxxx
Error Code: 0x80508007
Error description: Your computer is low on memory. Close some
programs
and
try again, or search Help for information about preventing low
memory
problems.

and

Windows Defender scan has encountered an error and terminated.
Scan ID: {E2CF6E44-D775-4CEC-83E7-5CD62722E421}
Scan Type: AntiSpyware
Scan Parameters: Quick Scan
User: xxxx
Error Code: 0x80508007
Error description: Your computer is low on memory. Close some
programs
and
try again, or search Help for information about preventing low
memory
problems.

:

If you've posted the error number accurately, this one is new to
me.
Thanks--it's always interesting to find a new problem.

I'm wondering if there will be any additional detail, perhaps, in
the
System
events log?

Start, run, eventvwr.msc <enter>

Click on System in the left column, then on View, Filter. From
the
Source
dropdown control, choose WinDefend.

Scroll down in the right pane 'till you find entries associated
with
the
time of the attempted scan--if you can find one giving that error
message,
double click on it, and use the button on the top right, below
the
arrows,
to cut and paste the details back to a reply here.

There are some scan errors that only happen if you press the
"scan
now"
button, and don't happen if you choose a scan from the menus--so
you
might
try that as well.


--

Antispyware was working just fine. Updated to defender.
Updated
the
definitions. and now Defender on 2 gig Dell Dimension 8300 with
XP
SP2
reports this error with the further explanation of "Your
computer
is
low
on
memory." I've rebooted, reinstalled, etc. Looks like a major
step
backwards
from my point of view. I was truly impressed with the
predecessor
product.

 

[Bill Sanderson MVP]

A custom scan runs a quickscan first, so if a quickscan fails, that will
too....

This kind of "out of memory" or low memory error used to appear with
Microsoft Antispyware when registry permissions were set on some keys such
that the scanner, which ran in user mode, couldn't access those (malware
related) keys.

I haven't seen this symptom before with Windows Defender, and am not at all
sure it has a similar cause. Do you know if any sort of "lockdown" work has
ever been done on the registry in this system?

If you create another user profile, probably better for it to be an
administrator, is a scan possible under that newly created profile?

--

Ran chkdsk /F during reboot. Fixed a couple of minor issues. Same
symptoms.
I also attempted a custom scan on just the windows directory of the c:
drive
to no avail.

More suggestions?

Have you tried running chkdsk on any volumes involved in the scan?
(grasping at straws, really, but this seems a sensible thing to check.)

--

2 gig RAM

No applicactions running--even killed startup services looking for a
conflict.

full scan or quick scan makes no difference--immediate error.

:

Another quick thought here... what happens if you only run a quick
scan?

--
--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to
this
message are best directed to the newsgroup/thread from which they
originated.
Same error in safe mode.

:

Bill,
The hang is immediate with no evidence that even the first file
gets
scanned.

I ran a Symantec scan (I have a small business corporate license
with
live
updates) that came up empty. Went to safety.live.com and ran a
scan
that
essentially came up empty except for some registry work which I
allowed
it to
do and some fragmentation and offline files--I use roaming
profiles.

I'll reboot and see if safe mode yields anything.

<<<SLM>>>

:

As you observe the scan in progress--can you spot what is being
examined?
Does it appear to hang?

I'm very tempted to ascribe this issue to malware--historically,
both
Microsoft Antispyware, and I believe still--Windows Defender,
have
had
some
problems with instances in which malware has changed registry
permissions
preventing scanning.

You seem to be doing all the right things, so that makes me
retreat
a
little
from that stance, but it seems worth investigating further.

Thoughts that I have include attempting scanning with Windows
restarted
in
safe mode. Similarly, if you restart in safe mode with
networking,
you
could do a scan at safety.live.com (This is a Microsoft
site)--which
would
give us an independent verification that the machine is clean.
Since
it is
Microsoft code, there's some chance it would evidence the same
behavior, but
it may be worth a try. I'm a little hesitent, since scanning may
be
rather
slow--but at any rate, a scan with another vendor of your choice,
Trend
Micro's housecall.trendmicro.com or any of the major antivirus
vendors
who
also go for spyware, might also be good choices.

--

Regardless of where I try to kick off or the type of scan, I
get
the
same
error

Windows Defender scan has encountered an error and terminated.
Scan ID: {64F4F432-E9AB-437A-A736-D98564024E0D}
Scan Type: AntiSpyware
Scan Parameters: Full Scan
User: xxxx
Error Code: 0x80508007
Error description: Your computer is low on memory. Close some
programs
and
try again, or search Help for information about preventing low
memory
problems.

and

Windows Defender scan has encountered an error and terminated.
Scan ID: {E2CF6E44-D775-4CEC-83E7-5CD62722E421}
Scan Type: AntiSpyware
Scan Parameters: Quick Scan
User: xxxx
Error Code: 0x80508007
Error description: Your computer is low on memory. Close some
programs
and
try again, or search Help for information about preventing low
memory
problems.

:

If you've posted the error number accurately, this one is new
to
me.
Thanks--it's always interesting to find a new problem.

I'm wondering if there will be any additional detail, perhaps,
in
the
System
events log?

Start, run, eventvwr.msc <enter>

Click on System in the left column, then on View, Filter.
From
the
Source
dropdown control, choose WinDefend.

Scroll down in the right pane 'till you find entries
associated
with
the
time of the attempted scan--if you can find one giving that
error
message,
double click on it, and use the button on the top right, below
the
arrows,
to cut and paste the details back to a reply here.

There are some scan errors that only happen if you press the
"scan
now"
button, and don't happen if you choose a scan from the
menus--so
you
might
try that as well.


--

Antispyware was working just fine. Updated to defender.
Updated
the
definitions. and now Defender on 2 gig Dell Dimension 8300
with
XP
SP2
reports this error with the further explanation of "Your
computer
is
low
on
memory." I've rebooted, reinstalled, etc. Looks like a
major
step
backwards
from my point of view. I was truly impressed with the
predecessor
product.

 

[Steve Dodson [MSFT]]

Can you get us a regmon while scanning?

--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

A custom scan runs a quickscan first, so if a quickscan fails, that will
too....

This kind of "out of memory" or low memory error used to appear with
Microsoft Antispyware when registry permissions were set on some keys such
that the scanner, which ran in user mode, couldn't access those (malware
related) keys.

I haven't seen this symptom before with Windows Defender, and am not at
all sure it has a similar cause. Do you know if any sort of "lockdown"
work has ever been done on the registry in this system?

If you create another user profile, probably better for it to be an
administrator, is a scan possible under that newly created profile?

--

Ran chkdsk /F during reboot. Fixed a couple of minor issues. Same
symptoms.
I also attempted a custom scan on just the windows directory of the c:
drive
to no avail.

More suggestions?

Have you tried running chkdsk on any volumes involved in the scan?
(grasping at straws, really, but this seems a sensible thing to check.)

--

2 gig RAM

No applicactions running--even killed startup services looking for a
conflict.

full scan or quick scan makes no difference--immediate error.

:

Another quick thought here... what happens if you only run a quick
scan?

--
--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to
this
message are best directed to the newsgroup/thread from which they
originated.
Same error in safe mode.

:

Bill,
The hang is immediate with no evidence that even the first file
gets
scanned.

I ran a Symantec scan (I have a small business corporate license
with
live
updates) that came up empty. Went to safety.live.com and ran a
scan
that
essentially came up empty except for some registry work which I
allowed
it to
do and some fragmentation and offline files--I use roaming
profiles.

I'll reboot and see if safe mode yields anything.

<<<SLM>>>

:

As you observe the scan in progress--can you spot what is being
examined?
Does it appear to hang?

I'm very tempted to ascribe this issue to malware--historically,
both
Microsoft Antispyware, and I believe still--Windows Defender,
have
had
some
problems with instances in which malware has changed registry
permissions
preventing scanning.

You seem to be doing all the right things, so that makes me
retreat
a
little
from that stance, but it seems worth investigating further.

Thoughts that I have include attempting scanning with Windows
restarted
in
safe mode. Similarly, if you restart in safe mode with
networking,
you
could do a scan at safety.live.com (This is a Microsoft
site)--which
would
give us an independent verification that the machine is clean.
Since
it is
Microsoft code, there's some chance it would evidence the same
behavior, but
it may be worth a try. I'm a little hesitent, since scanning
may be
rather
slow--but at any rate, a scan with another vendor of your
choice,
Trend
Micro's housecall.trendmicro.com or any of the major antivirus
vendors
who
also go for spyware, might also be good choices.

--

Regardless of where I try to kick off or the type of scan, I
get
the
same
error

Windows Defender scan has encountered an error and
terminated.
Scan ID: {64F4F432-E9AB-437A-A736-D98564024E0D}
Scan Type: AntiSpyware
Scan Parameters: Full Scan
User: xxxx
Error Code: 0x80508007
Error description: Your computer is low on memory. Close some
programs
and
try again, or search Help for information about preventing low
memory
problems.

and

Windows Defender scan has encountered an error and
terminated.
Scan ID: {E2CF6E44-D775-4CEC-83E7-5CD62722E421}
Scan Type: AntiSpyware
Scan Parameters: Quick Scan
User: xxxx
Error Code: 0x80508007
Error description: Your computer is low on memory. Close some
programs
and
try again, or search Help for information about preventing low
memory
problems.

:

If you've posted the error number accurately, this one is new
to
me.
Thanks--it's always interesting to find a new problem.

I'm wondering if there will be any additional detail,
perhaps, in
the
System
events log?

Start, run, eventvwr.msc <enter>

Click on System in the left column, then on View, Filter.
From
the
Source
dropdown control, choose WinDefend.

Scroll down in the right pane 'till you find entries
associated
with
the
time of the attempted scan--if you can find one giving that
error
message,
double click on it, and use the button on the top right,
below
the
arrows,
to cut and paste the details back to a reply here.

There are some scan errors that only happen if you press the
"scan
now"
button, and don't happen if you choose a scan from the
menus--so
you
might
try that as well.


--

Antispyware was working just fine. Updated to defender.
Updated
the
definitions. and now Defender on 2 gig Dell Dimension 8300
with
XP
SP2
reports this error with the further explanation of "Your
computer
is
low
on
memory." I've rebooted, reinstalled, etc. Looks like a
major
step
backwards
from my point of view. I was truly impressed with the
predecessor
product.