Comodo Internet Security 2019 v12.1.0.6914 Released.

Also unble to install KillSwitch and get Error 5 Access is Denied with Comodo Firewall.

Windows 10 Pro 64bit 1903. Up to date.

After some initial doubts with a couple of odd ‘errors’, I kept with it and didn’t really have any particular problems. I updated to the latest Windows KB and have really seen a vast improvement with this version since. The KB4522355 according to Microsoft fixed numerous Windows problems: Windows 10 update KB4522355 (build 18362.449) releases for version 1903 - Pureinfotech

Some of these issues will relate to CIS (and I’m sure some do) . . . it has made a remarkable change to this CIS version with Windows in the speed and smoothness in its running

Since yesterday, I’ve gone through reboots - cold starts - software installs - Temp file drive and Network swaps and several other oddball changes that would normally show up some errors in a Security software.

Nothing has appeared and it is running together with Virtual Desktop, KillSwitch, Secure Shopping just as expected. The Containment Clipboard bug is apparent, but I haven’t yet found anything else

love you!!! :slight_smile:

ill wait a few more days before going into w10 1903/09 with this new cis build. or maybe wait the next point release… but your statement brings some joy to my face :slight_smile:

edit.: just so people know, windows 10 1903 and 1909 are the same, except some 20kb enablement kb, but the cumulative updates, updates, etc., will be the same… they will all install on both windows 10 editions… so, if cis is running flawless in 1903, then it will do the same on 1909…

It’s a pity. Now: metoo!

After everything worked for 3 days my PC froze too.
First: It did not shut down, had to switch it off. Then nothing could be activated anymore - no responding. No reactions on the desktop.
I also went back to 6882.

I have exactly the same, but on Windows 10 1909 (449) x64. It turned out to be deleted only in Safe mode using a third-party uninstaller. Rollback to 6882

#metoo , I am back to 6882.

After updating with the online installer from 12.0.0.6882 to 12.1.0.6914, I have just the same issue when I try to (re-)install Comodo Cleaning Essentials on my Windows 10 Pro (ITA) 64bit 1903 build 18362.10024.
Thank you for your support!

When rating scanning reaches the file vdcss (Safe shopping), it doesn’t go any further. Full scan freezes for a long time.

Win 10 1909 (449) x64 Pro

With cis 6914 this update didn’t work on my PC with the message from Windows: is not supported, but with 6882 the update was successful.

I am having the same problem with 1903 (18362.449) x64.

Installing 6814 on 1903 was a bumpy ride but it seems stable now. I ended up installing 6814 after the recent Windows update KB4522355 and now things seem stable.

I started installing 6814 on build 18362.418. CIS would stall and freeze the system with the AV update hanging at 31,7%. I decided to give a hard reset and it rebooted. All seemed fine until it froze again. I had noticed with Resource Monitor that a crash report for cavwp.exe was being made. After that the scan continued.

I decided to install update KB4522355. I rebooted and the update was successful but CIS was stalling the system again. I did a hard reset and booted into safe mode and uninstalled CIS using the clean up tool.

I took a chance installing 6814 one more time now that I had updated Windows to build 18362.449. And now all seems fine and dandy. I am keeping fingers crossed, but so far so good.

This build is rough around the edges.

Edit: strike the above. 6814 turned out to be unstable on 1903 on my system. Like on 1809 it stalled starting of programs and would not reboot when asked. I am back on 6882.

Shouldn’t this release be pulled if it is this unstable? Perhaps more testing needs to be taken into account?

Removing 12.1.0.6914 also resulted in an error where it was unable to uninstall.

The removal tool did however seem to remove it.

For those that experienced system freezing/hanging or slowdowns, can you indicate if you elected to install the anti-virus and check for memory dumps in C:\ProgramData\Comodo\CisDumps. If you uninstalled or went back to a previous CIS version, the folder might be empty so if you can try this version again and collect the memory dumps if you experience the same issue as before. I’m pretty sure it is caused by cavwp process crashing so collecting the memory dumps from the crash will help Comodo fix the issue.

Please let me know how I can get you the dumpfile, I don’t remember.
I installed cis without cavwp but tried to open secure shopping and of course it didn’t work. Maybe that’s the reason for this dumpfile. Don’t want to make it publicly accessible. I don’t know what you can learn from it. I’ve never dealt with it before.

Upload it to a site such as Dropbox or Google Drive and then send the link via PM. You can zip it and Password protect it also, if you feel it’s necessary

Thank you!
[at]futuretech:

This will take some time, I go back to 6828 with my backup. dropbox is frozen, restore my backup, but I don’t know if it’s a bug from cis.

Edit: I didn’t go back to 6828, it wasn’t a bug of 6914!

I have also notice the situation. The configuration backuped seems cause the problem even performing an complete uninstall with the
Official Comodo Uninstaller and whole new install 6914.
6914 on Window 10 Home x64 1903 18362.449

PS. sometime the database update will start to download a whole new one (4-500MB), and it may just back to normal after stopping the process manually and clean the comodo folder programdata folder with the winapp2.ini and other compatible software.

This version “Comodo Internet Security 2019 v12.1.0.6914” is simply just a cripple bèta, pushed wild in the open;
Irresponsible and pitty when people tend to trust these releases.
I will wait for formal response from Comodo Staff and a new release.
regards, Biteater

comodo internet security 12.1.0.6914 is stable, just doesn’t complete the installation killswitch in proactive security :-TU

My PC freezes from 12.1.0.6914. You can’t do anything, even turn it off or restart PC.