Error 0x8050800f

[Guest]

I am getting this error message, any fix for it? I'm running Windows XP Home
Edition SP2 with all updates.

 

[Guest]

Additional info: I went to the event log, and this was under properties for
the error:
"Windows Defender Real-Time Protection agent has detected potential malware.
For more information please see the following:
http://www.microsoft.com
Scan ID: {5AD020FE-D4A5-410E-BF78-F7A0D958F60E}
User: HPMZC61\Owner
Threat Name: Unknown
Threat Id:
Threat Severity:
Threat Category:
Path Found: file:C:\WINDOWS\tasks\McAfee.com Scan for Viruses - My
Computer (1) (HPMZC61-Owner).job;file:c:\program
files\mcafee.com\vso\mcmnhdlr.exe;taskscheduler:C:\WINDOWS\tasks\McAfee.com
Scan for Viruses - My Computer (1) (HPMZC61-Owner).job
Threat Classification: Unknown
Detection Type:


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

I am running McAfee Antivirus and Firewall if that helps any.

 

[Guest]

Hello thebigdintexas,
Try this:
First remove all temporarily junk with CCleaner using Issues too.
http://www.ccleaner.com

Online
Then try Ewido for removal:
http://www.ewido.net/en/download/

http://safety.live.com/site/en-US/default.htm
Еиςеl

 

[Guest]

It would appear to me from that log I posted that Windows Defender does not
recognize McAfee's task scheduler key. Is this a know problem? An answer
from a microsoft representative would be helpfull.

 

[Bill Sanderson]

The known issues posted at the web site state that there are no known
incompatibilities with other antivirus or antispyware apps.

I would agree with you that this has the appearance of an app compatiblity
or false postive issue.

Did you get notification of this finding, in addition to the event log
message--your initial message implies yes?

If so, are you set as an advanced Spynet member, and have you intentionally
turned on notification of not-yet-classified items?

I think the fact that you were notified on this one, as opposed to just
having the event log message posted with no user notification--is a
consequence of those additional settings that you've made. I'd allow this
one--that should trigger a spynet vote which over time will perhaps change
this from not yet classified to known.


--

 

[Bill Sanderson]

Whoops - meant to say that I'm not a Microsoft rep--today's a holiday for
them, I suspect, and they don't respond to many threads.

 

[Guest]

I did not get any other notice other than what was in the event log. I have
the "basic spynet member" choice selected.

 

[Bill Sanderson]

I think your analysis is correct. The McAfee code involved is not
recognized as "known."

I don't think this is uncommon, especially in a beta--I'm sure this is one
reason that the incidents that give rise to these log messages are not, by
default, brought to the attention of the user.

As long as you are satisfied that what is involved is legitimate McAfee
code, I'd ignore this message--Microsoft and McAfee will need to build the
communication links to make sure that their apps are labelled
appropriately--and that may take time.

--

 

[Guest]

Just a suggestion then........perhaps a warning message that this code, file,
whatever, is not known could pop up, with a choice to send the information to
microsoft for analysis.