Compatibility Issue: CIS & Authentec TrueSuite (crash/freeze) on WIN7 64

Comodo Internet Security - CIS Resolved/Outdated Issues - CIS
1

Hi all,

I want to post a bug which I tried to fix several times but it seems to be related to a general compatibility issue between CIS (5.3.X) and “Authentec TrueSuite (4.00.258)”.

Environment:

Windows 7, 64-Bit (fully patched)
CIS 5.3.181415.1237
Authentec TrueSuite 4.00.258 (device here: AES 2550 finger print reader)

Problem:

CIS and TrueSuite run fine as long as TrueSuite is used for the finger print detection. TrueSuite allows use of Authetec’s finger print reader for logon (e.g. UAC, logged system etc.) and often -but not always- the system completely crashes (not even BSOD; freezing immediately). This happens on different installations/systems installed as mentioned above (clean install). I am not sure but it doesn’t seem to be a problem on 32-Bit Windows 7 systems (didn’t crash there so far).

Note: Since a couple of weeks TrueSuite now comes with Windows Update (driver update)

Using TrueSuite produces numerous alerts inside the Defense-Log (screenshot attached). Not all produce a crash but let’s say 1 out of 10 (re)produce it.

I didn’t find any solution. I already tried many suggestions from the forum and the application is marked as a “secure” one.

I would appreciate your help because I would like to keep on using your great product!

Thanks in advance
■■■■■

[attachment deleted by admin]

2

We would very much appreciate it if you would edit your first post to create an issue report in line with the bug forum guidelines and format here. You can copy and paste the format from this topic.

To understand the reasons why we ask you to follow these guidelines please see below.

WHY WE ASK YOU TO FOLLOW THESE GUIDELINES
Bugs/issues can be impossible or very time consuming to fix if developers don’t have enough information to reproduce them. Since CIS is free, development time is limited. So if you want your issue fixed, please use the format below to describe it.

To avoid clutter, issues not described in the format below your post will not be moved to the ‘moderator verified’ issues topic. This means that the developers may not look at it.

Best wishes and many thanks in anticipation

Dennis

3

Thanks to “Valentin N” from COMODO who helped me to find a solution or workaraound:

  • Take a look at your running tasks and you will see that there are 2 …ClientAppLogonEXE.EXE
  • Stop the 64-bit version from starting when the system boots (e.g. using something like CCleaner)

That’s it. The other 32 bit EXE will do the job and no more warnings are fired inside the D+ log.

Thanks to Valentin & regards

■■■■■

4

We really would very much appreciate it if you would edit your first post to create an issue report in line with the bug forum guidelines and format. You can copy and paste the format from this topic.

Thank you

Dennis

5

Unfortunately we do need this issue to be reported in the full right format, and with all the information we have asked for, if we are to forward it to verified issues.

For the moment I am going to move it to the Orphaned/Resolved child board. If you do edit your post to create a complete issue report in standard format, and PM an active mod, we will of course consider moving it to verified reports.

The devs only look at the Orphaned/Resolved board if they have time, so please do edit the post and PM an active mod if you want it fixed.

Dennis