Update Testing to Comodo Internet Security v12.2.2.7036 RC

[Citizen_K]

@EricJH post:52

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.

[Ploget]

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!

@EricJH post:52

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.

[Citizen_K]

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.

[Citizen_K]

@EricJH post:55

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).

[Citizen_K]

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?

[liosant]

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

[Citizen_K]

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.

[Dharshu]

@liosant post:22

download is very slowdown;
download database repeat…

Hello liosant,

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

[liosant]

@Dharshu post:60

Hello liosant,

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

it got better, but not perfect
regards!
sorry my english

[prodex]

No more bluescreen by now.

[Citizen_K]

I testing updating from 6914 to 7036 on Windows 10 1809 (17763.1098). The same is happening here. Updating without KillSwitch installed works and updating with KillSwitch installed does not work. I used a recently renewed version of my Proactive Security settings.

Because there is an issue with installing KillSwithc I “installed” it as described in:

@EricJH post:136

I took a further look into Killswitch not getting installed. I found the download folder in %temp% and from there I could not copy the files to the CIS installation folder. That was despited changing user rights to the folder and temporarily disabling HIPS and Auto Containment.

I then booted to the other hard drive that run Windows 10 1903 with CIS 6882 and I could successfully copy the files of Killswitch and CCE to the installation folder of CIS on the other hard drive.

These tests corroborate further that having KillSwithch installed prior to updating to 7036 breaks the update process.

[prodex]

When I click on ‘cleaning PC’ (cce), then ‘tools’ and there i can open ‘killswitch’.

[Citizen_K]

I put a shortcut to KillSwitch in the widget. My comment about the alternative strategy in my previous post was a workaround needed only in 6914 (I was testing the scenario updating from 6914 with KillSwitch installed).

[Citizen_K]

I had a crash of cavwp.exe being logged in two files at the same time. This installation was updated from 6914 to 7036. I am on Win 10 1809 (17763. 1098) x64.

[at] Dharshu I have uploaded the files to my one drive and sent the url by pm.

[prodex]

I had virtual desktop + secure shopping and used both intensively. open:

After closing it, I put the container back and folded. No BOSD, the reset did not take a second. Hadn’t been the case before.
The fact that my PC froze yesterday (could not close the virt.desktop) is only mentioned by the way, because I switched it off, so I have no error message. Could be more because I “overwhelmed” the PC, otherwise everything runs smoothly.

Very good work, if you consider (I am only amazed as a layman) how such extensive software is programmed and where the details (the devil is in the details) can be everywhere. One wrong “dot” and you have to find it.

Thank you for this monster work!

[Dharshu]

@EricJH post:63

I testing updating from 6914 to 7036 on Windows 10 1809 (17763.1098). The same is happening here. Updating without KillSwitch installed works and updating with KillSwitch installed does not work. I used a recently renewed version of my Proactive Security settings.

Because there is an issue with installing KillSwithc I “installed” it as described in: These tests corroborate further that having KillSwithch installed prior to updating to 7036 breaks the update process.

Hello EricJH,

Thank you for reporting.As per our dev,Could you please re-check the issue and confirm.
Have a nice day.

Kind Regards,
PD

[Dharshu]

@liosant post:61

it got better, but not perfect
regards!
sorry my english

Hello liosant,

Thank you for your response.Let me forward this issue again to the corresponding team members for completely resolve.
Have a nice day.

Kind Regards,
PD

[Dharshu]

@EricJH post:66

I had a crash of cavwp.exe being logged in two files at the same time. This installation was updated from 6914 to 7036. I am on Win 10 1809 (17763. 1098) x64.

[at] Dharshu I have uploaded the files to my one drive and sent the url by pm.

Hello EricJH,

Yes I got your dumps and I will forward that to my dev members for further investigations.
Have a nice day.

Kind Regards,
PD

[Dharshu]

@liosant post:61

it got better, but not perfect
regards!
sorry my english

Hello liosant,

I had forwarded your reply to our corresponding team member for further analysis of the issue.
Have a nice day.

Kind Regards,
PD

[Citizen_K]

@Dharshu post:68

Hello EricJH,

Thank you for reporting.As per our dev,Could you please re-check the issue and confirm.
Have a nice day.

Kind Regards,
PD

How do you mean recheck? Try updating from 6914 to 7036 with and without KillSwitch installed?

I have witnessed the behavior on installing updates coming from various versions:

@EricJH post:55

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.

@EricJH post:56

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).

@EricJH post:57

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?

@EricJH post:59

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.

@EricJH post:63

I testing updating from 6914 to 7036 on Windows 10 1809 (17763.1098). The same is happening here. Updating without KillSwitch installed works and updating with KillSwitch installed does not work. I used a recently renewed version of my Proactive Security settings.

Because there is an issue with installing KillSwithc I “installed” it as described in: These tests corroborate further that having KillSwithch installed prior to updating to 7036 breaks the update process.

There is one thing that could be worth testing and that is testing from a factory default profile. :-\