Yeah, I had to do those 200+ Windows updates again, filtering out the Win 10 update related ones. So much for my evening plans… Is there a write up on dealing with the network issue somewhere for next time?
Yeah, PSI shows Comodo on my machine with the lower number. Hopefully, it will be worked out as last time.
So, is there a way to bring in the application and path exclusion settings from a backup, or does it have to be done one by one manually? Thanks,
I am considering adding it to Most Effective Way to Reinstall/Update CIS to Avoid/Fix Problems
Yeah, PSI shows Comodo on my machine with the lower number. Hopefully, it will be worked out as last time.I hope the issue gets reported and Secunia will fix it. Convenient as these type of programs are they may sometimes get it wrong. In that case trust what the individual program reports.
So, is there a way to bring in the application and path exclusion settings from a backup, or does it have to be done one by one manually? Thanks,You can always [url=https://help.comodo.com/topic-72-1-623-7727-Importing-Exporting-and-Managing-Personal-Configurations.html]export a configuration[/url] and import it later.
I happen to be having the same problem between the version showing between Secunia and Comodo. Even though under “about”, Comodo shows the newest version 8.2.0.4792, I did notice that Comodo has this file below stored in the recognizer folder of the program:
recognizer_v8.2.0.4674.dll
So maybe Secunia is picking up the version number from there?
The way to tell what’s bothering Secunia is to click on the entry and choose details. On mine, it’s consistently shown cis.exe as the file at issue. And sure enough, cis.exe’s properties show it as 4674. I posted the issue on Secunia’s PSI forum a week ago and sent them an email last night. Three others there have also reported seeing the issue (two mistakenly posted under the top geekbuddy thread). The good news is that apparently(!) CIS is up to date.
Hi - Well I kind of thought it was okay. I guess it is more of a Secunia problem.
I was playing around with a new update checker called SUMO Lite. Interestingly, it found a load of other outdated stuff on my system.
Lookslike PSI’s Comodo issue won’t get fixed until Comodo updates binaries since Secunia staff doesn’t read forums nor read emails and parent company (Flexera Software) handles only paying customers issues.
when i use secunia it tells me my firewall is in need of “critical” update.
after i update, it still tells me i need the same update.
[attachment deleted by admin]
I have merged your topic with an already existing topic about this problem.
It has been reported with Secunia and it is up to them to fix. In case of doubt trust CIS to tell if it is up to date or not.
Cuser, I merged your post with this topic. Please give Secunia some time. It’s been reported recently; approximately a week ago.
The moderator at PSI forums says they don’t read the forums any more but do read emails. There is nothing apparent in the email process from the writer’s side that filters pay vs. nonpaying users, so we’ll see.
I sent email (their info-address since I doubt their customer support handles free version stuff) to Secunia ~2 weeks ago but no reply and PSI has gotten only minor updates since 3.0 release (same with corporate version) so no fix is somewhat obvious resolution.
True or an example of assumptions without foundation? You assume 1) Secunia/Flexera responds personally, 2) the problem is worth an out of cycle update, and/or that 3) the problem is PSI and not Comodo, or not one that Secunia or Comodo will eventually resolve and thus worth waiting out. I prefer patience, to see what everyone is going to do or not do.
Feels like facts since I sent email to Secunia years ago asking chance to change PSI 3.0’s installation folder (reason why I stayed in 2.0) and so far no change and I doubt its that difficult to code (since they had it in 2.0) so fixing CIS-issue seems minor aka not worth to make new build until next version (whenever it’ll be made). Error is by both Comodo’s and Secunia/Flexera’s, 1st uses old binaries and 2nd checks binaries instead program version.
It is hard to judge that from our perspective. They may have made a big overhaul of the program’s structure making it a less obvious change or they have judged it as a minor bug putting at the bottom region of the priority list. I must admit it annoys me also they are no providing the option to change the installation folder.
so fixing CIS-issue seems minor aka not worth to make new build until next version (whenever it'll be made). Error is by both Comodo's and Secunia/Flexera's, 1st uses old binaries and 2nd checks binaries instead program version.This has been reported recently. A bug needs to go through various steps of testing, reproduction, prioritizing, fixing the code, entering the fixed code in test tracks... etc. In short it takes time and a glass orb to really know what cooking or not cooking.
The flaws in your logic is shown now, as per the screenshot Secunia apparently changed the way it is classifying Comodo, at least for now.
[attachment deleted by admin]
yea secunia 3.0 suddenly regocnized cis as proper version w/o psi getting update (unless psi did silent update which would be very bad thing). dunno about 2.0 but my guess is that it shows cis outdated.
Sorry for necroing this but apparently Secunia 3.0 has autoupdater since it had installed several services and 1 of those was related to autoupdating.