Jump to content


  • Content Count

  • Joined

  • Last visited

Profile Information

  • Location

Recent Profile Visitors

1,201 profile views
  1. Surely investment in protection is more important than the visual appearance of Eset. How often do you open the Eset console. 99% of the time its hidden and works in the background. Unlike apps that are used daily that would benefit from the Dark/Light mode, I cannot see the point in having that option with a background service interface.
  2. I think it unfair to blame Eset when you are not using their communications systems correctly. Being a long standing user doesn’t give you more rights contacting support than a user the bought the software last week. All tech companies have ticketing systems for a reason and if you fail to use these correctly and don’t like the outcome that is not an issue for Eset. As for the technical issues you mentioned, this is clearly a lack of knowledge and understanding about the products you are using.
  3. The Eset article refers specifically to Windows Backup failing and not a result of 3rd party applications. If Windows Backup is installed then Eset should handle the exclusions. The role is only likely to be installed if it’s going to be used.
  4. But bdedit will identify the volumes or as per the BackupAssist article above, the registry hivelist. Surely this can be checked on install and the exclusions added. This article explains how to check the volume number so what’s the difference for an automated exclusion list. https://support.eset.com/en/kb6121-windows-backup-failing-error-message
  5. Having just started doing bare metal recovery using BackupAssist and in particular a Hyper-V and Hyper-V host there are a number of additional exclusion required to allow the backup to complete. Eset have a KB about the additional exclusions but wondering why they cannot be included as part of the standard list of Exclusions for Server file security.
  6. The Windows version of Eset V7 onwards I believe, now includes Ransomware protection as standard but I don't see the same protection for MAC's. Given that ransomware has been around for MAC's for a while and a new variant called EvilQuest has now hit the scene, which is a particularly nasty piece of work. It encrypts, installs a keylogger and a reverse shell, I'm surprised there is no apparent protection from the MAC Eset Endpoint AntiVirus.
  7. Sadly this could be a harsh lesson. Even with Windows shadow copies turned on, most ransomware will delete these shadow copies so this is by no means a guarantee to recover your data. You need to backup to an external device on a regular basis and get in to the habit of doing it. Windows 10 has an integrated backup tool, so make use of it. If you are not using Windows 10, just manually copy files to a USB drive to a dated folder so you can recover files at any point. Installing Antivirus after the event will not recover your files as the damage has already been done. You need to prevent, not a
  8. Linux is a much improved OS and can easily be used in a similar way to Windows. You generally only need command (CLI) functions for admin tasks or where a GUI does not exist. There are many flavours of Linux. You could easily install a distro in a VM such as Virtual Box on your Windows 7 machine to get the feel for it. Just bear in mind that the performance will not be great unless your host PC is of a decent spec, i.e. plenty of RAM and a good CPU. You can allocate varying resources to the VM. Alternatively set up a dual boot on your PC with a Linux partition and give it a go.
  9. Of course Eset will support Windows 7 for the foreseeable future. But Microsoft are not beyond 2020. Its your choice, stay safe by upgrading to Windows 10, or don’t. You cannot rely on Eset to protect you computer if Microsoft are not supporting the OS. Eset can only do so much.
  10. Why do you deem it necessary to have more than one AV product installed and active. Eset is more than capable of identifying malware. Running 2 active AV’s in the same PC is asking for trouble. If you are concerned about malware then you will need to dump Windows 7 come Jan 2020 and move to Windows 10 any way. Windows 7 will not be patched or updated after this date.
  11. Eset Endpoint Protection for MAC V6.7.876 is now reporting CleanMyMacX as a rogue application. Been using both for a number of years, but recently this has occurred. I have added CleanMyMac to the exclusions and also informed the developers MacPaw of this issue. Hopefully it will be resolved soon.
  12. I would attach the logs, but they a 2gb in size. After reenabling to recreate the error, the problem now persists and I cannot collect email again. Problem only occurred after re-enabling protocol filtering for the purposes of generating the logs. Now wish I had left it well alone as it was working.
  13. It appears that disabling IMAP protocol filtering and then re-enabling it causes the problem to go away. As the problem now appears fixed, not sure if the logs will show anything.
  14. We have 10 PC's all running the lates version of Eset NOD32 7.1.2053. 9 PC's are behaving themselves, but one refuses to sync IMAP folders throwing an error. Eventually I disabled Email protocol filtering for this PC and IMAP sync started. I cannot understand how 90% of the installs work without a hitch but 1 machines decides not to play ball. Re-enabling the protocol seems to have fixed the issue and sync continues to work.
  15. As a reseller the exact same thing happened to me. When I asked the same question of my account manager I was told the customer is informed of the reseller and whom they should contact but they can choose to ignore that information and renew themselves online. I was told that this was to protect the customer if a reseller has gone out of business. Thankfully it was only a small customer and they could be reassigned to me, but there is nothing to stop them doing the same thing again. As far as I’m concerned this should not be allowed to happen. How do Eset know the effort that we may have put i
  • Create New...