Memory Scan

Same problem here and i have windows xp home edition sp2

 

im using xp home with sp2 and all the patches i submited a bug report through the gui and put this thread into it so hopefully somebody at eset will read and fix this

 

I'm using XP Home SP2. In fact I didn't get this error (NOD32 2.7) on my old laptop (Windows 2000) where I temporarily installed NOD32 2.7 just to test this.
So, it's confirmed that this is happening on XP machines with ESS/EAV 3.0 but can somebody confirm this memory error with NOD32 2.7 (scheduled scan) or am I only one?

 

It must be in both ess and the av because im just running the av and its doing it

 

Hello,

I can confirm that I experience the problem described as well. When I checkthe operation memory as one of scan targets in the scan setup it is not subsequently saved to the scan profile. Replicated on w2k/xp.

However, it seems to me the problem with memory opening is not related to the one mentioned above.

 

Good. Will they have it fixed in the next build release?

 

I am using Windows XP Pro with SP2 (fully patched) and have this problem just fyi. Though I am using ESS.

 

Two possibilities - either in future build or via the automatic updates. Don't worry , it was officially confirmed ESET are aware of it

 

good deal im glad to be of help and hope it gets fixed =)

 

What is strange that it sometimes disappears - do you notice this ?

 

Scan Log
Version of virus signature database: 2682 (20071123)
Date: 23/11/2007 Time: 21:45:34
Scanned disks, folders and files: Operating memory
Number of scanned objects: 449
Number of threats found: 0
Time of completion: 21:45:37 Total scanning time: 3 sec (00:00:03)

NOD32 V3.0.563
XP Home
Comodo Firewall V3 with Defense +

Scan Log
Version of virus signature database: 2682 (20071123)
Date: 23/11/2007 Time: 21:48:02
Scanned disks, folders and files: Operating memory;Operating memory
${Memory} - error opening [4]
Number of scanned objects: 449
Number of threats found: 0
Time of completion: 21:48:05 Total scanning time: 3 sec (00:00:03)
Notes:
[4] Object cannot be opened. It may be in use by another application or operating system.

 

Hopefully they wil lfix this bug in an up coming build they are aware of it and replicated it so i guess ill just give it a little time