![]() ![]() Update / Profiles / My Profile (only profile listed) / Product Updates / Update Mode / Auto Update (though this is for =v9.0) (policy enabled but setting unselected) and also enabled the following setting. ![]() ![]() Update / Product Updates / Auto Updates (=>v9.0). I also had Product Updates enabled in a separate ESET Endpoint for Windows policy applied to all computers. This was on my 'internal' ESET PROTECT CLOUD service where up until yesterday I did still have the Common Features auto update policy. Marcos, I've had a couple more computers auto upgrade to v11 today even though I changed the policy. Due to the nature of problem, performing any diagnostics in real time is nearly impossible, so any additional help will be appreciated. If someone else is facing this issue or have suggestions, please let me know. I've tried disabling HIPS Advanced memory scanner but to no avail. CPU usage is normal, seems a memory lock issue to us, specifically during startup scan. So far we've started working with our local reseller to collect logs and relevant information. Disabling Realtime protection or uninstalling Endpoint Protection is the only way to let users work normally. Sometimes all gets back to normal after waiting, sometimes we have to physically power cycle. I searched for similar recent posts in Forum but couldn't find anything similar so I assume it's related with our locale (IT) or our specific endpoint policies.Ībout 2% of our managed endpoints are becoming unresponsive after boot: apps freeze, cannot interact with Explorer elements, network traffic stops, whole Windows GUI becomes unusable for several minutes. This is a first hint of a problem we're facing since Endpoint ver.0 has been rolled out on our Windows 10 customers. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |