Process [cmdagent.exe], memory block, is infected with Win32:FakeVimes-B [Trj].

[MostlyHarmless]

Kissbaby, I still receive the process [cmdagent.exe], memory block, Win32:FakeVimes-B [Trj], 'high severity' threat notification whenever I complete any scan which includes a high-sensitivity memory check.
I'm satisfied that Win32:FakeVimes-B [Trj] is merely a fragment of the actual virus which Comodo loads into memory as part of a legitimate process. It's irritating to see it flagged with every Avast! scan, but I can live with it.

[Pondus]

It's irritating to see it flagged with every Avast! scan, but I can live with it.

so why dont you remove the "scan memory" from your custom scan setting ?

or use the default quick / full scan with default setting....

[MostlyHarmless]

It's irritating to see it flagged with every Avast! scan, but I can live with it.

so why dont you remove the "scan memory" from your custom scan setting ?

or use the default quick / full scan with default setting....

Why would I want to lessen the chance of detecting other possible threats?

[Pondus]

Why would I want to lessen the chance of detecting other possible threats?

you wont.....the avast guys have been playing with malware since 1988....they know how this works

So trust the default settings

[Seany007]

Kissbaby, I still receive the process [cmdagent.exe], memory block, Win32:FakeVimes-B [Trj], 'high severity' threat notification whenever I complete any scan which includes a high-sensitivity memory check.
I'm satisfied that Win32:FakeVimes-B [Trj] is merely a fragment of the actual virus which Comodo loads into memory as part of a legitimate process. It's irritating to see it flagged with every Avast! scan, but I can live with it.

I have same thing here... Time to time... Strange...

[CraigB]

Kissbaby, I still receive the process [cmdagent.exe], memory block, Win32:FakeVimes-B [Trj], 'high severity' threat notification whenever I complete any scan which includes a high-sensitivity memory check.
I'm satisfied that Win32:FakeVimes-B [Trj] is merely a fragment of the actual virus which Comodo loads into memory as part of a legitimate process. It's irritating to see it flagged with every Avast! scan, but I can live with it.

I have same thing here... Time to time... Strange...

Best to do as Pondus has suggested and remove the scan memory from your custom scan or use the default quick and full scan's.

[true indian]

u are having outdated comodo...

update comodo...the latest version is 5.9 see my signature.

that should fix that

[DavidR]

Kissbaby, I still receive the process [cmdagent.exe], memory block, Win32:FakeVimes-B [Trj], 'high severity' threat notification whenever I complete any scan which includes a high-sensitivity memory check.
I'm satisfied that Win32:FakeVimes-B [Trj] is merely a fragment of the actual virus which Comodo loads into memory as part of a legitimate process. It's irritating to see it flagged with every Avast! scan, but I can live with it.

I have same thing here... Time to time... Strange...

Please don't post in multiple topics about the same thing, it just duplicates the efforts of those trying to help. I have replied in your other topic also.

[giogio]

Simply add an exclusion

You can set the exclusion (e.g. for the particular scan you created) as follows:
*PROCESS\*\cmdagent.exe
- then the Comodo process won't be scanned at all.

[Saulius]

Hey that's a good idea Giogio, set exclusions to to memory scans from always detecting things that are harmless but that it regular flags.

I just 'caught' one of those Win32:FakeVimes-B [Trj] heavy alerts in AVG, I figured it was harmless but since it's been a while since I discovered anything I could delete I did so and later checked that AVG is OK, which I keep for backup manual AV scanning, mkay.

[Pondus]

Hey that's a good idea Giogio, set exclusions to to memory scans from always detecting things that are harmless but that it regular flags.

would it not be smarter to not use the memory scan...but default scan settings

which I keep for backup manual AV scanning, mkay.

running multiple AV can/will create all kind of windows errors and false positive detections

Read reply from quietman7
http://www.bleepingcomputer.com/forums/topic186533.html