Ewido 4.0 beta bug

I reboot about twice a week - mostly to cure Windows irregularities.

And yes, a manual scan does show on the status page.

Does this mean that other beta users do not experience this problem, and daily (or nightly) scheduled scans run successfully?

 

My schedule runs nicely however it doesn't warn you it's away to start and the only indication I get is a bit of hard disk noise.
Open the ewido GUI and click the scanner tab and you'll see if it's scanning. Although the status screen will show you the date of the last scan.

 

I just tried myself a scheduled scan: no problem

Gerard

 

and after the scheduled time:

 

OK, this has been confirmed to be a known bug in this separate topic. (The Catch Up option must be checked in order to run the scheduled scans).

 

Ok when the ewido gaurd (guard.exe) is "active" and if you try to end it using task manager you can't, but if you make the "resident shield" (ewido guard) set to "inactive" via the ewido main interface you can use task manager and end ewido's guard (guard.exe) successfully..is this normal?

 

I have no problems using task amanger with the shield enabled.

 

I have no problems with the Task Manager either.

 

I didn't look through all the pages of this, but has anyone else had problems where it doesn't SAY that it found anything?

To test out my theory (origianlly that it wouldnt get FF cookies):

1. Went to screensaver.com
2. Ran Ewido 3.5
3. Found some thing but didn't remove
4. Scaned Cookies.txt w. Ewido 4
5. Didn't say it found anything
6. Scanned again w. Ewido 3.5; didn't find anything.

Sadly, I needed some spyware for this so I went to screensaver.com, it actually seemed very safe! The worst thing I had was 5 tracking cookies... Then again, I didn't download anything...

 

When I am running Ewido Beta 4 active, it makes oasrv.exe from Online Armor AV+ jump cpu usage from 0 to about 13 + every few seconds. I am guessing they don't like each other or somehow ewido is running through OA's oasrv.exe. As stated before, Ewido beta 4 has been pointed out to cause mid cpu usage every few seconds but while running along side OA AV+, it is oasrv.exe doing the cpu jumping. I have tried this a lot of times to see if it was ewido and yes it was. When ewido guard is off, then the GUI is closed, oasrv.exe goes back to normal cpu usage of 0.

dja2k

 

edit. Sorry wrong alert. I fixed that bug myself.

 

Is this bug? I founded it newest version of ewido:

hxxp://img232.imageshack.us/img232/4126/nimetn4pu.jpg

 

bug reappeared...
notice the commas

 

This is ewido 4.0.0.172?

BR

 

I'll check this.

BR

 

The same problem also appearing while scanning...

 

What locale are you using.

 

I use the greek local and my windows XP sp2 are the greek version.
Nevertheless the last public beta version was working fine in my system.