M
Mike Treit [Msft]
Information on errors 0x8020800c, 0x80508026, 0x80501001.
If you have encountered any of the error codes listed above, you may want to
review the information below for some details on possible causes and actions
you may want to consider taking to try and correct the issue. This
information is taken from other threads where these problems were reported.
Also, we will eventually improve the error messages so that they will
contain better information than the cryptic error codes you see in the
current build.
== Error 0x80280800c when performing a quick scan or full scan ==
This error happens when failing to load one of the registry hives on your
machine for some reason. We treat that (incorrectly) as a fatal error. When
we have seen this happen before, it is because of some file corruption on
disk, in at least one case caused by a failing hard drive.
I would recommend running chkdsk and a disk defrag on your machine if you
encounter this error, and see if that addresses the problem. If not, we
should release a fix for this along with one of our signature updates in the
near future.
Thanks to beta tester Dan Koerner for helping us investigate this one.
== Error 0x80508026 or 0x80501001 when trying to remove a threat ==
This error will occur if a threat is detected inside of a container such as
a ZIP file, RAR archive, etc.
The "remove" action cannot (in most cases) be applied to an object inside of
such containers, without deleting the entire container.
It might be worth noting that the original Antispyware beta did not have the
ability to scan inside such containers.
We still need to work on the best way to handle this scenario. The issue is
that you may have a ZIP file with tons of non-malicious file in it, but one
or more "bad" files as well that are detected. The question is: how should
we handle that? Deleting the entire container may inadvertently delete the
clean files as well, and that might not be what you want.
For now you can check if the ZIP file has anything else inside of it that
you want to keep. If not, just delete the ZIP file yourself and you will
have removed the threat.
If you really want to keep the ZIP file around but do not want to see this
error (and again, you can expect that in the future we will have a better
story here - at least not such a cryptic error message) you can disable
scanning inside archives. Clear the checkbox for "Scan inside archives" in
the General Settings section under the Tools menu. Generally, threats inside
archives, while good to know about, are not "active", meaning they can't do
anything bad to your system while inside the archive.
Thanks
-Mike
If you have encountered any of the error codes listed above, you may want to
review the information below for some details on possible causes and actions
you may want to consider taking to try and correct the issue. This
information is taken from other threads where these problems were reported.
Also, we will eventually improve the error messages so that they will
contain better information than the cryptic error codes you see in the
current build.
== Error 0x80280800c when performing a quick scan or full scan ==
This error happens when failing to load one of the registry hives on your
machine for some reason. We treat that (incorrectly) as a fatal error. When
we have seen this happen before, it is because of some file corruption on
disk, in at least one case caused by a failing hard drive.
I would recommend running chkdsk and a disk defrag on your machine if you
encounter this error, and see if that addresses the problem. If not, we
should release a fix for this along with one of our signature updates in the
near future.
Thanks to beta tester Dan Koerner for helping us investigate this one.
== Error 0x80508026 or 0x80501001 when trying to remove a threat ==
This error will occur if a threat is detected inside of a container such as
a ZIP file, RAR archive, etc.
The "remove" action cannot (in most cases) be applied to an object inside of
such containers, without deleting the entire container.
It might be worth noting that the original Antispyware beta did not have the
ability to scan inside such containers.
We still need to work on the best way to handle this scenario. The issue is
that you may have a ZIP file with tons of non-malicious file in it, but one
or more "bad" files as well that are detected. The question is: how should
we handle that? Deleting the entire container may inadvertently delete the
clean files as well, and that might not be what you want.
For now you can check if the ZIP file has anything else inside of it that
you want to keep. If not, just delete the ZIP file yourself and you will
have removed the threat.
If you really want to keep the ZIP file around but do not want to see this
error (and again, you can expect that in the future we will have a better
story here - at least not such a cryptic error message) you can disable
scanning inside archives. Clear the checkbox for "Scan inside archives" in
the General Settings section under the Tools menu. Generally, threats inside
archives, while good to know about, are not "active", meaning they can't do
anything bad to your system while inside the archive.
Thanks
-Mike