Defender: error 0x8050800c during scan

[Guest]

I have the same trouble with wowexec, bit pants really used to work at the
start then went downhill from there

Windows update says installed ok then eventvwr says: -

In Application

Event ID: 1024 Source: MsiInstaller

Product: Windows Defender Signatures - Update
'{46BE8A2F-A348-418A-BEA4-FFA98FF60E04}' could not be installed. Error code
1603. Windows Installer can create logs to help troubleshoot issues with
installing software packages. Use the following link for instructions on
turning on logging support: http://go.microsoft.com/fwlink/?LinkId=23127

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

System Log

Event ID: 1005 Source: WinDefend

Windows Defender scan has encountered an error and terminated.
Scan ID: {B5612794-4446-4978-83DB-4DAF0C501CA8}
Scan Type: AntiSpyware
Scan Parameters: Quick Scan
User: NT AUTHORITY\NETWORK SERVICE
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.)


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

 

[Bill Sanderson]

This is a bug--it isn't related to the specific file, but, according to a
Microsoft post--the scan is deterministic, so the failure will tend to occur
at the same filename.

There was a Microsoft post late last week suggesting that an engine update
might be posted early this week. It didn't happen yesterday, but perhaps
there'll be something on Thursday--we can hope!

--

 

[Bill Sanderson]

You've got more than one issue--have you tried

http://support.microsoft.com/?kbid=915105

for the updating issue?

--

 

[Guest]

Yes tried that thanks, Still bombs out after a whole 1 min 11 secs after
doing 18400 files with wowexec, but thanks for the tip

 

[Bill Sanderson MVP]

We need to get yesterdays update installed--That fixes the bomb out on the
crash--so the update issue is more important at this point.

Have you tried going the Windows Installer Cleanup tool route--and removing
"Windows defender signatures" and then retrying the update?

--

 

[Guest]

I installed the update from MS Update--check for updates in Defender did
zilch. I exited & restarted it.

So how do I get Defender to recognize that the definitions have been
updated? And I still get this:
Windows Defender encountered an error: 0x8050800c. 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.)

 

[Bill Sanderson MVP]

I'm not sure I have this straight:

You did an update via Windows or Microsoft Update: What update?--was it a
Defender definition update?

You then tried Check for Updates in Defender--did that go without an error,
even though it didn't actually find an update? Did you get the balloon
notifications?

What's the definition level currently in place as stated at the bottom of
the home page of Defender?

--

 

[Guest]

1. Yes.
2. Not exactly-- When I opened defender, even after updating the definitions
via MS update, I get "Windows Defender definitions havn't been updated in 39
days."

The signature version displayed is 1.13.1276.16 built on 2/15/2006 at 2:39 PM.

No balloon notifications (I turned that annoyance off years ago). When I
click "check for updates," first it does not grey out and something makes a
popup noise; when I retry, it greys out, lays there like a dead fish for a
while, then popoup noise again and the updates button is re-enabled.

And it still says it hasn't been updated.

 

[Guest]

i have 1.1.1051.0
1.1.1303.0
& 1.14.1353.2

and it still konks out

 

[Bill Sanderson MVP]

Those numbers are all current--so you are up to date. Explain "conks
out"--do you mean you are still seeing the error in the subject header for
this thread during a scan?

Have you run a chkdsk since you started seeing this error?

--

 

[Guest]

when i say konks out i mean that it gives me the error message (in the header
of this thread) on wowexec....and yes i ran a chkdsk on the drive

 

[Bill Sanderson MVP]

OK - I don't have a fix for your situation. My advice is to look for a
thread on this subject in which Mike Treit is participating--search on him
as the sender--and give him these same details--you've got the patch that
fixed some instances of this, but are still seeing the error. He may want
to collect more data from your machine.

--