Comodo Internet Security 2019 Beta (v12.0.0.6798) is now available for download.

I confirm. All of the above happens on my computer on Windows x64 1809 17763.348. Installation was clean and setup without importing configurations.

I noticed you had a different version number so I checked for Windows Updates to see if there was an update. Indeed there was and I am now also on Win 10 (1809 17763.348).

The system hang on 1809 17763.348 will be the same, eventually rolled back to CIS 6744.

no problems her on windows 1809 17763.348.

All running smoothly , very happy

So far . . . . after several clean installs and using different Configs (both imported or not)

  1. The HIPS Memory Access problem now up over 2000 log entries showing every application that’s run
  2. The delay necessary prior to Windows login still present, otherwise the ‘Firewall not turned on’ message appears
  3. Unable to remove Trusted Vendors

Can’t reproduce that however, but will be going back to 11.6778 until fixes rolled out

.dll is recognized as .dl :-X

I had it installed less than 24 hours and it was terrible - i had to reinstall CIS 11.
CIS 12 Beta keep after a while freezing my windows 10 computer and the main problem i think are HIPS - it did not help whitelisting all the windows system files…

Thank you for checking. I double checked with both the fresh and imported Proactive profiles and my finding reproduce on both configurations.

Hi Eric, Dewan, DeathCat, could you please share your exported configs?

I sent a link by pm.

Vladimir could you comment on the updated AV engine and overall performance improvements? How were they realized? Is there a change how the AV engine handles things? Were binaries codes more efficiently? Was a different compiler used?

The performance improvement also influence the UI which responds faster and lost its sluggishness. Were there changes made to the UI framework or are the improvements a result of the general improvement of performance?

How much of the stability fixes are coming from the built in reporting feature of CIS?

Thanks Shane and Comodo. So far so good. Fresh installation. Windows insider 18348 64 bit pro.

Thought cis12 will have new interface or was I just dreaming? :slight_smile:

I cannot install the Beta on Win7. (Whereas I can get it to install on Win8.1, although not straight forward.)

In Win7, I get a message that “cmdhtml.dll wasn’t properly signed. Installation aborted.”

I tried it in both a User and Admin account.

In Win8.1, I also tried to install from both a User and Admin. (Two different instances of Win8.1). In both cases, I got a message half way through the installation of the Beta saying “Present installer’s state cannot be saved to properly resume installation after restart.”

I had to reboot and run the installer again. Then it worked. (It appears that I get the message after Comodo 11 was uninstalled, but before Comodo 12 installs.)

I haven’t seen anyone else report problems during installation. So, for the record, both my Win7 and Win8.1 have been heavily trimmed using NTLite.

So it could be that my OS’s aren’t vanilla. OTOH, I haven’t had a problem installing Comodo 11 on them.

Is there a way to disable the five new JSON items in the Context Menus?

Or is this just temporary during the beta?

I have no idea how to use them.

This is temporary or when you use beta. If there is an issue on your system, mods or developers will ask for dump which you can generate using the new JSON items on context menu and pass it on to them.

Hi pimkep,

This is overinstall known issue, machine should be rebooted between 11 uninstall ans 12 install.

As reddy.shyam mentioned, this is test functionality available for BETA builds.

Hi Eric,

[i]

How much of the stability fixes are coming from the built in reporting feature of CIS[/i]
I can’t tell exact numbers, but their share is pretty tangible.

>> The performance improvement also influence the UI which responds faster and lost its sluggishness. Were there changes made to the UI framework or are the improvements a result of the general improvement of performance?

UI framework is not changed, it is the result of general performance fixes, unrecognized items handling improvement and optimization of interaction between CIS components.

Performance improvements can be divided on several branches:

  • Improvements based on fixes of issues found and reported by forum users (especially by Pixo1, Megahertz, Ploget and you) - their specific environment highlighted several hidden issues which are basically invisible on “regular” environment, but still affect performance. Mostly all of them are about communication between CIS components.

  • Improvements based on code refactoring, new C++ standard benefits

  • Optimization of unrecognized items handling (especially noticeable when widget is enabled).

As for updated engine:

>> Is there a change how the AV engine handles things?
Externally - not so much, for other CIS components it is almost the same engine. Mostly changes are under the hood: script scanner performance is significantly improved, also we’ve added support of various unpackers, etc.

>>Were binaries codes more efficiently?
Yes, we’ve integrated new C++ standard with it’s benefits, performed refactoring.
[i]

Was a different compiler used?[/i]
No.

:viva:

Its working well for me on 17763.348 Windows 10 x64 on 2 systems. I’ve not got the HIPS on (which it sounds like may be causing problems for some people). For me, it is working well.
Specifically:

  • Faster OS startup/login.
  • Faster scanning.

The UI itself at some stage could do with a tune up. Sometimes when installing large packages (e.g. Visual Studio), I disable the AV for 30 mins or 60 mins or whatever, but sometimes there’s a huge delay between selecting the disabling and the menu popping up with the choice of how long to disable (15, 30, 60 mins or permanently). Sometimes the UI lag has been 30-60 seconds. But it’s fairly random.

Overall great work though :slight_smile:

Thanks Mike.

We will put an eye on this popup.

Dev team asks users who faced the issue to create full dump when the issue is produced (for example by NotMyFault tool from sysinternals - NotMyFault - Sysinternals | Microsoft Learn) and share it with us if it is possible.