VerwirrterUser

Thanks for your answer! We can't migrate our ERA v5 to ERA v7 because we do not have a partner or a company for that anymore. I don't have this knowledge to do this. The C:\Windows\temp was cleared and the permissions are correctly set (after a fresh installation) Kind regards,

Hello everybody, at the beginning i wanted to warn you for my bad english. Now i will start to explain my problem to you. Our company have a ESET 5 server with ESET 5 clients. Up to Windows 7 there was never problems with ESET but with Windows 10 and a major other changes that comes with Windows 10. We noticed now that we are not able to update the signature manuelly. The automatic works sometimes but not anytime. The error which occuring is "error creating the temporary file". But if we try to update from the Internet (directly from the eset servers) it works sometimes and more stable like to our server. The server is Up-To-Date and have no Windows Firewall running. The clients have Windows Firewall running and the ESET Firewall is turned off. The Firewall on the clients is allowed to talk with the server (to ESET) over the Ports 80, 443, 2221, 2222 I have to say, for the implementation in the past we had a company, but they dont care so we just quitted the contract and now we dont have any personal partner anymore. So I'm here to ask what we can do that ESET works normally on the clients again. Windows Firewall clients: TCP 80 ESET server Allow TCP 443 ESET server allow TCP 1237 ESET server allow TCP 1238 ESET server allow TCP 2221 ESET server allow TCP 2222 ESET server allow TCP 2223 ESET server allow TCP 3128 ESET server allow The way back is allowed too. Just for have all complete: ESET client version: 5.0.2272.7 (up-to-date) ESET server version: 5.3.39.0 (up-to-date) ESET server console version: 5.3.39.0 (up-to-date)