Hello,
Does anyone know if this is normal behavior by said process and/or Comodo’s Firewall? I know what MemCompression is about, but i can’t find any info about what it means for it to try to establish a connection with those protocol & ports (see attached screenshot).
A bug in v11 and older of comodo firewall that is fixed in v12.
Nige_39
October 11, 2019, 2:57pm
#4
Hi there,
It’s still showing for me Using V12.0.0.6882
I have left it, and have not Blocked it, or allowed it.
Regards
Nigel
Dharshu
October 11, 2019, 4:22pm
#5
Hi there,
It’s still showing for me Using V12.0.0.6882
I have left it, and have not Blocked it, or allowed it.
Regards
Nigel
Hi Nigel,
kindly Check your PM and provide use the info.
Thanks,
PD
Dharshu
October 13, 2019, 8:04am
#7
Will do many thanks
Nigel
Hi Nigel,
Thanks for providing the requested logs. We will forward the logs for developers for further investigations.
Regards,
PD
iamme99
October 24, 2019, 5:55pm
#9
I saw the same thing today. I am on 12.0.0.6818.
Metheni
October 28, 2019, 3:51pm
#10
Dev team is working on the issue. As workaround please add MemCompression to Windows System Applications file group.