Excuse me if the program is supposed to do that through some setting, for i must be terribly oblivious not to notice it. The problem is, i’m using Firefox dev builds. Nightly and the such, and a new update is released like 3 to 4 hours. In a few days, COMODO creates a new trusted file entry for the same files in the list, accumulating more than 50 times the same files.
Given how tedious it is to select many entries at once to clean this mess up, i’m justified to say that this little problem needs to be addressed. If my db of trusted files was broken up into pages of 50 entries, i’d have… about a hundred pages, if not more.
So yea, that’s my request. If COMODO won’t search for duplicates automatically when adding them in the list, at least allow the purge to do it.
Thanks in advance.
EDIT: Alright, if you decide to bash on me, i accept that, i was a little lazy with the search and only found it after the 8th try that the same issue has been discussed already. So… you’re free to lock this if you want, i’m sorry if i wasted your time. I just hope it gets fixed eventually. The new firefox files are automatically added in the list each time so i don’t really care about old versions and hashes, i just want to be able to keep the list clean.
I don’t believe that you would get bashed for this… mildly teased maybe, but certainly not bashed.
Anyway, as you’ve now discovered, this has been discussed at length. Actually I still don’t believe that we’re 100% sure if it is a bug or by-design. So, you may want to add your own views/opinions to this issue… a fresh view is always welcome.
If you want to lock this topic, then you are free to do so.
Excuse my attitude, i’m just accustomed to seeing moderatorss overreacting to people not doing thorough searches before posting a new node.
However, onto what i believe. While this “feature” may help with restoring an older file version and still keeping its entry in the list, the fact that there’s no automatic cleanup when the file itself is added in that list on its own without a user prompt only clutters things, and doesn’t really provide any helpful insights.
There’s no additional information about these entries, so you have nothing to compare the hashes to. This pretty much nullifies the point of keeping the old duplicates in there. Even if COMODO prompted you each time for the same file when an update occured, it would still be easier to just click the allow button and be over with, despite this being rarely the case given how automated the whole thing is.
Bug or design, it only makes the list load slower, and the purge take longer since it’s going through the same entry multiple times (or at least it looks like it’s doing that, i don’t really know :P).
Allow me to chime in here with my 2 cents, because this has been driving me bonkers.
Actually, it used to be quite simple to remove duplicates, as follows:
The new entries are always added to the bottom of the list - this is easily demonstrated. All I would do is select (check) those new entries, then click on the File Path column header to sort the list by name. Now I’d go down the list, and wherever there is a check mark, remove it, and if there is a duplicate adjacent, select THAT one, which, of course, is the old entry. After doing this for all the selected entries in the list, I hit REMOVE, and that’s it - duplicates are gone.
Now, somewhere along the way, a few releases back, it seems to me that CIS started to cache these Trusted Files entries (evidenced by the speed at which the list is populated now, compared to before). So although the above procedure should still be valid, CIS seems to get very confused about what it’s doing, and is unable to keep track of what’s what. The end result of all this is that CIS seems to be so confused here that sometimes both the OLD and a new entry re-appear.
I really would appreciate a solution to this situation, as I hate unnecessary clutter.
Personally, i don’t have this issue others have described as ‘entries not getting removed’.
However simple it may be to remove dupes though, it’s tedious, and when you have well over 50 files with 30 old entries each, clicking each individual one is just not the best approach. Unless you’re so bored and have nothing else to do for 20 minutes.
Really? Do you mean to say that when you install a new version of something, you end up with only one entry in the TF list? If so, I’d really love to know why.
Yes, it could be tedious, but it’s not too bad if done regularly, so that one doesn’t end up with too many superfluous entries. What I find MUCH more tedious, is removing unnecessary entries created when some applications are installed. Sometimes these exceed a hundred, most of which are not needed for program execution! >:(
Thanks for the suggestion, but there is no OK button on the Trusted File list. There is a CLOSE button, which I use. I know my eyesight has been deteriorating, but I believe I am seeing all there is to see. I’ll be pleased to find out that I’m missing something ??? ;).
First of all, what is the point of keeping duplicate entries? If a file is replaced by a newer version then only one file exists so it’s either trusted or not, in which case the earlier entries are redundant anyway so why not get rid of them.
Secondly, because I keep suffering from CFP.EXE using a lot of CPU after a couple of days and one suggestion that might stop this happening is to reduce the size of the trusted files, I’ve just spent about 15 minutes marking all the files I want to remove, then clicked on the Remove button and the whole thing appears to have hung up so I guess I’m going to have to start again.
It really would be useful if there was a quicker way of doing this, espcially as I found many, many MS update files in the list and you can’t even select a record at one point and scroll down and select all from there down to the next point with the shift key as you can with so many other lists. A filter would also be useful as a lot of MS files are in the same directory.
I think I may have spotted the problem with removing entries. Some of my trusted files are on a remote drive and when I try to remove just one file it can take a long time to respond after I click on Remove. I’m not sure I understand why the fact that a filename for a file on a remote drive that is being removed from a list needs to refer to the remote drive but that appears to be what is happening. I would have expected remove to simply remove the entry. Purge, yes, but Remove!