BUGREPORT: CFP3 X32 bit and SuperAntiSpyware

When SuperAntiSpyware checks for program updates (which it does when it starts and every 8 hour) it greates a file in the temp folder… (SSupdate.exe) (and if the file allready is there, it gets replaced by a new file)

Now the problem is now that CFP3 adds SSupdate.exe as a new application, so i have to allow SSupdate.exe every single time…

(i have also writed something about it here, but didnt find a way to fix it: https://forums.comodo.com/help_for_v3/cfp3_and_superantispyware-t14990.0.html)

(and i can see there also is some other files that gets added more then once)

[attachment deleted by admin]

Hi oOeagleOo

It looks like the new version does not read the rules with a ‘’~" in it. Replace these rules with full path and see if that helps.

John

Hallo oOeagleOo
You got also duplicated entries for cmdagent this is really strange so maibe is a compatibility issue.
Please post a gmer report too.

It didnt help… and in the applications, if i use “add–> select → browse–>my computer” it looks like my computer is empty.

  1. CPU (32 bit or 64 bit)
  2. Operating System information (including Service Pack Version)
  3. Actively-running security and utility applications
  4. Specific symptoms of the bug, and steps you can take to reproduce it.
  5. Specific steps you have taken to try to resolve it.
  6. If you pc reboots or you have a BSOD post in BSODs: Please add your minidump files here

1: 32 bit
2: Windows XP media center (service pack 2) (version 2002, dont know if that information helps)
3: SuperAntiSpyware Pro, Avira Antivir Personal (utility applications.??)
4: Dont know what information i can give here…
5: edited the rules for the applications.

and i think i need a little guide for Gmer.

If its not this, i need help with Gmer

[attachment deleted by admin]

The GMER report seem ok to me.
This may be an issue related to avira or SuperAntiSpyware.

I guess I’m going to search previous bugreports to find any common denominator.

No news. A similiar issues was reported by testers using AVG.

will it get fixed??