What is this stopservicelauncher.exe file that was downloaded today?
A few minutes ago the latest Windows 10 October update was installed. And Comodo 11 stoped working. Again.
So again back to 10.
This is really sad, since the problems of Comodo 11 seem to be forever.
Stopped working how? Maybe try a clean install, funny others have no issue with this version and the Windows 10 October update.
I did a clean install, after the widget didn’t show. But a clean install didn’t help. By “Stop” i mean the widget didn’t load at all.
So back to 10, that seems to work fine.
Those old errors came back:
bad_module_info, έκδοση 0.0.0.0
and a new:
can’t start " CmdAgentProt"
Please upload it to Virus Total and post the url to the report here.
That file was also updated/uploaded for Comodo 10.
Avira is no longer flagging it as a malware nor does any of the other scanners at this time. It’s pretty much safe to assume it was a false positive detection.
Just wanted to say that am using Win 10 1709 with Comodo 11.0.0.6710 all is good. I upgrade from the old version of Comodo 11.0.0.6606. This is after I installed Win 10 1709.
I’m using 11.0.0.6606, is the live update on? I got an update message today, clicked OK, the dialog finished but nothing changed, still version 11.0.0.6606.
Thanks for replying.
And you’re right. I just rebooted to see what would happen this time. And comodo installed the updates without problems this time and no Avira adware warning popup, hooray. Also MBAE was updated I notice, but that one is apparently crashing my browser (Opera) without any warning now, ugh. That happened as I was typing this replymessage here.
How was this AV false positive fixed by the way? Do they fix it manually as people report it or comes trough via automatic feedback report from their software?
Hello team,
I’m going to uninstall build 6606 for the new one 6710 in some minutes.
Is there any information about the issue with cmdagent.exe taking randomly 25% cpu usage ?
(25% on my system, maybe not the same usage on other systems people use).
Okay so if something is going wrong, I’ll try to give back infos as clear as possible.
And as I don’t see any reason why it would go wrong (because I noticed the evolution of this version 11, and I never had any issue by updating the Firewall, what was not the case as It was the time of version 5, So that’s the reason why I never used anymore the updated method anymore. And I started to try it again with this version 11 and there’s nothing to compare with the old version 5 that caused me so much troubles by updating it).
So, (why I talk about that ? do we care ? well not really).
I’m on the way to reinstall this new build.
If I do not login here again after 1 month, so you can put me in the list "lost one after 6710 install.
Merry Christmas and happy new year (in case).
ailef.
I assume it has been reported to Avira as a possible false positive by a concerned netizen.
It’s not fixed in this build but the fix is in the pipeline.
Hi All,
Stopservicelauncher.exe is related to Comodo dragon browser to run with CIS.
It was a false-positive from Avira and it was fixed.
Sorry for the inconvenience.
Kind Regards,
PremJK
I’m on 6710 and got an Update message - update to what?
Hi Pixo1,
Thanks for reporting. We will look into it.
Kind Regards,
PremJK
Hi Giraffe,
You can always check what is updated from CIS Task logs.
Kind Regards,
PremJK
Thanks - it’s showing Binary Update from 6710 to 6710!