Comodo Internet Security 2019 v12.2.0.6938 Beta 1 is available for testing

[megaherz33]

@prodex post:59

It’s my system.

Currently doesn’t work website ubdate, recognizer update and program update.

I deleted the entries from the host file immediately after installing the beta and registered the address in the CIS. Everything works.

[prodex]

Many thanks!

P.S.: Recognizer and program update are not working yet. Before that everything worked, the problem is new. Could change again as under 6882 when the web site update sometimes did not work. At least I hope so.
The entries in the host file I had remarked with #, but I did not enter the address in the CIS.

Problem solved: I had not entered the DNS address in CIS, which is registered in TCP / IP4.

But why did it function before? :o

[Ploget]

Any ideas on this one yet? 6914 worked in this respect, but not 6938

@Ploget post:35

I’ve now done a clean install of the Beta and everything is working well - except there is still no integration with the Security Centre

Tried all the suggestions given; turning FW or AV on and off; advanced to Basic view; reset of Security Centre etc. but no luck

The cmdagent Protected Service is not starting or running and this is what is shown

[colchis]

Hello, I was trying to install CIS 6938 but have that issue:

My cuurent CIS is:

[R2C2]

Did you uninstall the old version of comodo first?

[megaherz33]

@colchis post:64

Hello, I was trying to install CIS 6938 but have that issue:

My cuurent CIS is:

Setup Details:
In order to install online setups, please ensure you have following entries in Windows hosts (c:/windows/system32/drivers/etc/hosts) file:

178.255.86.194 download.comodo.com
178.255.86.194 www.download.comodo.com

[Metheni]

Thank you everyone for having taken your time to test and to provide us with your valuable feedback, your helpful comments are much appreciated.

Developers are working on these issues:-

1. CIS Diagnostics error

@megaherz33 post:7

Diagnostics gives an error

2. Security Centre notification- Antivirus and Firewall are turned off

@Ploget post:15

With this Beta, it’s back to the Security Centre notification that pops up the message that Antivirus and Firewall are turned off.

3. Systray icon is not visible

@EricJH post:37

This boot the tray did not show although the tray function is active. Showing the tray icoan has been intermittent with me. I’d say it’s a minor bug.

4. Allow contained application option is not working correctly.

@tachion post:44

Windows 10 Enterprise 1909 (18363.476)

This option still does not work correctly.

5. BSOD & CIS crash

ReeceN, could you please send us the link for dump files for further investigation.

@ReeceN post:28

Firewall crashed two times when in the Settings.
Will send the CIS .dmp file in PM if someone wants it.

prodex, we received a dump file from futuretech, i guess it was the one you mentioned here, if not please sent us the link for dump file.

@prodex post:31

I found it in minidump. Shall I send you the files/link?

[Dharshu]

@Ploget post:35

I’ve now done a clean install of the Beta and everything is working well - except there is still no integration with the Security Centre

Tried all the suggestions given; turning FW or AV on and off; advanced to Basic view; reset of Security Centre etc. but no luck

The cmdagent Protected Service is not starting or running and this is what is shown

Hi Ploget,

Thank you for reporting,We are checking in this.

Regards,
PD

[vitim]

@Metheni post:67

Thank you everyone for having taken your time to test and to provide us with your valuable feedback, your helpful comments are much appreciated.

Developers are working on these issues:-

1. CIS Diagnostics error
2. Security Centre notification- Antivirus and Firewall are turned off
3. Systray icon is not visible
4. Allow contained application option is not working correctly.
5. BSOD & CIS crash

ReeceN, could you please send us the link for dump files for further investigation.

prodex, we received a dump file from futuretech, i guess it was the one you mentioned here, if not please sent us the link for dump file.

sorry, i know its offtopic but i have to say it: im really glad to see this post of yours… this shows me, as a cis user, that you guys are still comminted to the development of this so beloved software. its not common to see the kind of thing going on in others companies forums… please, keep it up… continue this great approach talking to users and letting us know whats going on in dev. this is much apretiate. this is, in fact, the kind of thing that differs comodo from others… sure, the software itself too, but this, THIS post response, is the greatness in shape!!! waiting the second beta and with hype on the next cis release thats poping up to be maybe the best release ever…

[Citizen_K]

@prodex post:62

Many thanks!

P.S.: Recognizer and program update are not working yet. Before that everything worked, the problem is new. Could change again as under 6882 when the web site update sometimes did not work. At least I hope so.
The entries in the host file I had remarked with #, but I did not enter the address in the CIS.

Problem solved: I had not entered the DNS address in CIS, which is registered in TCP / IP4.

But why did it function before? :o

Hard to tell. May be DNS cache needed to be flushed after changing the hosts file. That could explain but given that time pas passed and DNS information may have been updated there is no way of telling.

When using the beta server Proxy and Update Settings you will not get updates for the AV signatures. CIS will not show an error but you won’t get those updates. Just wait one or two days and then update with the default server and see you will get AV signature updates again.

The problem with website databases was a temporary glitch. Not seeing recognizer updates when using the default server settings with the beta will give the error about not being able to update the recognizers. It’s one of those inconveniences of a beta program

[Citizen_K]

Thank you for keeping us in the loop Metheni. We really appreciate to know what Comodo has cooking. (:CLP) :■■■■

[R2C2]

Metheni - this issue identified by cruelsister and others should also be addressed as it creates an exploitable hole in CIS - https://forums.comodo.com/news-announcements-feedback-cis/comodo-internet-security-2019-v12106914-released-t124993.0.html;msg893449#msg893449

[prodex]

@EricJH post:70

Hard to tell. May be DNS cache needed to be flushed after changing the hosts file. That could explain but given that time pas passed and DNS information may have been updated there is no way of telling.

When using the beta server Proxy and Update Settings you will not get updates for the AV signatures. CIS will not show an error but you won’t get those updates. Just wait one or two days and then update with the default server and see you will get AV signature updates again.

The problem with website databases was a temporary glitch. Not seeing recognizer updates when using the default server settings with the beta will give the error about not being able to update the recognizers. It’s one of those inconveniences of a beta program

Thank you.

The problem with website (already known in 6882 and befor, I think) wasn’t a problem for me. I thought the same for updating e.g. the program.

[colchis]

Thanks for support and helping me here.

I appreciate that much.

I am newbie in Comodo world and feeling love of it. here what i saw in these my first days is that all members supporters and developers are very friendly communicably and full of responsibility.

That’s fine.

[Metheni]

@prodex post:31

Edit: I shut down the computer, turned it off completely (power switch off for about 5-7 sec), restarted and tried the same procedure with virtual desktop again. No more BSOD with my own configuration. Of course, no explanation for it or it is a correction from Microsoft, which collects the errors when the PC crashes. Is MS corrective?

Hi prodex,

Did you ever experienced the BSOD again after this statement. Could you please check your PM and verify our request.

[prodex]

No, everything is okay.

I’ve read your PM, but because everything works, I don’t change anything.

You’re doing a really good job! :-TU

[Dharshu]

@megaherz33 post:8

He blocked the class “Printing devices”, and his Canon MF-4140 MFP, then added it to the exceptions.

Hi megaherz33,

Thank you for Reporting,We are checking in it.

Regards,
PD

[megaherz33]

@Dharshu post:77

Hi megaherz33,

Thank you for Reporting,We are checking in it.

Regards,
PD

Hi,
Everything works perfectly.

[Dharshu]

@Ploget post:35

I’ve now done a clean install of the Beta and everything is working well - except there is still no integration with the Security Centre

Tried all the suggestions given; turning FW or AV on and off; advanced to Basic view; reset of Security Centre etc. but no luck

The cmdagent Protected Service is not starting or running and this is what is shown

Hi Ploget,

Kindly use the Uninstaller Tool for cleaning of your PC and Re-install the CIS latest v12.2.0.6938 Beta 1 version. Make sure that cmdboot is installed and check its version 1.0.0.466385.
Also check the version of the cmdagent.

Thanks in advance!

Regards,
PD

[Ploget]

Hi Dharshu - I’ve done that several times now, with the same result. I’ve been running it ever since with no other problems on this system, apart from that

The cmdboot details are shown . . .

@Dharshu post:79

Kindly use the Uninstaller Tool for cleaning of your PC and Re-install the CIS latest v12.2.0.6938 Beta 1 version. Make sure that cmdboot is installed and check its version 1.0.0.466385.
Also check the version of the cmdagent.