Defender

[Guest]

I have used MS AntiSpyware since it started, and installed it on all the
clients I visit as a PC engineer. It was great.
Now the name has changed to Defender... my own PC refuses to scan. It
throws up an error that is not consistent. The error is "unexpected". It
seems to occur at different files in the scanning process. Sometimes the
error occurs at the same file - sometimes not.
There is no error number given, just an obscure location.
Now I dare not use Defender for anyone!
Help!

 

[Guest]

Hi Peter,

I am in exactly the same basket. I have 100's of clients running the
AntiSpyware and now the change has occurred I get the same error number and
other variants on Servers and Client machines.
Can someone help here.

 

[Guest]

Hi Mike,

I do have Dynamic Disks but unfornatuly they are in a Mirror Situation on
Server 2003.
I have just re-downloaded the Defender MSI file. Installation Successful,
and updates successful but the scan was unsuccessful.
I have also been recieving a similar error in XP but I think that was to do
with windows XP Automatic Updates change reciently. So I re-updated that and
will know if its fixed for XP after I re-boot.
Please let me know if there is anyway to get around the Server Based problem.

Regards
DAn

Hello Peter,

This is from Mike T.:

Subject: Explanation of error 0x8050800c using engine build 1.1.1186.0
2/27/2006 3:48 PM PST
By: Mike Treit [Msft]
In: microsoft.private.security.spyware.announcements

Last week we updated the scanning engine used in Windows Defender to version
1.1.1186.0. One of the changes in this new build was a fix for customers who
were reporting the error code 0x8050800c, which our investigation showed was
the result of corrupt registry hives failing to be loaded from disk.

With build 1.1.1186.0 the original problem is fixed, so if you have
downloaded the latest engine and signature updates you should no longer see
that error code due to failure to load a corrupted registry hive.

However, as part of the investigation for the previous issue we found some
cases where errors during scanning were not being reported. We made a change
to correct that, which has had the side-effect that numerous other users who
had not seen the original error are now reporting that they are hitting it
when performing a scan. This is because those users were actually
encountering the unexpected error condition all along, but it was being
ignored and no error message was being presented in the previous build.

Thanks to help from several beta testers active on these newsgroups, we have
confirmed the cause of these errors and will have a fix available the next
time we update the engine build. The issue is something we had already found
internally, but the fix did not make it into the previous update.

To summarize the new cause of the problem: if your system drive (the drive
on which you have installed Windows) is configured as a dynamic disk, rather
than as a basic disk, we will fail to load one of the registry hives during
a scan, and the error code 0x8050800c will be reported.

If you see this error, please verify whether or not your system drive is
configured as a basic or dynamic disk. You can do so by executing "start |
run | diskmgmt.msc" and then inspecting the value of the "Type" column for
your system drive in the list view.

If you see the error code 0x8050800c and your system drive is NOT configured
as a dynamic disk, please post a message in the newsgroups or send me an
email so we can investigate further.

Thanks

-Mike

I would recommend you use the Search For: box, and enter the error number to
get the lates news or advance in each NG.

Good luck

Еиςеl
--

The error message given whenever I run Defender is 0x8050800c (or very
similar).
Is there a fix for this?

 

[Bill Sanderson]

I believe that Microsoft has a fix for this, but that it is not yet
available to us. It'll come out via the standard update facility, which is
still fully functional, as is Real-time protection--on machines seeing this
error.

--

Hi Mike,

I do have Dynamic Disks but unfornatuly they are in a Mirror Situation on
Server 2003.
I have just re-downloaded the Defender MSI file. Installation Successful,
and updates successful but the scan was unsuccessful.
I have also been recieving a similar error in XP but I think that was to
do
with windows XP Automatic Updates change reciently. So I re-updated that
and
will know if its fixed for XP after I re-boot.
Please let me know if there is anyway to get around the Server Based
problem.

Regards
DAn

Hello Peter,

This is from Mike T.:

Subject: Explanation of error 0x8050800c using engine build 1.1.1186.0
2/27/2006 3:48 PM PST
By: Mike Treit [Msft]
In: microsoft.private.security.spyware.announcements

Last week we updated the scanning engine used in Windows Defender to
version
1.1.1186.0. One of the changes in this new build was a fix for customers
who
were reporting the error code 0x8050800c, which our investigation showed
was
the result of corrupt registry hives failing to be loaded from disk.

With build 1.1.1186.0 the original problem is fixed, so if you have
downloaded the latest engine and signature updates you should no longer
see
that error code due to failure to load a corrupted registry hive.

However, as part of the investigation for the previous issue we found
some
cases where errors during scanning were not being reported. We made a
change
to correct that, which has had the side-effect that numerous other users
who
had not seen the original error are now reporting that they are hitting
it
when performing a scan. This is because those users were actually
encountering the unexpected error condition all along, but it was being
ignored and no error message was being presented in the previous build.

Thanks to help from several beta testers active on these newsgroups, we
have
confirmed the cause of these errors and will have a fix available the
next
time we update the engine build. The issue is something we had already
found
internally, but the fix did not make it into the previous update.

To summarize the new cause of the problem: if your system drive (the
drive
on which you have installed Windows) is configured as a dynamic disk,
rather
than as a basic disk, we will fail to load one of the registry hives
during
a scan, and the error code 0x8050800c will be reported.

If you see this error, please verify whether or not your system drive is
configured as a basic or dynamic disk. You can do so by executing "start
|
run | diskmgmt.msc" and then inspecting the value of the "Type" column
for
your system drive in the list view.

If you see the error code 0x8050800c and your system drive is NOT
configured
as a dynamic disk, please post a message in the newsgroups or send me an
email so we can investigate further.

Thanks

-Mike

I would recommend you use the Search For: box, and enter the error number
to
get the lates news or advance in each NG.

Good luck

????l
--

The error message given whenever I run Defender is 0x8050800c (or very
similar).
Is there a fix for this?

:

I have used MS AntiSpyware since it started, and installed it on all
the
clients I visit as a PC engineer. It was great.
Now the name has changed to Defender... my own PC refuses to scan.
It
throws up an error that is not consistent. The error is
"unexpected". It
seems to occur at different files in the scanning process. Sometimes
the
error occurs at the same file - sometimes not.
There is no error number given, just an obscure location.
Now I dare not use Defender for anyone!
Help!

 

[Bill Sanderson]

If they are on dynamic disks, they will see this error until the fix is
pushed out, via the standard update process.

--

 

[Guest]

I would like to pass on this information i have determined. I have been using
AntiSpyware and now using Defender. I have updated to the most current
updates listed. I have had problems installing, updating, re-installing,
updating, and scanning. The systems i have used are my 2000 servers, 2000
Pro, XP, 2003 web edition, and 2003 SBS. Each opf these have different
situations, but what i have seen is that the problems seem to always be 2000
server or pro issues. During my testing i have also noticed that the systems
that have the problems are the ones that are using (multi-keys). What i mean
by multi keys is the older versions of windows I.E. 2000 could use the same
key and have many installs. We do testing before we put our systems out for
our customers and it would seem that any product that is able to be installed
and used as a so called genuine windows might sem to be in the backround as a
thought. I have just checked my systems and the 2000 systems all have dynamic
disks. My home system is 2000 Pro and i have the same error, but i have not
yet checked if it has dynamic disk since i am currently at work. So i pose
this question "is there any correlation of the Key that could be a issue with
these errors?" The other question is "does the dynamic disk problem only
happen on systems that are using the mirror option, or does this happen on
dynamic disks that are not mirrored?"

Hello Peter,

This is from Mike T.:

Subject: Explanation of error 0x8050800c using engine build 1.1.1186.0
2/27/2006 3:48 PM PST
By: Mike Treit [Msft]
In: microsoft.private.security.spyware.announcements

Last week we updated the scanning engine used in Windows Defender to version
1.1.1186.0. One of the changes in this new build was a fix for customers who
were reporting the error code 0x8050800c, which our investigation showed was
the result of corrupt registry hives failing to be loaded from disk.

With build 1.1.1186.0 the original problem is fixed, so if you have
downloaded the latest engine and signature updates you should no longer see
that error code due to failure to load a corrupted registry hive.

However, as part of the investigation for the previous issue we found some
cases where errors during scanning were not being reported. We made a change
to correct that, which has had the side-effect that numerous other users who
had not seen the original error are now reporting that they are hitting it
when performing a scan. This is because those users were actually
encountering the unexpected error condition all along, but it was being
ignored and no error message was being presented in the previous build.

Thanks to help from several beta testers active on these newsgroups, we have
confirmed the cause of these errors and will have a fix available the next
time we update the engine build. The issue is something we had already found
internally, but the fix did not make it into the previous update.

To summarize the new cause of the problem: if your system drive (the drive
on which you have installed Windows) is configured as a dynamic disk, rather
than as a basic disk, we will fail to load one of the registry hives during
a scan, and the error code 0x8050800c will be reported.

If you see this error, please verify whether or not your system drive is
configured as a basic or dynamic disk. You can do so by executing "start |
run | diskmgmt.msc" and then inspecting the value of the "Type" column for
your system drive in the list view.

If you see the error code 0x8050800c and your system drive is NOT configured
as a dynamic disk, please post a message in the newsgroups or send me an
email so we can investigate further.

Thanks

-Mike

I would recommend you use the Search For: box, and enter the error number to
get the lates news or advance in each NG.

Good luck

Еиςеl
--

The error message given whenever I run Defender is 0x8050800c (or very
similar).
Is there a fix for this?

 

[Bill Sanderson]

So i pose
this question "is there any correlation of the Key that could be a issue
with
these errors?" The other question is "does the dynamic disk problem only
happen on systems that are using the mirror option, or does this happen on
dynamic disks that are not mirrored?"

I'm not aware of any correlation with the install type--the key and the OS
version are related--VL keys won't work with standard retail or OEM
bits--only Volume Licensing bits, as I understand it. At any rate, I don't
have any VL key systems, but I have seen this error.

I believe others here have posted seeing this error on simple workstations
that happen to be configured as dynamic, no raid, no mirroring.