Thanks a lot for your concern, I’m sure if it’s related to the last update you will find a solution soon. But I think it’s a big chance since it started after the update.
Hi,
We are coming up with a hot-fix, which will fix following issues seen after v6408 release:
- RDP issue
- Repeated request for crash report submission
- Diagnostic error due to check for non-critical TCP services unavailability
We hope to place a RC on test server by this week-end and same will be live next week.
Thanks
-umesh
Hi,
When it will be hot-fix?
by mid next-week.
Thanks umesh,
It is strange, because like you wrote, those files should be locally trusted but that’s not the case.
Here are sh-1 of some unrecognized windows files (even Windows media player is among them) :
ie4uinit.exe - 959D231AAFCED977A252CF50648834BED5512ACD
inetcpl.cpl - 280E031E9B356CEE493E6F264DF791DBFE490164
wmplayer.exe - F4C8649DA809D7F5DE0F004167D026809268E989
urlmon.dll - BAF5468C699BE63B1DF8E1CF98C4D32346AC9B04
SearchIndexer.exe - 3FBB40B61E9DD56D8599DAB945ED39D05BD6DEC4
werui.dll - CE8E43B4C6B72762C777FD85D25052C61A5680E1
ieframe.dll - EB48BB5B4868AAE13FDA7B06882F8F4DFB2D6177
And for example new version of software CCleaner isn’t also locally trusted although is digitally signed by Piriform Ltd.
Piriform suffered a security breach concerning CCleaner. Piriform is currently being watched by Comodo before it will be considered to make Piriform a trusted vendor again.
I recall this case, it was ugly.
Thanks EricJH,
I know that were security problems with 32-bit version of their software and that Avast acquired them and implemented some nagging update process.Good to know reason why their software doesn’t considered trusted.
Can you perform a clean uninstall and reinstall and see they are still unrecognized?
I will try that and report.
Well, it’s a very good thing that I tried to reinstall Comodo because now I found more serious problem then windows unrecognized files.
I can’t uninstall Comodo (I have only firewall component) at all!
I tried several times, both options(reinstall and permanent uninstall) and I’m always getting the message “cannot uninstall Comodo firewall” - call some phone number…
This is now more serious, there are some problems with this new 10.0.2.6408 version (at last for me).
Can I get some help about this?
I used in the past some special Comodo uninstaller but that was long time a go, I don’t know where I can get that now?
Besides this, I can’t see any other problem for now, Comodo firewall 10.0.2.6408 generally works well and I don’t have any performance drop.
I already mentioned that I’m on Windows 7 Ultimate 64-bit and I have updated Comodo firewall through internal updater from v10.0.1.6294 to v10.0.2.6408.
You’re looking for the removal guide here which contains removal tools, you can use either one as they both work fine under Windows 7. But before you do, go to the %TEMP% folder and collect cmdinstall logs so they can see why it wasn’t uninstalling properly.
Well, I managed finally to uninstall Comodo firewall with newer removal tool (batch file) from removal guide posted here by futuretech.Older removal (for Windows 7 and lower) tool can’t be downloaded and Firefox is blocking download and flags file like dangerous content.Newer removal tool (batch file) did the job, but people should be careful with option 2 (remove Comodo folders and registry keys) because it can broke a lot of things in Windows.Option 1 (kill Comodo services so you can easily uninstall program) is enough and then you can clean up traces manually or with help of some uninstall software.
A lot of unexpected night job and effort for me. 
Fortunately I’m always using backup from Paragon and that saved the day.
So, problem with uninstall process is that you can’t kill Comodo services and processes (at last me with Windows 7 and updated Comodo firewall 10.0.2.6408) and that’s why I couldn’t uninstall Comodo firewall 10.0.2.6408.Task manager didn’t help, reboot in safe mode also.
I attached one of many cmdinstall logs so you can investigate what was wrong.
Back to the problem with unrecognized Windows files after Windows update.With clean install of 10.0.2.6408 version of Comodo firewall everything is OK.Those Windows files are locally marked as trusted.But will be interesting to see what will happen when Windows December Tuesday update arrive?
Seems that like many times before, problems arise with updating Comodo firewall through internal updater.And those problems are different for different users, have many forms.They are present sometimes and sometimes not.I’m using Comodo since version 2 (bare network firewall), so I used pretty much to that.
I hope that one day these problems with updating through internal updater will be vanquished forever. 
Guys, I’m in the panic!
Yesterday CIS decided not to work anymore! In practice, testing with EICAR detect alerts for a fraction of a second and does not block any files. Tonight I will try to make a clean uninstall and hope everything will resume working.
Any better ideas?
Somebody help me, please?
Did you perform a clean uninstall and reinstall yet like you said yet? Or are you still experiencing the issue after doing so? Check CisDumps folder in ProgramData\Comodo directory as it sounds like the alerts UI and or cmdagent process is crashing.
Hello and thanks.
I had uninstalled and installed again and imported my configuration. He worked well for only a little while, and after that, the problems had come. However, I did not uninstall it according to the removal guide. Do I have to try it again?
Did you get an error message from CIS or Windows indicating something was not working?
The AV does not monitor the download of files. Did you try to execute Eicar when testing?
No message. I tried to run it and find it sandbox
Then it is contained. That is expected behavior. There is no need to worry.