Error: 0x8050800c

[Guest]

I have McAfee VirusScan Enterprise 8 and Norton Ghost 10. And my XP Pro SP2
is already up to date with IE7 beta 2.
Everytime the Windows Defender scan my PC, it will have error aaaas follow:

Windows Defender encounted as error: 0x8050800c. An unexpected problem
occurred. Install any available, and then try to start the progeam again.

help!

 

[Guest]

Hello Sam,

By 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

You can send the e-mail at:
mtreit @ microsoft.com

I hope this post is helpful, let us know how it works ºut.
Еиçеl
--

 

[Guest]

My Signature Version is 1.14.1288.5 built on 02/March/2006, and my hard disk
is dynamic disk. Is it the problem cause? and will this problem affect the
on-line Spyware scan?

Sam.

Hello Sam,

By 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

You can send the e-mail at:
mtreit @ microsoft.com

I hope this post is helpful, let us know how it works ºut.
Еиçеl
--

I have McAfee VirusScan Enterprise 8 and Norton Ghost 10. And my XP Pro SP2
is already up to date with IE7 beta 2.
Everytime the Windows Defender scan my PC, it will have error aaaas follow:

Windows Defender encounted as error: 0x8050800c. An unexpected problem
occurred. Install any available, and then try to start the progeam again.

help!

 

[Bill Sanderson]

Yes--the dynamic disc is the reason.

I'm not sure what on-line spyware scan you might mean.

This bug will prevent a full or quickscan from completing on your system.
It will not prevent updating and real-time protection is still fully
effective.

--

My Signature Version is 1.14.1288.5 built on 02/March/2006, and my hard
disk
is dynamic disk. Is it the problem cause? and will this problem affect
the
on-line Spyware scan?

Sam.

Hello Sam,

By 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

You can send the e-mail at:
mtreit @ microsoft.com

I hope this post is helpful, let us know how it works ºut.
??ç?l
--

I have McAfee VirusScan Enterprise 8 and Norton Ghost 10. And my XP Pro
SP2
is already up to date with IE7 beta 2.
Everytime the Windows Defender scan my PC, it will have error aaaas
follow:

Windows Defender encounted as error: 0x8050800c. An unexpected problem
occurred. Install any available, and then try to start the progeam
again.

help!

 

[Bill Sanderson]

Just to clarify--this is a bug, and a fix is in the works, but not yet
distributed--it will come as a normal update, through the program or
WindowsUpdate.

--

My Signature Version is 1.14.1288.5 built on 02/March/2006, and my hard
disk
is dynamic disk. Is it the problem cause? and will this problem affect
the
on-line Spyware scan?

Sam.

Hello Sam,

By 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

You can send the e-mail at:
mtreit @ microsoft.com

I hope this post is helpful, let us know how it works ºut.
??ç?l
--

I have McAfee VirusScan Enterprise 8 and Norton Ghost 10. And my XP Pro
SP2
is already up to date with IE7 beta 2.
Everytime the Windows Defender scan my PC, it will have error aaaas
follow:

Windows Defender encounted as error: 0x8050800c. An unexpected problem
occurred. Install any available, and then try to start the progeam
again.

help!

 

[Guest]

I have the same problem, I have two Harddrives and they both are Dynamic and
I get the same error my Signature Version is 1.14.1315.1 built on 3/8/2006 at
4:06am.

Just to clarify--this is a bug, and a fix is in the works, but not yet
distributed--it will come as a normal update, through the program or
WindowsUpdate.

--

My Signature Version is 1.14.1288.5 built on 02/March/2006, and my hard
disk
is dynamic disk. Is it the problem cause? and will this problem affect
the
on-line Spyware scan?

Sam.

Hello Sam,

By 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

You can send the e-mail at:
mtreit @ microsoft.com

I hope this post is helpful, let us know how it works ºut.
??ç?l
--

:

I have McAfee VirusScan Enterprise 8 and Norton Ghost 10. And my XP Pro
SP2
is already up to date with IE7 beta 2.
Everytime the Windows Defender scan my PC, it will have error aaaas
follow:

Windows Defender encounted as error: 0x8050800c. An unexpected problem
occurred. Install any available, and then try to start the progeam
again.

help!

 

[Bill Sanderson]

One day, when we least expect it... it'll go away (Here's hoping!)

--

I have the same problem, I have two Harddrives and they both are Dynamic
and
I get the same error my Signature Version is 1.14.1315.1 built on 3/8/2006
at
4:06am.

Just to clarify--this is a bug, and a fix is in the works, but not yet
distributed--it will come as a normal update, through the program or
WindowsUpdate.

--

My Signature Version is 1.14.1288.5 built on 02/March/2006, and my hard
disk
is dynamic disk. Is it the problem cause? and will this problem affect
the
on-line Spyware scan?

Sam.

:

Hello Sam,

By 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

You can send the e-mail at:
mtreit @ microsoft.com

I hope this post is helpful, let us know how it works ºut.
??ç?l
--

:

I have McAfee VirusScan Enterprise 8 and Norton Ghost 10. And my XP
Pro
SP2
is already up to date with IE7 beta 2.
Everytime the Windows Defender scan my PC, it will have error aaaas
follow:

Windows Defender encounted as error: 0x8050800c. An unexpected
problem
occurred. Install any available, and then try to start the progeam
again.

help!

 

[hlv]

0x8050800c and Win2003 server

I have been running MS Spyware beta very happily for a long time.
When MS Defender occuret, I installed it (naive as I may be).
Since the first update, it has unconditionally crashed all scans scheduled as well as manually initiated with 0x8050800c on both my W2003 SP1 servers.

I do use dynamic mirrorred drives - who can run professionally without that ?

It does not seem to consern the MS people at all - no info available on their beta site at all on this problem, which seem to be rather general in nature.

I therefore want to reinstall MS Spyware beta - but where do I find an installable version ? The one I have saved says "expired".

Best regards

Harald

 

[Guest]

hi,

I have the same problem, I have two Harddrives and they both are BASIC and
I get the same error my Signature Version is 1.14.1361.6 built on 30/3/2006
at
11:08.