Update Testing to Comodo Internet Security v12.2.2.7036 RC

Thanks, Eric! I left the modification ON for the time being - no errors on program updates checking. :slight_smile:

Hello EricJH,

Thank you for reporting.
I had forwarded your logs to my developing team members for further investigations.
Have a nice day!

Kind Regards,
PD

Hello EricJH,

Thank you for your request.I added them in our feature requesting list and also forwarded your request to my PM for further implementations.
Have a nice day!

Kind Regards,
PD

Hello liosant,

I have forwarded this issue to the corresponding team members for further investigations and they are checking in it.
Have a nice day!

Kind Regards,
PD

I ran the update from 6914 to 7036 successfully and as described on Windows 10 x64 (17763.1098). :-TU

DNS:
156.154.70.22
156.154.71.22
CONNECTION NOT ESTABILSH
Region: Brazil - águas lindas de goiás

NOTE: comodo web installer add 156.154.70.22 and 156.154.71.22

===================================================

comodo secure shopping not ask acess address configured, but normal if open browsers direct with comodo secure shopping

Hi

I had version 12.1.6914 on a computer.
Win 7 32Bits
I modified the Hosts file.
The update to Comodo Internet Security v12.2.2.7036 is not done. The program tells me that I am up to date.

Did you get the message saying an update is available or try running the updater? If so did CIS tell the update failed and stored a report?

I didn’t receive a message saying there was an update available. I forced the update from the program.
CIS is not reporting any errors.

Could you post your hosts file to see if it is set up correctly?

Yes

Your HOSTS file setting is ok.

I did a test trying to update from 6818 to this build on Windows 10 1909 (18363.752) but it failed. I have added the beta server to Proxy and Host settings using my custom Proactive Security profile.

CIS 6818 downloaded the files and then gave an error: “0x80070002 - The system cannot find the file specified.” when checking View Logs (see attached image). I tried emptying :\ProgramData\Comodo\Cis\Quarantine\Temp\TempFiles folder but that didn’t help nor did changing to the default Proactive Security or Internet Security profiles.

The same is happening with 6870.

Maybe a shot in the dark, but have you changed the Environmental Variables by any chance? I’ve come across that before if I remember correctly with Secure Shopping as I had the Temp Files pointed to a RAM Drive - which it didn’t like at all!

I didn’t change environment variables like redirecting temp, appdata and document folders to another drive. The only frivolity is that CIS is installed in Program Files\Internet\COMODO\COMODO Internet Security.

Odd thing is the update worked when updating from 6882 to 7036. The only that may be different between updating 6818 and 6870 and 6882 is that with 6882 I had not downloaded KillSwitch before updating but that’s a wild stab.

I did some more testing. I tried updating from 6870 to 7036. It failed with KillSwitch installed and would work without KillSwitch installed (if memory serves me right).

I did another round of testing updating from 6882 to 7036. It failed with KillSwitch installed and worked without KillSwitch installed prior to updating.

My findings lead me to believe that on my system having KillSwitch installed prior to running the program update the update will fail. I have witnessed it with 6870 and 6882. For 6818 I assume it was KillSwitch keeping form updating successfully.

I am on Windows 10 x64 1909 (18363.752) I have been using my own variation of Proactive Security throughout those tests. I have newly set it up approx a week ago so there is no dirt from a previous installations.

Are there others also witnessing this?

update is normal, but download database antivirus slowdown :-TU

I did an update test on WIndows 10 1809 (17763.1098) x64 going from 6818 to 7036. It failed with KillSwithch installed and worked witout KillSwitch installed prior to the update. That further corroborates KillSwitch gets in the way of updating.

Hello liosant,

The issue has been fixed so could you please check and confirm that.