G
Guest
On my machine (XP Pro SP2 32-bit) the error is generated while scanning this
file: C:\WINDOWS\system32\wowexec.exe
Wow, indeed.
--piaqt
file: C:\WINDOWS\system32\wowexec.exe
Wow, indeed.
--piaqt
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
G
Guest
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.
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.
O
ObiWan
This error should be fixed with the engine update
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
we released earlier this evening.
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
G
Gary
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:
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.
M
Mike Treit [Msft]
Thanks to everyone who has reported this - it is under investigation.
-Mike
-Mike
G
Guest
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.
Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1186.0
Signature Version: 1.13.1286.1
and still getting this error.
B
Bill Sanderson
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.
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.
G
Guest
My disk is plain vanilla. So why these errors?
B
Bill Sanderson
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.
--
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.
--
G
Guest
Tomato, tomahto. Yes, it says basic. It also says healthy.
G
Gary
Tomato, tomahto. Yes, it says basic. It also says healthy.
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.
G
Guest
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
============
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
============
B
Bill Sanderson
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.
--
that "healthy" designation in disk manager--I'd recommend running a chkdsk.
--
G
Guest
are we all still having the error message? no activity on the board for 5
days now...
days now...
G
Guest
Sky's still blue.
--
--piaqt
--
--piaqt
pajama said:are we all still having the error message? no activity on the board for 5
days now...
G
Guest
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
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
G
Guest
I ran chkdsk. Still getting that error. BTW: what is wowexec?
G
Guest
wowexec stands for "windows on windows" - it is used for running 16 bit
prrograms
prrograms
B
Bill Sanderson
As far as I know--no fix for this has been issued yet.
--
--
G
Guest
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
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
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.