SCR

Most Valued Members
  • Content count

    277
  • Joined

  • Last visited

  • Days Won

    20

SCR last won the day on February 12

SCR had the most liked content!

About SCR

  • Rank
    N/A

Profile Information

  • Gender
    Male

Recent Profile Visitors

380 profile views
  1. I have been using Eset for quite a number of years in Interactive mode and have never had the issue you describe. My apologies, my response was to assist with a rapid response to mitigate damages caused by an operator error.
  2. The purpose of "interactive mode" is to allow "you" to decide about connections. If you feel that you have accidentally allowed any incoming or outgoing connections the easiest and fastest solution would be to edit the rule and either block, disable or delete the rule you created. If you want to stop the connection immediately right click on the Eset Icon in the system tray and select "Block all Network Traffic" until you get things sorted out remembering to once again allow network traffic once you have finished. Turning off the ability to create a rule pretty much negates the purpose of interactive mode.
  3. itman, Thanks for the link. Interesting read and a interesting site.
  4. I am not a Hybrid OS user. Simply Windows 7 Pro and Premium both x64, separate systems of course. I'm not having any issues with EIS on either system. Based on my own personal use I must disagree. While I will admit that there is a bit of an up hill learning curve if you are using anything but "Automatic" mode. I use Interactive mode on the Pro machine and Automatic on the Premium. I used both ESS and ESSP without issues as well. However both provided options that were either duplicates to programs already installed or simply not necessary for my use @cyberhash: I agree regarding "lack of experience and knowledge." However that's why Eset provides the Automatic mode. I consider the running of two AV's or duplicate real time protections a self induced issue. While I have several second opinion titles installed they are on demand only. It is unfortunately the common thought that more is better when it comes to protection when in fact it isn't.
  5. .I have EIS v10.0.390.0 On my Windows 7 x64 Pro system and a lifetime licensed user of MBAM I tried several v3 releases but because of the problems, which were many, I have removed it. I found it to be to much of a hassle for the reward of using it. I'll wait till they get the kinks out to see if it works. If it does, great. This is not to say that you may install it and be on your way. At the very least I would strongly recommend that you make an image of your drive prior to installing v3
  6. Eset has Internet Security for those that do not need the latest additions for whatever reason. Mine is that I already have those items covered with other licensed software. I prefer EIS over my two system licensed ESS which I renewed for two years last July. I could have used ESS if I wanted to on both machines but both are desk tops so anti theft was not really needed. My other system ran Eset v8 until the final EIS v10 was released. It's my wife's computer and she does not have any patience for learning the inner workings of the computer. The simpler the better as far as she is concerned. (Thank you Eset for Automatic Mode.) By the way she was not happy about the reminder either. As for me I like to tinker with the computer and have a curiosity about what's making it work, I use interactive mode . The point being I used v8 till it was my choice to update and to which version. It didn't cost me anything when I made the decision to do so. In fact from what I understand Eset has offered a rather favorable path to upgrade to ESSP. I also had the choice to use any mode I wanted learning, automatic, interactive or policy. As to clicking the button and send more money. I doubt seriously that it would cost you anything to update your licensed v8.x to a comparable v10.x. I like having choices and I believe Eset 's offerings provide those choices very well.
  7. Eset Internet Security just did a in product update to v10.0.390.0 requiring a reboot. Windows 7 Pro x64 with EIS updates set to "Pre-release" and "Update Mode" set to permit "Application update." "Ask before downloading" is not set to active. My other system, Windows 7 Premium x64 not on Pre-release updates, is still on v10.0.386.0 .. Checking Product Update advises that EIS is up to date. All this for what it's worth.
  8. I attempted to update Chrome and it showed as failed with the error "An error occurred while checking for updates: Installation failed. Please try again. (error code 7: 0x80040905 -- system level). " However, closing Chrome and reopening showed that in fact it had updated "Version 56.0.2924.76 (64-bit) Google Chrome is up to date" It seems that Chrome needs to restart to install the latest update. Windows 7 x64 - Eset Internet Security v10.0.386.0
  9. I'm one of those that if Eset says no I don't go type, just makes life easier. If Eset says there's a problem I look for alternative ways to accomplish the task. In this case a Google search brought many results for a "YouTube to MP3 conversion" without the need to download software. I went to about five of them and Eset remained happy. However, this may not be satisfactory to you.
  10. Outstanding! Thanks for the link itman
  11. Eset v10.x updated without my intervention because I have given Eset permission to do so. Eset then notified me of the upgrade requiring a reboot for it to complete the install. With regard to your friends on v8. I don't think you can update to v10.x over v8 although they should have been getting notification of the new version. I think that you have to uninstall v8 and then install v10.x manually. I'm pretty sure you can install v10.x over v9.x but it's always been my practice to do a clean install any time there is a major upgrade even if Eset could upgrade from in program.
  12. My update setting for EIS Win7 Pro x64 was and is on pre-release. However my other system, Win 7 Premium x64, is not on pre-release and it updated EIS on it's own as well a few hours later. Perhaps it's just a slow roll out.
  13. Using EIS on Windows 7 pro x64