Comodo Internet Security 2019 (v12.0.0.6810) – Released

[giraffe]

Just tried to access my Humax recorder. I don’t do it very often, so hadn’t realised that it just times out.
It was working prior to updating Comodo. Could there be something wrong in Network Zones? - I’ve tried a couple of things but still no luck.

[blade120]

@EricJH post:200

Did you find it in c:\Program Files(x86)\AMD AVT\Bin? It is part of AMD driver suite: AMD AVT - kdbsync.exe - Program Information .

Virus Total shows it is a clean file.

Yes. I wanted to find out why comodo shows this registry entry as unknown during the operating system scan and can somehow fix it

[ZorKas]

Here is my search on CIS v.12 on Windows 10 Pro x64 1890 Build 17763.404

• The cmdagent.exe error no longer exists in the event log with version v.12
• The procedure uses 6 processes, the startup of the PC is fast in my case
• The occupation of the memory is very correct
• Complete antiviral analysis uses maximum resources to quickly process results
  Good job the Comodo team :-TU

[Citizen_K]

@blade120 post:202

Yes. I wanted to find out why comodo shows this registry entry as unknown during the operating system scan and can somehow fix it

It’s not digitally signed and apparently kdbsync.exe is not a known executable. Hence why it is not trusted. You could submit the file to Comodo in Submit Applications Here To Be Whitelisted - 2019.

[Citizen_K]

@giraffe post:201

Just tried to access my Humax recorder. I don’t do it very often, so hadn’t realised that it just times out.
It was working prior to updating Comodo. Could there be something wrong in Network Zones? - I’ve tried a couple of things but still no luck.

Could you start a separate topic about this in the Help section?

[blade120]

@EricJH post:204

It’s not digitally signed and apparently kdbsync.exe is not a known executable. Hence why it is not trusted. You could submit the file to Comodo in Submit Applications Here To Be Whitelisted - 2019.

Thank you very much for your help. I will immediately report this file to the white list.

[Zee64]

This is the fourth time when the whole system became unresponsive and I was locked out. I couldn’t even bring up Task Manager or to restart the system. Without CIS the problem is gone. This version should have stayed in beta testing for at least one more month.

[clocks]

@Zee64 post:207

This is the fourth time when the whole system became unresponsive and I was locked out. I couldn’t even bring up Task Manager or to restart the system. Without CIS the problem is gone. This version should have stayed in beta testing for at least one more month.

I have reported the same issue. It sounds like it is a known problem.

[Citizen_K]

@Zee64 post:207

This is the fourth time when the whole system became unresponsive and I was locked out. I couldn’t even bring up Task Manager or to restart the system. Without CIS the problem is gone. This version should have stayed in beta testing for at least one more month.

The problem has surfaced during beta testing, reports have been sent and Comodo has been working on the problem.

Given there has been a lot of reworking of code happening issues may show up now it is final. When you’re using a new version of CIS with a big version number jump like that has not been released to the wider audiences kinks may happen. It’s how Comodo works and regulars like yourself know this. If this too much to stomach just wait for it to arrive at the program updater and refrain from caustic comments. Rather than that volunteer to submit a crash log:

@EricJH post:7

Comodo is interested in the hanging phenomenon. Tyey may contact you and will ask to create a full memory dump when the system hangs again. The following article describes how to let the computer crash on purpose so it will produce a memory dump file: Enable Crash on Ctrl+Scroll Lock in Windows 10 .

When the computer hangs again push the right control button and hold it and push the Scroll Lock button twice. The system will then create a BSOD an dump file.

At clocks. Did you set up your computer to provide a crash dump when the hanging happens again? If you could catch it would greatly help Comodo.

[clocks]

One of the devs asked me to DM them a config file, which I did yesterday.

[Citizen_K]

Wonderful.

Could you in anticipation on a possible request for a crash dump set up the pc as described and when it starts to freeze produce a full dump? The reason for asking is that these freezes do not occur too often so it makes sense to seize the moment when it starts to happen.

[DecimaTech]

@EricJH post:198

Since almost a week Windows Security Center will not detect CIS in a timely fashion upon boot. I will get an alert but a little later the Windows Security Center will tell everything is hunky dory. I see no obvious reason why this has changed.

Because the WDSC service is set to delayed start, which means it takes awhile before the service will actually start compared to if it was set to automatic startup. When the service is not running, WDSC will not be able to report the status of any installed 3rd party AV or firewall.

@blade120 post:202

Yes. I wanted to find out why comodo shows this registry entry as unknown during the operating system scan and can somehow fix it

There is nothing to fix as it is a new feature

“Heuristic Command-Line Analysis” and “Embedded Code Detection” for scanning and monitoring of auto-run entries.

if you notice in your screenshot the autorun entry is for cmd.exec /c start etc which is detected as an embedded code detection for cmd.exe.

@Zee64 post:207

This is the fourth time when the whole system became unresponsive and I was locked out. I couldn’t even bring up Task Manager or to restart the system. Without CIS the problem is gone. This version should have stayed in beta testing for at least one more month.

Does this happen on a system with ISE installed? If yes can you try uninstalling ISE and then monitor the system for the issue to see if it resolves it.

[Citizen_K]

@futuretech post:212

Because the WDSC service is set to delayed start, which means it takes awhile before the service will actually start compared to if it was set to automatic startup. When the service is not running, WDSC will not be able to report the status of any installed 3rd party AV or firewall.

But that does not explain why it started to happen where it would register in timely fashion before. I always assumed this type of problem to be a timing issue. No biggy, just wondering out loud.

[ZorKas]

Here are the protections of Comodo CIS v.12 induced under Windows 10 Pro 1809 latest Build 17763.404
Default installation
They are 3

[megaherz33]

Hi,
Solve the problem with the hang of the PC?

[khanyash]

After system boot, sometimes Windows report Firewall disabled. Win 10 Pro 64-bit, build version 1803.
I keep Windows Firewall disabled in Group Policy.

I have to disable Comodo Firewall and re-enable to fix it.

[Avos]

Hi Guys,
all right for me.
The only problem concerns Secure Shopping that no longer starts automatically from various browsers.
it’s normal??

[Citizen_K]

@yashkhan post:216

After system boot, sometimes Windows report Firewall disabled. Win 10 Pro 64-bit, build version 1803.
I keep Windows Firewall disabled in Group Policy.

I have to disable Comodo Firewall and re-enable to fix it.

Could you run Diagnostics and see if it can fix it?

[NDABBRU]

Have you solved the problem that viruses in USB drives even if recognized are not deleted and quarantined? But they always remain there.

Thank you!

[Xstof25]

Hello,
Since Saturday on Windows 10 1809 64 bit Outlook starts very slowly and completely blocks the PC. It takes several minutes to regain control.
By disabling Comodo (Antivirus in CIS), I have no problem. Looking at the Event Viewer I see a lot of information pointing to cavwp.exe crash (BEX64).

Do you have a solution ?

OK the comodo scan is correct. I still generate the report.
In the report I think there are the dump but I will provide them if necessary.

Result of sfc = OK.

I’ve launched scan with comodo : It’s OK