Jump to content


  • Content Count

  • Joined

  • Last visited

Profile Information

  • Location
  1. Interesting as I grabbed the install from the ESET website (had to make sure I grabbed the right macOS app) and it upgraded fine over the old version (I make a back up of the settings as in the past I have had it where those were reset). I upgraded from the version before 6.10.700.0. My other question would be when was the last time you restarted (I do know that macOS 11.4 is due in the next few days).
  2. I got it sent to them. I also posted here as I think others might be having the same bug if they are trying to get to the modem internal webpage.
  3. Thanks, I usually have to wait about a week for them to respond and provide the cloud link they use (also I shared it via a cloud link in my email reply back)
  4. Just checked the speed via TheTimeMachineMechanic which pulls it from the logs and I am seeing speeds of around 0.37MB/s while ESET scans every file as it is transferred to the network drive on the network drive. I have also watched real time scanner scanning the backup drive in the Protection Status
  5. Strange I can't edit my last post to note that the logs are to big for email (just over 40MB)
  6. #00190599 I got a replication of it in the ESET log collector will see if the logs are again to big to send via email
  7. I opened a ticked almost a week ago but have not heard back, posted here to see if it was happening to anyone else also.
  8. For anyone else does HTTP protocol checking cause the modem admin page to fail for anyone else. Have to leave it unchecked if I want to view it (with it on it will partly load in about 1 in 1000 tries). Last 3 or 4 versions of Cyber Security.
  9. The path is a network volume /Volumes/.timemachine/DeviceName._afpovertcp._tcp.local./ and it is an ESET bug for the past few months where network volume exclusions are ignored. Also the backup drive is APFS I have a ticket and sent video and photos of the bug along with what ESET support asked for but have not heard back form support in almost 2 months. This ESET bug add 6 to 12+ hours to back ups 6.10.700.0 did not fix it
  10. I guess the feature is coming in a future Cybersecurity update (Windows version is out with that feature), the website I guess is updated macOS side before it is public for macOS users, and the myESET site kinda breaks when you update the key and it does not allow you to reconnect (looks like you wait till that one expires to link it back). Looks like https://help.eset.com/my_eset/en-US/add_license.html?new_device.html also was partly updated recently.
  11. ESET support has refused to help even tho I opened the ticket and sent screenshots and other things as they requested back in December, this is adding 2+ hours to back up less than .5GB. Other times developers seem to ignore what I sent completely. The back up drive is not physically connected to this Mac, it is on the local network, have reinstalled ESET completely a few times last year. macOS mounts the drive when it is time to back up. I sent ESET support screenshots of the paths being excluded and scanned object showing those paths being ignored (I think they are being ignored beca
  12. I have had that for a few years, and still no go, the back up drive is not local to the machine or plugged into it, it is on the local network (yes Network Media is not checked in Real Time Scanner yet ESET is scanning every file as it is placed in the Network drive). I also have the local snapshot path excluded and the Time Machine app and the process that does the backup, and the path to the network drive where the backups are being placed. Local to the Mac drive paths work fine, but network locations are still being scanned.
  13. I have the path for the back up in the exclusions list for a long time now and ESET realtime scanner is still scanning them (local exclusions are working), the drive I am backing up to is not local to the machine but on the network (never have had scanning of network media enabled in Real-Time protection settings), the ESET scanning them is adding 4+ hours to Time Machine back ups.
  • Create New...