Defender: error 0x8050800c during scan

  • Thread starter Thread starter ObiWan
  • Start date Start date
On my machine (XP Pro SP2 32-bit) the error is generated while scanning this
file: C:\WINDOWS\system32\wowexec.exe
Wow, indeed.
--piaqt
 
still receiving the error, in fact didn't receive the error until after the
23rd.
just finished uninstalling and reinstalling defender WITHOUT the updates.
the program ran a custom scan without any problems. then updated to the
latest version and tried the program again. yes, ran into the same error
message again.
 
This error should be fixed with the engine update
we released earlier this evening.
Click to expand...

Still getting the same error; if you need I may file in some
more details about the machine and the s/w (just let me
know); and since we're at it, I think it would be a good
idea to add to the eventlog error messages the various
version infos (program, engine, pattern) this may help
you spotting issues

HTH
 
On my machine (XP Pro SP2 32-bit) the error is generated while scanning
this
file: C:\WINDOWS\system32\wowexec.exe
Wow, indeed.
--piaqt


"Mike Treit [Msft]" wrote:
Click to expand...

My sons computer was getting an error on the same file so I ran chkdisk on
his computer and it found errors on the drive and fixed them. So I ran
another scan and it completed the scan after it fixed the drive errors. Try
it and see if it fixes your problem.
 
Just updated to:
Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1186.0
Signature Version: 1.13.1286.1

and still getting this error.
 
If your disk partition is a dynamic one, rather than basic, my understanding
is this error will continue until a future engine update, which will come
through with the normal updates. You will be unable to complete a scan
until then, but updates and real-time protection will remain fully
functional.
 
I doubt that it says "plain vanilla" when you look at the partition in Disk
Manager?

One alternative explanation is that there are errors on the disk that could
be corrected via Chkdsk. One other user has found that running chkdsk
eliminated this error on a "basic" partition.

So--right-click My Computer, choose manage.

Click on Disk Management.

See whether the partition(s?) are shown as "basic" or "dynamic."

If basic, run chkdsk.



--
 
Tomato, tomahto. Yes, it says basic. It also says healthy.
Click to expand...

My son was getting this error on his computer and we ran chkdsk on his
computer and it found errors on the drive and it fixed them. He ran another
scan and it finished the scan this time so you might want to try this and
see if it works for you.
 
Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1186.0
Signature Version: 1.14.1288.5

Still got this error.
WinDef seems to be knocked out on wowexec.exe.

May it helpful to submit the Scan ID (always changing) from system event log?

DD.20060307.1116
============
 
I'm not sure whether errors that chkdsk might correct would be reflected in
that "healthy" designation in disk manager--I'd recommend running a chkdsk.

--
 
I just installed Defender on another machine and now I get this same error
and it seems to be on either WOWEXEC or NOTEPAD that it produces the error.
Just thought you would want to know. Since it doesn't seem to be fixed with
any updates yet.

Fred Newkirk
 
In my case (same as pajama 2/26/2006) I bomb out on wowexec, I tried doing a
custom scan ignoring %system root%\system32 but it still finds and bombs on
wowexec. Uninstalling and re-installing has no effect, worked fine when first
installed then went downhill from there
 
Back
Top