Secure shopping issue

Problem Whith Secure shoping says have another computer conected
Can you reproduce the problem & if so how reliably?:
Yes if i open secure shoping comodo alert me another computer are conected
?
If you can, exact steps to reproduce. If not, exactly what you did & what happened:
1:? Open main interface
2:? Go to secure shopping
3:?
One or two sentences explaining what actually happened:
?
I recibe a alert who says another computer on my network can see what i doing
One or two sentences explaining what you expected to happen:
?
I dont want to have another computer on my network spying me. I dont want this alert because i know not have another computer in my network the only computer in my network is that
If a software compatibility problem have you tried the advice to make programs work with CIS?:
?
I do not understand i have zemana antilogger premium, malwarebytes free and adguard desktop and shadow defender . I know they not are incompatible
Any software except CIS/OS involved? If so - name, & exact version:
I dont think because CIS dont sent me alert . As i say
I have
Zemana antilogger 2.70.204.118
Adguard 6.1.298.1564
MBAM 3.0.5.1299
Shadow defender1.4.0.648
Any other information, eg your guess at the cause, how you tried to fix it etc:
?
i have administrator account i try go fix it stoping network activity and disconecting modem

B. YOUR SETUP
Exact CIS version & configuration:
?
10.0.0.6086
Modules enabled & level. D+/HIPS, Autosandbox/BBlocker, Firewall, & AV:
?
“Proactive configuration” default seeting in proactive seetings
Have you made any other changes to the default config? (egs here.):
?
I put heuristic in maxmium level and put scan memory when windows start
Have you updated (without uninstall) from CIS 5, 6 or 7?:
?
Clean install
if so, have you tried a a a clean reinstall - if not please do?:
?
yes
Have you imported a config from a previous version of CIS:
?
if so, have you tried a standard config - if not please do:
I use default seetings
?
OS version, SP, 32/64 bit, UAC setting, account type, V.Machine used:
?
Windows 10 aniversary update
Other security/s’box software a) currently installed b) installed since OS, including initial trial security software included with system:
a=? b=?
Adguard, Zemana antilogger and mbam
C. ATTACH REQUIRED FILES (delete this section (section C) after attaching required files)
Always attach the diagnostics file (instructions on how to do this provided here) and the KillSwitch Process List (instructions on how to do that provided here) and put the resulting file in a zip file. Both should then be attached to your post.
Note that additional information may be requested by the processing Moderator.

Is that all you need?

Could you kindly try with a different application? Does it happen all the time?

Hi Guys, Alberto,

Thank you very much for the bug report. As I have explained via pm, we use heuristic way to detect remote control, false positives might happen. Applications such as antiloggers can cause such case . We will analyse the applications you stated in your bug report and get back to you.

For your information

Kind Regards
Buket

I hope it helps and you tell me what are the solution

Hi Alberto,

We need one more information from your side. We need to get the registry (HKEY_LOCAL_MACHINE\Software\ComodoGroup\CSB\remote) information when remote connection protection is triggered by unknown application.

Please kindly check and let us know .

Thank you very much in advance

Kind Regards
Buket

They registry key information is located under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ComodoGroup\CSS\remote.

Yes thanks very much for your feedback Alberto

Just FYI, the conflict is most likely with ad blocking software to judge by other feedback in the announcement post.

If you are willing to uninstall that, reboot and re-try, you may find the problem has disappeared, and that would give Comodo useful information.

Kind regards

Mouse

I have Zemana Antilogger Pro as realtime protection with CIS 10…

I disabled Zemana and that warning disappeared :-TU
There must a conflict between these 2, it is not a bug on my end.

OK with the antilogging then… interesting

Seems to be an incompatibility with another security software so not really a bug. Moving to resolved.