Frank H

Running multiple protection apps concurrently is a source for PIA's anyway.

i believe these temp files seems to be Bitdefender related and is not to worry about. This is not new behavior. This could happen when no updates are available, which happens so now and then

where do you get this from ?

we have 1 requirement: cloudbroker.emsisoft.com on TCP port 61614 should be open in your firewall more info: https://help.emsisoft.com/en/2317/emsisoft-cloud-console-beta/

no executable data is and can be transferred from device to ECC.

Hi Zwergenmeister Thanks for your feedback. Please note that ECC is in beta stage and we're adding new stuff and fixing things on a regular base. 1. planned 2. known and being worked on 3. data: what would you like to get from and send to a device ? german translation will be updated. VG Frank

Thanks for your feedback Pete. We have to check each time EAM starts as users can delete installed KB's. When we 'assume', because we set some tag somewhere, that the KB is installed and just start EAM, it will just stop working, as this KB is a mandatory, rendering user's system unprotected. which is a no go.

EAM performs the check at program startup, so if you won't see it the first time, you'll never see it ;=)

@Peter2150 we have just released Emsisoft Anti-Malware 2019.5.0.9476 beta which includes improvements regarding the KB4474419 check. The KB should now correctly be detected.

We’ve just released Emsisoft Anti-Malware 2019.5.0.9476 beta. You will have to enable beta updates to get this version. Minor tweaks and fixes.

my screenshot was made using EAM just as an example and sure you can use the same variables in EEC policies.

Thansk @Peter2150, we are testing a fix and will release a 2nd beta this weekend most probably.

Hello Noel, You can use environment variables in the exclusion rules. See my attached screenprint. by using these you can easily create one rule for all your user's local app data folders. example: %userprofiles%\appdata\MSteams\ will exclude all files in those folder please note that EAM env. variables contain more paths than expected, as EAM protection work on system level and not on user level This is why you see multiple paths in my example. Does this help ?

@peter2150 thanks.

@peter2150 does EAm still warn you to install that KB or is all fine now