Explanation of error 0x8050800c using engine build 1.1.1186.0

  • Thread starter Thread starter Mike Treit [Msft]
  • Start date Start date
That could well be the source of the issue. I'm not sure how to fix that
one--a repair install would seem a bit much....

Can you post the error from event viewer? I can get easy google hits on the
missing hives which result in a no-boot situation, but yours is obviously
more subtle--there may be a workaround, and doing some digging with the
precise error message involved would be the way I'd go about looking for it.

As I recall the Microsoft explanation of this error--it relates to scanning
the registry hives--so I think you've probably put your finger on it the
cause, and now we should look for a fix.

--

Hmmm... I have a basic disc. Chkdsk didn't fix it for me.

I may have deleted some account(s) I shouldn't have... event viewer
indicates that the system needs a hive it can't find.
 
I uninstalled WD a couple of days ago, then finally today got up the nerve to do a repair install. What a hassle. I just now got everything cleared again... no event warnings or cautions. It's getting pretty late, so I will probably wait until tomorrow to try WD again. I'll post any outcome.
 
Ugh--lot of work. Glad it came out ok in the end--I've never had a problem
with that kind of install, but I've done very few of them with XP.

--

I uninstalled WD a couple of days ago, then finally today got up the nerve
to do a repair install. What a hassle. I just now got everything cleared
again... no event warnings or cautions. It's getting pretty late, so I will
probably wait until tomorrow to try WD again. I'll post any outcome.
 
I am getting the error with a basic partition and the following configuration:

Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1186.0
Signature Version: 1.14.1315.1

chkdsk did not signal any error.

Thanks
 
Thanks--I don't know what additional triggers there may be--you are not the
only one that I've heard from with like conditions--so clearly there is
something else.

--
 
One user has reported that a chdsk repair fixed this for him--but several
others have not found that to help.
 
I had this same problem, basic disk and chkdsk failing to help. I did find in my event viewer a kind of non-descriptive reference to an account registry hive not loading properly for a totally different process. Since Mike had reviewed a trace log of my error condition and responded to me basically as shown below, I decided to try a repair install. It worked... that error is now gone, along with a few others that were occurring for unexplained reasons. However, Defender is still somewhat rough around the edges.
 
Windows Defender encountered an error: 0x8050800c

I've checked on my system drive (Windows 2000 server) where configured as basic type disk, and with below information:

Windows Defender version: 1.1.1051.0
Engine version: 1.1.1186.0
Signature version: 1.14.1325.6

Please help me to solve on this problem as soon as problem.

-----------------------------------------------------------------------------------------------------------------------------

e
Mike Treit [Msft] said:
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
Click to expand...
 
Mike Treit said:
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


Mike: I have the same problem with my computer and Defender, I get the same error message every time Defender scans. My drives are all configured as basic, I have three drives on my system. Regards Fred
Click to expand...
 
Mike Treit said:
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

Fred 2794
Click to expand...
My disk is not configured as a dynamic disk and I encounter the error
message code 0x8050800c. My version of Defender is: 1.1.1347.0; Engine
version: 1.1.1481.0. Definition Version is: 1.14.1525.2. Regards Fred 2794
 
Hi Fred,

Please update Windows Defender w/ the latest Engine (1.1.1508.0 or later)
and signatures.
If the problem persists, please send me an e-mail at:
abivol-at-microsoft-dot-com with the details.

Thanks.
 
Can I get a copy too? I don't think that internal version has been release
to the public yet...
 
Hmm --at this writing, 1481 is the latest available engine on XP, at any
rate.
Here's hoping that the later code is released before long.
 
Mike Treit said:
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


from Fred 2794. I have the same problem with error code0x8050800, my disk configuration is Basic and my Defender version is 1.1.1347.0; engine version is 1.1.1481.0; definition is, 1.14.1525.2. How and where do I download version 1.1.1186.0 from? Our laptop has the same configuration and the currant version I have on my PC, works ok on it. Regards Fred2794
Click to expand...
 
Fred--can you update to the newest definition set and re-test? There was an
update yesterday, which included an engine update--so there may have been
changes which would affect this error on your system.

After the definition update, the Engine version should be 1.1.1508.0
 
Back
Top