error: 0x8050800f generated by Denfender scan

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Op Sys: Win XP Pro SP2 with all updates applied
CPU: Athalon 64
Other: Usually have multiple accounts logged on the same machine
simultaneously (using fast user switching).

I find the following error message waiting for me in the mornings. I am
assuming that it is generated when Windows Defender trys to run its daily
scan.
"Windows Defender encountered an error: 0x8050800f. 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 followed the directions provided in the error message. I have applied
all available updates; this has not resolved the problem. I am still getting
the same error message. The error message is generated in both active user
accounts that are simultaneously logged on through the night. I'm not 100%
certain, but I believe that the error only occurs once per log in or boot. In
other words, if I say "OK" to the message I won't see it again until I log in
an out of an account. Again, I'm not 100% certain about the last statement.
 
Thanks --I see this myself, on a Windows 2000 server that commonly has
Terminal Services admin sessions running as well as the console session.

It appears to me that the scans are completing, based on the system log
records.

I've been ignoring it--I think maybe I'll see if it goes away with the next
update to happen that fixes some other scanning errors, and if this doesn't
go away, I'll complain more then.
 
I get the same message. I didn't get it this morning. I made a change
yesterday to the time that it does it's daily scan. It just so happens that
I had OneCare updating and scanning at the same time so I change the time on
Defender. Don't know if they are related but we will see.
 
I have also been seen these failures. They occurs only when multiple
accounts are logged in. When only one account is logged in it does not
happen.

Dan
 
When you get the same message, do you have more than one account logged
(simultaneously)?
 
It may be valuable to the developers to confirm that this error msg is
isolated to cases where more than one account is logged simultaneously.

Is anyone in the community receiving this error message when only one
account is logged?

Dan, do you get this message every time the scan runs or only the first time
the scan runs after logging multiple accounts? I seem to only get it the
error message on the first scheduled scan after logging multiple accounts.
IOW, if I leave multiple accounts logged (simultaneously) for several days
(which I normally do) then I only get the error message after the first auto
scan. The error message doesn't recurr until I log in an out of the accounts.
Then it will occur again on the first scheduled scan.
 
I see this message every morning after a scheduled quick scan runs when I
have multiple user accounts logged-in. I run a quick scan at 2:00 am each
morning. I do not see it when I have one user account logged-in. I do not
see it when I run a manual quick scan.

Dan
 
I've been seeing the error on several machines, but all with single instance
login.

WHY is there no answer to this, when so many are getting it?
 
Back
Top