Jump to content

wpsullivan

Members
  • Content Count

    7
  • Joined

  • Last visited

Profile Information

  • Location
    USA

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Actually, looking at the log file, I just discovered that ESET Internet Security said that it found four infected files and deleted two of them. The two it deleted were Log C:\Windows\WinSxS\amd64_microsoft-windows-security-spp-tools_31bf3856ad364e35_10.0.18362.1_none_17f6b61a3c58cd26\slmgr.vbs - VBS/TrojanDownloader.Banload.FA trojan - cleaned by deleting [1] Log C:\Windows\WinSxS\wow64_microsoft-windows-security-spp-tools_31bf3856ad364e35_10.0.18362.1_none_224b606c70b98f21\slmgr.vbs - VBS/TrojanDownloader.Banload.FA trojan - cleaned by deleting [1] The log note says tha
  2. I forgot to mention: I had MSRT work specifically on the SysWOW64 folder, but it's not clear that it worked. The results screen didn't show the SysWOW path, and I didn't see the slmgr.vbs file in the results, so it's not at all clear that MSRT was able to see the file or do anything with it.
  3. ESET Internet Security is reporting that it's found VBS/TrojanDownloader.Banload.FA with the following message: Log C:\Windows\SysWOW64\slmgr.vbs - VBS/TrojanDownloader.Banload.FA trojan - error while cleaning Microsoft Windows Malicious Software Removal Tool doesn't seem to be able to see the trojan, even though it's been able to detect Banload since 2015, as far as I've been able to determine. That said, it looks like ESET might have interrupted MSRT; it's hard to tell. I tried to get ESET to delete the file, since that seemed to be the only available option once cleaning had
  4. I was actually just coming to see if I could edit this post. Right after I did wrote this, I stumbled across a very recent ESET support page that dealt with this: https://support.eset.com/en/disable-ssl-filtering-in-eset-windows-products The disable/re-enable SSL filtering part of the post worked for my setup. That said ... there do seem to have been a number of users with this issue this year. ESET should have their certificate added to Mozilla's certificate store so that Firefox could recognize it. That would make life simpler for everyone.
  5. I just purchased ESET Internet Security to go with a new system. Everything was fine before I actually installed ESET. I was able to use Firefox and reach websites and they displayed correctly. After installing ESET, the majority of websites were unreachable. Most were blocked by Firefox as insecure, and the few that weren't completely blocked were broken; their CSS wasn't loading at all. The issue seems to be that ESET somehow takes over the security certificate function. Every single website that was completely blocked was shown as having a certificate issued by ESET SSL FILTER CA,
×
×
  • Create New...