Jump to content


Most Valued Members
  • Content count

  • Joined

  • Last visited

  • Days Won


SCR last won the day on April 14

SCR had the most liked content!


Profile Information

  • Gender
  • Location

Recent Profile Visitors

1,642 profile views
  1. The easiest way to determine when Eset updates and when it tries , at least for me, is shown below. It's found by clicking "update" from the home screen Updates can also be checked in the log files under "Events" Do you by any chance run full screen programs? I ask because I don't think Eset will notify you on full screen. If you've already been through all this please ignore. Just a guess on my part.
  2. You may get a better answer by contacting the wjst x software author. Here is a link to their support page: https://physics.princeton.edu/pulsar/k1jt/support.html
  3. @Marcos, Thanks for the information.
  4. I think this post states the issues the OP is having: https://forum.eset.com/topic/16163-how-to-eis-112490/
  5. I believe this is an ongoing discussion in another thread. You may find some information here: https://forum.eset.com/topic/16132-eset-internet-security-not-wotking-on-windows-insider-17713/
  6. Well said and completely agree. My post reflects my experience and should be taken as such along with the above from TomFace. As with any software your experience may be just fine. However, I will endorse and recommend Eset products to anyone that asks as they have served me well and have kept my systems safe and clean for many years.
  7. Like TomFace I also have a life time license with MBAM and can not, will not, use it. Most all my issues developed after v3.x was released and are described by the OP. I tried subsequent releases of MBAM but still had to many problems on my otherwise smooth running Windows 7 x64 Pro machine and my Windows 7 x64 Premium machine. I have an aversion to setting exclusions for anything in EIS. (Formerly ESS). However, having said that I did give the exclusions described by COStark26 a go. I also set exclusions in MBAM for EIS. While the problems were less pronounced I still had unacceptable issues both constant and intermittent. With MBAM not running and using it as a secondary scanner only issues still presented themselves simply because it was installed. After I completely removed the MBAM install with their clean tool and did a clean EIS install I haven't had any issues on either machine. MBAM provides some protections already in EIS. Given the issues MBAM has had in the past, the resources used by MBAM along with the never ending issues introduced with updates to the program I decided to go with my resource lean, reliable, tried and true install of EIS. It should be noted that I did not remove EIS to try MBAM as the only protection install. Simply put I don't trust MBAM to protect my systems nor do I want to waste my time with their development issues. My only reason for having MBAM installed initially was for a second opinion scanner. Back in the v1.x days it worked perfectly and I purchased my life time license to support the program. In v2.x some problems developed but were manageable. When v3.x was released it all went down hill immediately for me. The only way the OP will know for sure is to remove MBAM completely. Do a fresh install of the chosen Eset product and see if the issues are resolved. If the problems are resolved then the OP can remove Eset and try using a clean install of MBAM to insure there are no problem. I can't help feeling that there will be issues with MBAM only, but as I said I never tried for the reasons stated. As TomFace has said the OP is more then likely going to have to pick one or the other for a trouble free OS
  8. I'm just guessing, it's probably because the public beta has not been released.
  9. Just in case Eset should consider this. I request that it be add it to a Premium type version and leave the Eset Internet Security version in it's present light weight state. It's hard to beat the protection and ease of use at under, right now, 55 MB of RAM and 0% CPU. That way if people want the additional tools they can support it by purchasing the "Super Premium" version at an additional cost. I have no interest in more bells and whistles. All I want Eset to do is protect my systems and it does that exceptionally well right now.
  10. I wouldn't have thought so as ESET ormally advise a clean install once the final release comes out. It could have changed though. It may work but I have found that the best practice is to do a clean install of the final release. Some changes between the last beta and final may cause some issues. I have every intention of doing that when the time comes. I'm not online all the time and I didn't want a surprise of non working protection system when I boot up. Eset will more then likely have a final release out by the expiration date or extend the expiration date as needed.
  11. It may have been a good idea to have a final release available before warning users that their protection was going to end and provide a link to v9 which is not Eset Internet Security. Just an opinion. On Edit: I entered my license key for v9.x and Eset registered it. No more warning.
  12. I have no doubt it will work until then. Seems that Eset got a bit ahead of itself by having the warning show up with a link back to a page containing v9 and nothing about "Eset Internet Security" at all let alone v10x.
  13. Yeah it is but as far as I know a final out of beta has not been released. There is the possibility that I am missing some news here.
  14. I received a warning from my install of Eset that the beta period is ending in 13 days and the protection of my system will end. I renewed last July but I have been beta testing since prior to the renewal. Should I enter the license information? If not, what should I do? Thanks.
  15. Eset Internet Security updated to v10.0.171.0 this morning. No issues or problems so far.