nasaeed

All the workstations experiencing the issue are on a plethora... including the newest 6.6 version. Additionally, we have thousands of workstations and we would have to schedule each upgrade with each client. This isn't a feasible solution to the issue.

Update on my end, a few more have randomly trickled in today. But nowhere near the influx of before. It's so odd that it's inconsistent and random.

I'll be keeping my fingers crossed. My experiences have all been rather... mixed.

Also, derp. This issue has been going on so long I forgot you had shown examples of how your exclusions were set up.

That's great. I have a ticket open with them too and this was the answer I got from an escalated tech. If you get more help, I'm dying to know what's going on.

The amount of instances trigerring have decreased drastically for me without any actions being taken. From ESET I've only heard the following: "We recommend adding an exclusion for the specific file path that the threat detection is occurring at and include the threat name in the following format. @NAME=Win32/PSWTool.ProductKey.D@TYPE=ApplicUnsaf If this is unable to help with the issues that you are encountering please contact us at the information listed below." I'm not entirely sure how to accomplish this. We already have the exclusion set up so I'm unsure how to set it up with said format.

Hi mwhalenhtc, I'm experiencing the exact same issue. We use Connectwise/Labtech as well and this is only happening for four of our clients. All four clients were recently upgraded from v 5 or so to 6.6. I've ensured the global policy that we use that also whitelists all the necessary LT related folders/executables are showing on the workstations. The odd thing is it's not happening for every workstation for those companies, it's almost sporadic. It started mid last week for us. I've opened a ticket with ESET as well and I've been told to run the log collector as well, but it's been tricky as I have to schedule with the client first. Do you have any updates?