mkrupa

@JozefG We have configured a proxy (eset bridge) but the policy is only a few months old and there is no proxy password

Actually the problem got worse. Since ESET pulled back version 1.4.50 we cannot activate newly installed clients with the older version anymore. Our licence is for 320 instances and only 72 are in use now.. From the log of the client: [2023-11-29 13:17:42.629] [agent] [info] [5300] Received Activation task from Agent [2023-11-29 13:18:03.693] [licence] [error] [5300] Cannot send message "association" : 20003 [2023-11-29 13:18:03.693] [licence] [error] [5300] ecp::Result::HttpRetryAfter [2023-11-29 13:18:03.695] [licence] [error] [5300] Association Failed : result 3 resultcode 20003 [2023-11-29 13:18:03.695] [licence] [error] [5300] Activation Failed 0 : 0x00004E23 [2023-11-29 13:18:03.695] [agent] [error] [5300] Activation task has failed

We were trying to encrypt 10 new devices with version 1.4.50 yesterday via our on-prem Protect server but the product faild to activate on the clients. We had to manually uninstall this version of FDE on the clients and roll out the previous version again, which activated fine.

How can you clear the cache?

I tried right now and it is still not working here.

Does this change in spread control also apply to on-prem Eset Protect Server installations?

OS is Windows 10 Pro 22H2 on latest patches. Yes, we use ESET Bridge.

We have the same problem. Some Clients won't update the agent from 10.1.1288.0 to 10.1.1292.0 but show a green checkmark in the task,