howardagoldberg gave kudos to Marcos in Release 13.2.15 before official announcement
As far as I know, it's a rule of thumb that vendors publish changelogs with the release which also happened this time. In the course of testing a new version, changes may not be final and may still occur to the final version.
howardagoldberg gave kudos to joloriquelme in Release 13.2.15 before official announcement
Microsoft releases every month updates to the Office 365 suite and posts changelog here:
It does SEVERAL hours after the updates are available. You can check next week (patch tuesday).
Many other Software vendors do the same.
Please calm down and move on.
howardagoldberg gave kudos to Nightowl in Release 13.2.15 before official announcement
You are just angry at something that you can't change , all companies do the same , they release an update and then they give the change notes after a while , or go meet Microsoft , they won't tell you what changed. or say hello to Steam
I don't represent ESET , and I don't work for them , but a delay of a bit or few hours after being posted in their download page and after that to their forum , it doesn't mean anything bad , they have posted it they didn't hide them , It's just a matter of a little bit of time delaying the upgrade so you can read the notes and after than initiate your upgrade or delay it for next version.
howardagoldberg gave kudos to Walt in Android 10: Interesting Issue with Location, Permissions, and WiFi identification
Thanks! I had the same issue with a Pixel XL after upgrading to Android 10. Giving ESET Location always permission, and toggling wi-fi off and on cleared it up.
howardagoldberg gave kudos to somewheretodisappear in Android 10: Interesting Issue with Location, Permissions, and WiFi identification
I was having the same issue on a Pixel 2 after the Android 10 update. Permissions were set to Always. Disconnect/reconnect to home WiFi fixed the error.
howardagoldberg gave kudos to MikeO3 in Android 10: Interesting Issue with Location, Permissions, and WiFi identification
Thanks for you help and quick response.
1. Yes, it is Always.
2. Yes, WPA2 personal (this is my home network WiFi)
3. Disconnect & reconnect WiFi worked.
Thank you for your suggestions as it appears to be resolved now after an scan and reviewing the audit summary.
howardagoldberg gave kudos to itman in HTTPS Monitoring
Interesting article. I checked the environment variables for FireFox; I don't use Chrome, and Eset does not use or need to use this baloney.
Both Avast and Kaspersky were having issues with use of their root CA certificates in Chrome a while back to decrypt SSL/TLS traffic. Appears this is Avast's solution to the problem and a very insecure one at that.
howardagoldberg gave kudos to itman in ESET issue with Sandboxie - Persistent holding of registry keys
My cleaner module ver. is currently 1195 dated 6/10. I could have swore that it had been previously updated to 1198.
Check what ver. your cleaner module is. If its not 1198, you will have to switch to pre-release updates to get it.
howardagoldberg gave kudos to TomasP in 64-bit to 32-bit
We are indeed in the process of switching from 32-bit modules to 64-bit modules.
The 64-bit module are being tested and will be released via an update soon, so currently the app runs 32-bit modules, but there is full compatibility and full protection even on 64-bit systems and thus nothing to worry about.
Now why you saw "64-bit" in the about screen earlier - this was simply a bug, which instead of the modules showed the bit-ness of the system. We fixed the bug in the latest release and now it correctly shows the bit-ness of the modules.