offbyone

Just rechecked the installations and rebooted one of our test systems The systems we are running with v9.0.12017 seem not to be affected by this issue. Maybe someone can shed some light on this. Cheers

We have still some customers with v9.0.12017 on Windows 2008 R2 in disconnected environments. As v9.0.12018 needs Azure Code Signing it will not work in those environments. Is there any workaround for this setup? THX

@Marcos THX for clarification.

OK I found it. It is currently running version 2099.6 from 23.11.2023.

How to find out version of configuration module? Sorry for my cluelessness on that point.

We have exactly the same problem as described here after upgrading ESET EFS from version 7 to version 9. https://forum.eset.com/topic/35590-profile-folders-stacking-up/ Is there any solution for that? THX and Regards.

OK seems that we have to do so. But this is definitively true. We checked here multiple times in parallel with two identical VMs, one with 7.3 and one with 9.1.

@Marcos We are facing a similar problem and had to find out the hard way, that performance exclusions were no longer honored by initial scans or manual scans (testing with latest 9.x releases here). This is different from version 7.3 where performance exclusions worked for all kind of scanning. Do you have a suggestion for workaround? THX.

@Marcos Yes you did. After upgrading from 7.3 to 9.0 SSL/TLS protocol filtering was activated without changing the policy.

@Marcos THX for the hint. We will check what happens after upgrading EFS and if its still disabled force it to be enabled via policy.

We are just preparing to update some old ESET EFS 7.3 to EFS 9.x. Any idea why "SSL/TLS filtering" is not enabled on ESET EFS 7.3 (Windows Server 2019) although the policy settings insists that it should? I verified that the latest policy was applied to the Windows Server. Policy Client

Just set up a test environment and made some tests here. I think we will install ESET Server Security 9.0.12017 on Windows 2008 R2. This seems to work flawlessly also without the KB. The most up to date version currently is 9.0.12018 which fails it KB is not present.

THX for pointing out. We have few customers with 2008 R2 servers in offline environment which are target to update ESET on. I will setup a test environment before.

@itman THX for fast reply.

What about Windows 10 LTSC? Windows 10 LTSC 2019 is supported till 2029 by Microsoft. It should be supported by ESET also.