Error Code: 0x8050800c

G

Guest

EVT VWR Log

Windows Defender scan has encountered an error and terminated.
Scan ID: {5344F0A7-1755-4BF1-9DBC-99D67AFD977F}
Scan Type: AntiSpyware
Scan Parameters: Quick Scan
User: Domain\User ID
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.)

I have tried to get updates but it always says it is up to date. I also
received this error while installing the program. I have uninstalled and
reinstallled twice.
 
G

Guest

Hello Spiney_Norman

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: announcements group


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

The e-mail to Mike is:
mtreit @ microsoft.com

I hope that (this) post is helpful, let us know how it works ºut.

Еиçеl
 
G

Guest

Thank you for the reply! Yes it is a Dynamic disk configuration. I use that
to distinguish between it and other drives I scope out and tech since most of
the company's drives are of the same size and configuration but set to basic.
That just keeps me from making a bad mistake:).

Neil S>Spiney_Norman

Engel said:
Hello Spiney_Norman

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: announcements group


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

The e-mail to Mike is:
mtreit @ microsoft.com

I hope that (this) post is helpful, let us know how it works ºut.

Еиçеl



Spiney_Norman said:
EVT VWR Log

Windows Defender scan has encountered an error and terminated.
Scan ID: {5344F0A7-1755-4BF1-9DBC-99D67AFD977F}
Scan Type: AntiSpyware
Scan Parameters: Quick Scan
User: Domain\User ID
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.)

I have tried to get updates but it always says it is up to date. I also
received this error while installing the program. I have uninstalled and
reinstallled twice.
 
G

Guest

Greetings. I am also experiencing this error message and I have a dynamic
disk. I have the latest software download (3/6/06). When will the fixed
"next version" be available? Until the fix, basically the program is
usless...

Thanks.
Stan

Engel said:
Hello Spiney_Norman

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: announcements group


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

The e-mail to Mike is:
mtreit @ microsoft.com

I hope that (this) post is helpful, let us know how it works ºut.

Еиçеl



Spiney_Norman said:
EVT VWR Log

Windows Defender scan has encountered an error and terminated.
Scan ID: {5344F0A7-1755-4BF1-9DBC-99D67AFD977F}
Scan Type: AntiSpyware
Scan Parameters: Quick Scan
User: Domain\User ID
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.)

I have tried to get updates but it always says it is up to date. I also
received this error while installing the program. I have uninstalled and
reinstallled twice.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top