Explanation of error 0x8050800c using engine build 1.1.1186.0

[Mike Treit [Msft]]

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

 

[Guest]

My system drive is configured as a dynamic disk and I am getting the error
0x8050800c as you report, I just wanted to also let you know that I always
get the error when the scan attempts to scan the
c:\winnt\system32\wowexec.exe file on my Windows 2000 Server SP4 machine.
Will the fix in the next engine build fix this and in the meantime is my
computer protected?

Damian

 

[Mike Treit [Msft]]

The file that is displayed in the user interface as being scanned at the
time you get the error actually turns out to be unrelated to the problem.
The scan will typically always show the same file because the series of
actions taken during the scan is deterministic, and when the error happens
(while trying to load one of the registry hives from disk) the scan will
normally be in the same spot every time. But, rest assured that the file is
not relevant.

Yes, the next engine build should fix this issue.

As to whether you are protected, the answer is yes and no. In general the
realtime protection facility should continue to work, which does offer some
protection, but you will not be able to successfully perform either a quick
scan or full scan of your computer until the next engine release. This means
that it is possible that some spyware will not be detected during the
intervening period.

Thanks

-Mike

 

[Lyall Kingman]

I hadn't scanned for 4 days and when I tried to scan I got the error
message. My drive type is basic. My signature version is 1.13.1282.6 dated
2/23/06

Lyall Kingman

 

[Mike Treit [Msft]]

Can you please go to help | about and tell me what it says your engine
version is?

Thanks

-Mike

 

[Guest]

Mike,

I have been getting the 0x8050800c error for many days. I checked my drive
configuration. My system drive is a Basic disk.

What else would you like to know?

Thanks,
George

 

[Mike Treit [Msft]]

If you could confirm what engine version you are running (it's in the "About
Windows Defender" dialog) that would help.

If it's 1.1.1186.0, please send me an email and I can send you some tools
that will allow us to gather the information we need to investigate further.

Thanks

-Mike

 

[Guest]

Just downloaded today's (28th) update and still receiving the same error
message. Yes, my disks are dynamic, is that still a problem?

 

[Mike Treit [Msft]]

Yes, we have only released new signatures and not a new engine at this
point, so the fix is not available yet.

-Mike

 

[Guest]

Mike,

I used Microsoft Update and installed the latest version this morning. Here
is the version information from the About dialog.

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

I opened Defender and pressed the Scan button on the Home page. I quickly
received an invalid pointer error. I then chose a Quick Scan from the Scan
Menu. It ran for some time and then displayed the familiar 0x8050800c error.

Feel free to send or refer me to some tools. I'll gather the data and send
it back.

Regards,
George

 

[Dan Koerner]

Mike,

Would you happen to have a ballpark idea on ETA of the next engine build? Will it be accessed via Windows Update also?

 

[Guest]

I have the latest update & my disc is configured as basic but I'm still
getting the error report - the error seems to occur (& the scanner stop)on
the same file each time which is "C\Windows\system32\notepad.exe"
Hope this is helpful
Sam

 

[Bill Sanderson]

George--because postings here are largely anonymous, Mike doesn't have an
email address to reach you, unless you've cc:ed him by email on this
message. He's posting with a clear email, I believe--so just send him a
note via email.

 

[Mike Treit [Msft]]

I don't have an ETA yet for when we will release the new build, but yes it
will be accessed in the same manner as signature updates.

Thanks

-Mike

Mike,

Would you happen to have a ballpark idea on ETA of the next engine build?
Will it be accessed via Windows Update also?

 

[Guest]

My system drive is configured as a dynamic disk and I am getting the error
0x8050800c as you report, I just wanted to also let you know that I always
get the error when the scan attempts to scan the
c:\winnt\system32\wowexec.exe file on my Windows 2000 Server SP4 machine.
Will the fix in the next engine build fix this and in the meantime is my
computer protected?

Damian

 

[Guest]

Anyone know if the 3/7/06 definition update (1.14.1314.1) includes an update
to the scanning engine to fix this issue yet?

I really don't feel like having to uninstall WD-beta2 from my PCs &
re-installing MSAS-beta1; but I'm not feeling so safe right now either, with
not being able to successfully scan my systems...

 

[Mike Treit [Msft]]

No, that update does not include a fix for this issue yet.

Thanks

-Mike

 

[Guest]

I'm running into the error also and can't get WD B2 to scan. My notes on the
work to date:

Windows Defender encountered an error: 0x8050800c. An unexpected problem
occurred. Install any available updates, and then try to start the program
again....

This error occures around when WD is scanning Object Number near 24311, but
it is failing when scanning C:\windows\system32\wowexec.exe.

There is an error logged in the System Event Log for the failure.

Event ID: 1005 with the following Desrciption:
Windows Defender scan has encountered an error and terminated.
Scan ID: {5E79935F-ECDA-4A5E-A08A-83F5A86BA754}
Scan Type: AntiSpyware
Scan Parameters: Quick Scan
User: <computer>\<userID>
Error Code: 0x8050800c
Error description: An unexpected problem occurred. Install any
available updates, and then try to start the program again. (To check for
updates, click Start, click All Programs, and then click Windows Update.)

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

The link does not have any further info.

I'm running WXP Pro SP2 with all Windows Update patches. I'm running Symantec
Antivirus Ver 9.0.1.1000 with scan engine 51.3.0.11 and def file /8/2006 rev
7. I have SpyBot S&D installed and also running the Spybot S&D with the
latest patches. I've also tried disableing Symantec AV and Spybot S&D's file
protections.

I've run WU until I shown no optional or important programs to install, and
taken an reboot, and reinstalled WD but I still get the same error. Then I've
stopped and restarted WD, but I'm still getting this error. I've stopped NA
and SB S&D. I have Spyware Blaser v 3.5.1 with the 2/20/2006 updates
insatlled with allprotection enabled for IE and Mozilla/Firefox, along with
all the restricted sites protection being enabled. I updated the database to
the 3/7/2006 set and this did not prevent the error.

I installed WD B2 on another computer today without any errors.

I Googled for the error code, and finally ended up on the MS Beta forum
where they recommened trying a custom scan first (but I uninstalled
AS_Sigs.MSI prior to this, so I rerun that MSI once the custom scan failed
also.) Still no joy.

I've got:
Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1186.0
Signature Version: 1.14.1314.1

David

 

[Bill Sanderson]

David--this error is expected, due to a bug, on machines with dynamic disk
partitions, as opposed to basic disk partitions. Users with basic disk
partitions may also see it if the disk has errors that need to be corrected
via chkdsk.

You can see the type of partition via right-clicking My Computer, choosing
Manage, and then clicking on Disk Management, and looking at the type for
the partition in the left side of the lower right pane.

If you are getting the error because of a dynamic partition, the fix is
coming, but did not come in the most recent update.

 

[Dan Koerner]

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.