Scan Oddity

[JeremyWW]

Don't know when this happened, but over the last few days (after some update I guess), the In-Depth scan (AV V3.0) is scanning less files than it did! The scan takes half the time it did - for the wrong reasons it would seem. My System Restore area is not being scanned at all now for example, and many, many other files on my 2 drives. What's happened - Marcos, anyone from Eset...?? And no, I haven't changed any default settings for the In Depth scan...

[JeremyWW]

Oh dear...and now 'Eset Service' crashed...horribly. Had to kill the egui process off. This doesn't look too clever guys...

[krokodil_bb]

Yes, it's a known bug. If is performed scan of a same specific directory structure, then ekrn.exe process ends with error (unknown software exception 0xc00000fd) and egui.exe freezes or ends. If don't crash, repeat scan of directory system report different number of scanned files (+-2000 scanned files differ in my). I informed betasupport about this 2 weeks ago and they confirmed me this bug.

[JeremyWW]

OK, thanks for the heads up....

[JeremyWW]

I just uninstalled, cleaned out, and reinstalled (new download). Same results on an 'In-Depth' scan. Scan ends prematurely on the second hard drive, missing hundreds of files, and Sys Restore completely. No crash this time, but not good...

[JeremyWW]

Can anyone add anything to this? Or reproduce it? Basically now (as of a few days ago), NOD32 V3.0 refuses to scan my System Restore area i.e. D:\System Volume Information\_restore{.......

This is using an In Depth scan, as I always have, with ALL the default settings. Other AV's including spyware scanners such as AdAware and SUPERAntiSpyware all scan this area of the drive.

Thanks.

P.S I wasn't convinced this was the same issue as krokodil's post above...

[krokodil_bb]

I know about this crash bugs in nod3rc1 version 3.0.414.0



1st picture - service crashed, next scanning is not possible(2nd picture). if don't crash, scanning is not reliable - that is what i wrote in previous post. I send to betasupport instructions how to exactly reproduce crash, and they confirmed this bug.
3d picture - service crashed, but is immediately restarted by eset driver and all is ok. i send this to betasupport and they dont' reply.

uninstall/reinstall RC1 or update can't solve this kind of problem, so we must wait to rc2 (rc1 licence valid until 1.11.2007).

[JeremyWW]

Well, at the moment I only have an issue with NOD32 not scanning the System Volume / Restore area. Although I had the one crash, I never had the error as in your 2nd image. What is odd though, and has pi**ed me off a little, is that Beta Support (or any Eset representative here) have not replied to me at all!!

[SweX]

Hi.

I agree whit Jeremyww the Eset people or eset moderators are a bit wierd sometimes they say that we should post : Bugs, problems, etc. Here at the forum.

And if you do post about anything then you want an reply/explanation about your post/problems that's obvious.

Shape up ESET Moderators that's why you are here for, to answer and read about our problems!!!!!

"Take this as a FEEDBACK post"