Jump to content


Most Valued Members
  • Content Count

  • Joined

  • Last visited

  • Days Won


peteyt last won the day on February 21 2018

peteyt had the most liked content!


Profile Information

  • Location

Recent Profile Visitors

3,409 profile views
  1. A few things to try. Firstly if your on 12 update to 13. Did you try to switch to learning mode for the firewall instead of interactive mode? It does sound like something is corrupt. You could try to repair eset by going to add/remove programs ans find eset. When you try to uninstal there should be a repair option that could repair and fix the issue. You could always back up your settings if needs be but there is a risk the issue could get copied. You could also uninstall if the repair does not help and reinstall from scratch. If a full uninstall does not help you may need to uninstall with esets uninstall tool in safe mode available from https://support.eset.com/en/uninstall-eset-manually-using-the-eset-uninstaller-tool although hopefully the repair will work and avoid all this
  2. According to a similar post 2051 2005 means incorrect password. On the other hand, 2051 2000 means that you are trying to associate the device with the name that already exists in your device list.
  3. Just to add windows 7 will end most support in january
  4. Am I correct in assuming non home products can download and then install updates on an offline device or have I read that wrong somewhere
  5. The problem with the system cleaner for me is it does not give enough information. It is handy that it tells you a setting has been changed but would be handier if it was able to tell you what actual setting so you could decide better. However like Marcos has said it is okay to ignore if you do not suspect malare which to me it sounds like you are safe. I also think it would be handy if after you could see the spefic settings you could add them into some kind of exception. When this feature first came out I gave it a try. Problem was I saw nothing to indicate what got changed and it did not make any logs and there is no way to undo it. Again it might be a good feature for people trying to clean up the leftover mess from an infection but thats it as there is for me not enough info and could actually cause issues with people chaging stuff and not knowing what
  6. Weird I'm not 100 percent but looks like there might be a problem which has caused it to get removed. Possibly uninstalling and reinstalling or running the uninstall and choosing repair. You can always try to backup any custom settings before you do this.
  7. I'd recommend downloading the live installer for the latest. I see you had problems with a previous version. Version 13 seems stable but if you have any issues you can report them. Problem is by downgrading it avoids the problem being fixed. Newer versions also often have better improvements and newer technologies
  8. Welcome to the forum. Glad to see a fellow horror fan to. I love slasher and giallo films
  9. Just a quick question. I presume excluding utorrent would mean torrents and their files downloaded via utorrent would still be scanned
  10. I actually posted this in the wrong post. My question was actually in regards to the zerocrypt ransomware from this post my question is as the user in the video didn't show us him downloading the ransomware does that mean it was probably detected and he conveniently did not show this part.
  11. Just wanted to share a video by the same user for another AV where the developer of that AV has claimed the user has been using bad practises including in the video secretly whitelisting one of the malicious files It shows that you have to take tests with a pinch of salt
  12. Can I just confirm - would the user in the video have had to disable eset to download this ransomware. Obviously it shows in the video eset didn't detect once run but I presume eset would have blocked it from actually being downloaded in the first place?
  13. As mentioned this ransomware with a few others get in by brute force. Is RDP enabled. What tends to happen is they use brute force to figure out the login to get in. They then attempt to disable eset which is made much easier if eset doesn't have a password set for its settings. You can set it so that RDP has a set number of login attempts before locking a user out. Also it's important to make sure you are fully patched with windows updates
  14. You don't need to do that yet. Have you tried to disable the mentioned eset settings and test it?
  • Create New...