error 0x8050800c

[Guest]

i get this error everytime it tries to do a scan.. i have uninstalled
re-installed ran a standalone scan and still no luck... i am using xp sp2..

anyone got any clues...

 

[Guest]

I was getting that message too until I downloaded the updates on the 23rd.
After that I was able to run a scan without a problem.

 

[Guest]

System:
Microsoft Windows Server 2003 R2 Enterprise Edition SP1

When I install Windows Defender but do not allow the updates. It runs
without error.
After I run the update for the most current engine and signature I get the
following error:

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

I've installed all updates using the Microsoft Update Link:
http://update.microsoft.com/microsoftupdate/v6/

The follow are from my event logs:

Event Type: Information
Event Source: MsiInstaller
Event Category: None
Event ID: 11707
Date: 2/26/2006
Time: 8:02:13 PM
User: VMS001\Administrator
Computer: VMS001
Description:
Product: Windows Defender -- Installation operation completed successfully.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 4241437b 30453939 39422d36 342d4632
0010: 2d304541 44413938 4139442d 39393543
0020: 36343031 7d46

Event Type: Information
Event Source: WinDefend
Event Category: None
Event ID: 1000
Date: 2/26/2006
Time: 8:02:27 PM
User: N/A
Computer: VMS001
Description:
Windows Defender scan has started.
Scan ID: {C669F713-BE26-46F3-B253-B90E86DF1B3B}
Scan Type: AntiSpyware
Scan Parameters: Quick Scan
User: VMS001\Administrator

Event Type: Information
Event Source: WinDefend
Event Category: None
Event ID: 1001
Date: 2/26/2006
Time: 8:02:48 PM
User: N/A
Computer: VMS001
Description:
Windows Defender scan has finished.
Scan ID: {C669F713-BE26-46F3-B253-B90E86DF1B3B}
Scan Type: AntiSpyware
Scan Parameters: Quick Scan
User: VMS001\Administrator
Scan Time: 0:00:21

Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1185.0
Signature Version: 1.0.0.0

Ran update:
Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1186.0
Signature Version: 1.13.1282.6

Event Type: Information
Event Source: MsiInstaller
Event Category: None
Event ID: 11728
Date: 2/26/2006
Time: 8:10:14 PM
User: VMS001\Administrator
Computer: VMS001
Description:
Product: Windows Defender Signatures -- Configuration completed successfully.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 4335417b 30413243 39452d39 342d3344
0010: 2d434539 44333239 3833302d 42423437
0020: 32433444 7d43

Event Type: Information
Event Source: Windows Update Agent
Event Category: Installation
Event ID: 19
Date: 2/26/2006
Time: 8:10:19 PM
User: N/A
Computer: VMS001
Description:
Installation Successful: Windows successfully installed the following
update: Definition Update 1.13.1282.6 for BETA Windows Defender (KB915597)
Data:
0000: 57 69 6e 33 32 48 52 65 Win32HRe
0008: 73 75 6c 74 3d 30 78 30 sult=0x0
0010: 30 30 30 30 30 30 30 20 0000000
0018: 55 70 64 61 74 65 49 44 UpdateID
0020: 3d 7b 32 41 31 41 34 32 ={2A1A42
0028: 34 43 2d 42 41 31 42 2d 4C-BA1B-
0030: 34 31 32 31 2d 38 30 45 4121-80E
0038: 38 2d 39 37 31 32 46 36 8-9712F6
0040: 42 30 44 30 43 44 7d 20 B0D0CD}
0048: 52 65 76 69 73 69 6f 6e Revision
0050: 4e 75 6d 62 65 72 3d 31 Number=1
0058: 30 30 20 00 00 .

Event Type: Information
Event Source: WinDefend
Event Category: None
Event ID: 2000
Date: 2/26/2006
Time: 8:10:14 PM
User: N/A
Computer: VMS001
Description:
Windows Defender signature version has been updated.
Current Signature Version: 1.13.1282.6
Previous Signature Version: 1.0.0.0
Update Source: Scheduled
Signature Type: AntiSpyware
Update Type: Full
User: VMS001\Administrator
Current Engine Version: 1.1.1186.0
Previous Engine Version: 1.1.1185.0

Event Type: Information
Event Source: WinDefend
Event Category: None
Event ID: 1000
Date: 2/26/2006
Time: 8:13:22 PM
User: N/A
Computer: VMS001
Description:
Windows Defender scan has started.
Scan ID: {9B215A8A-15B9-4BED-9C39-FB1F685C67F1}
Scan Type: AntiSpyware
Scan Parameters: Full Scan
User: VMS001\Administrator

Event Type: Error
Event Source: WinDefend
Event Category: None
Event ID: 1005
Date: 2/26/2006
Time: 8:13:45 PM
User: N/A
Computer: VMS001
Description:
Windows Defender scan has encountered an error and terminated.
Scan ID: {9B215A8A-15B9-4BED-9C39-FB1F685C67F1}
Scan Type: AntiSpyware
Scan Parameters: Full Scan
User: VMS001\Administrator
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.)

It looks like the lates Windows Defender Update has a bug and was not
properly tested before being released...

 

[Bill Sanderson]

Your log entries are helpful, since they show that you are on the current
engine version, which resolved some of these errors, including the one
alan1801 had.

However, your post and others make it clear that there is still some
circumstance which is hitting this error.

--

 

[Dan Koerner]

Mike Treit (MSFT) analyzed trace data from my x64 system that I sent to him on 2/15. He also made some comment about this same efgfect on or about 2/16 in this forum. The following is what he had to say about this error....
~~~~~~~~~
Hi Dan.

Thanks again for your help and patience while we investigated this issue.

You are hitting a problem that we are going to fix in a forthcoming update. We have been investigating the same issue on some machines here at Microsoft that encountered the same problem in the past day or so.

Basically, we are failing to load one of the registry hives on your machine for some reason, and we treat that (incorrectly) as a fatal error. When we have seen this happen before, it is because of some file corruption on disk, in at least one case caused by a failing hard drive.

It's not clear why we fail to load the hive in your particular case - you may check if you have some unused user accounts on the machine that may have some registry hives that haven't been loaded in a long time and somehow were corrupted. Deleting such accounts (if they are unused) may allow you to work around the problem for now. Unfortunately our tracing is a bit lacking for this particular scenario, so I can't say for sure which account's hive fails to load. (Better tracing is something we are also adding in an upcoming release.)

I would recommend running chkdsk and a disk defrag on your machine, in any event, as that might clear up the problem. If not, we should release a fix for this along with one of our signature updates in the near future.

Thanks

-Mike

~~~~~~~~~~~~~~

There are only two accounts on this machine, Mine and Administrator. Both are working fine. The chkdsk and defrag did NOT solve my issue. Sooooo.... I am awaiting the fix from MS. This is a certified software bug and MS is definitely aware of it... thanks to Mike.

 

[Mike Treit [Msft]]

Please see my earlier post in the announcements newsgroup entitled
'Explanation of error 0x8050800c using engine build 1.1.1186.0' for a
description of why you are most likely hitting this problem.

Basically, if your system drive is a dynamic disk you will see this error
until the next engine update happens.

Thanks

-Mike

 

[Guest]

Mike,
Thanks for the explanation. Fits my situation exactly. Question now is,
When is the next engine update going to occur. Soon I hope.

Rick

 

[Guest]

thanks mike that answered it perfectly does this mean though at the moment it
is not scanning properly? should i be using another spyware protector?

 

[Bill Sanderson]

Yes--it does mean that scans are not completing. Real-time protection is
working normally, though, as is the update functionality. You may want to
do full scans with another product in the interim.

 

[Guest]

Cheers Mate

Please see my earlier post in the announcements newsgroup entitled
'Explanation of error 0x8050800c using engine build 1.1.1186.0' for a
description of why you are most likely hitting this problem.

Basically, if your system drive is a dynamic disk you will see this error
until the next engine update happens.

Thanks

-Mike

 

[mon]

Looks as though no-one has had 'error 0x8050800c' in Defender for quite a
while.
I am running XP pro Sp3.
Windows Defender Version: 1.1.1593.0
Engine Version: 1.1.3520.0
Definition Version: 1.33.9651.0
Every scan crashes with unexpected 'error 0x8050800c'.
Any ideas?

 

[Dave M]

No we haven't seen that in a good long time. Are you using a dynamic disk
as suggested? Seems like it might be a regression error. Here is the
original "earlier post" from Mike Treit if you haven't seen the full text:
http://www.pcreview.co.uk/forums/thread-2426407.php

As Bill Sanderson said at that time "One day, when we least expect it...
it'll go away (Here's hoping!)" Wondering if it's now back to bite again?

 

[Bill Sanderson]

Thanks for digging that thread up!

As I recall, that error had multiple causes, and they were trying to pin
down the most frequent ones.

I think I would recommend a chkdsk run, just to be sure there's no clearcut
file corruption involved--but I'm not sure that catches corrupt registry
hives--presumably that's not filesystem corruption, but data corruption.

I'll bet Mike Treit's email which is there in that thread is still good...