Jump to content

TomFace

Most Valued Members
  • Posts

    1,720
  • Joined

  • Last visited

  • Days Won

    78

Posts posted by TomFace

  1. 23 minutes ago, esset said:

    Strange. It seems I'm currently at version 11.2.49.0

    I did not do a manual product upgrade for as far as I know.I didn't have the issue mentioned in the first post in this thread.

    Has this been 'fixed' somehow ?

    If you had pre-release updates enabled that's probably how you got 11.2.49.0 if you did not manually pursue it.

    As far as v12 is concerned, it will be released when ESET deems it ready. No one has a firm date for v12.

    If you wish to go back to an older ESET version see https://support.eset.com/kb2885/

  2. Just an FYI...I just updated to EIS 11.2.49.0 via the suggested method https://support.eset.com/kb2476/

    As my ESET security settings are password protected, I had to enter my password. The only issue was that as I had changed my EIS password a couple times, when uninstalling the existing (old) version, the uninstall (via Win 7 control panel>programs) did NOT:unsure: recognize the latest password. Rather, I had to enter the original password. Luckily I keep a PW log.

    Next I'll see if the scheduled in-depth scan reviews all the files it should....or will it be the same as it was with the previous update....see https://forum.eset.com/topic/15011-incomplete-in-depth-scan/

     

     

  3. 15 minutes ago, Bummer Man said:

    The weird thing is, that now that I reinstalled ESET and did a full scan, it found one potentially unwanted program, which was, if I'm not mistaken;

    Microsoft Compatibility Telemetry.

    Oh, the Irony.

    That almost sounds like some of their updates that advocated telemetry.

    Here is the link concerning Microsoft Compatibility Telemetry https://support.microsoft.com/en-us/search?query=Microsoft Compatibility Telemetry

    I prize my privacy...don't want/need another spy.:ph34r:

    Take care.

  4. I'm glad your issues have subsided. As far as I know, an MBAM lifetime license does not end should you uninstall it...as I have one (and SCR I believe has one as well) and have NOT had any issues (uninstalling and re-installing) as I have tried (again and again) to run MBAM (v3) with EIS. It does not work for me (for they do not play well together since MBAM v3). So I will NOT run MBAM...paid or free.

    I hope your software conflict lull last a long time, but with the combination you are using I think it will arise again.

    Just my opinion, it's only a matter of time.

    Good luck.:)

  5. 43 minutes ago, txhawkeye said:

    I've been away for a several days and haven't been online.

    How do I proceed from here?  I don't know if Eset monitors these forums.  Do I need to submit a bug report?  If so, how?

    Thanks in advance.

    If you need to open a trouble ticket, if you are North America see https://www.eset.com/us/support/contact/s3/?seg=home

    If you are in other parts of the globe, you should probably contact the ESET office in your country  https://www.eset.com/int/about/contact/ or your local  distributor/reseller.

  6. 1 hour ago, Legaleagle89 said:

    Thanks for the help.

    I've tried uninstalling from the control panel but can't locate the "ESET application" there.

    I might need to uninstall manually. Any easy step-by-step way of doing this?

    If the standard method isn't working, you can do a manual uninstall using the ESET uninstaller tool > see https://support.eset.com/kb2289/

    the same link is also under troubleshooting in https://support.eset.com/kb2788/?_ref=zap

  7. Should the OP decide to totally remove MBAM, here's a link to their MBAM Clean Removal Process 2.x.

    The OP should read the instructions completely as the tool will remove ALL MBAM data (including license information).

    https://forums.malwarebytes.com/topic/146017-mbam-clean-removal-process-2x/

    As far as a 2nd opinion on-demand scanner is concerned (should one be desired), I use HitmanPro, not HitmanPro.Alert. The enhanced HitmanPro.Alert (just like MBAM v3) causes (me) issues when using ESET.

    But again, it is the users call. This is not meant to be (or construed as) an A vs. B vs. C comparison, an endorsement or slam of any particular product or brand and what works for one user may not work for another.

  8. I used to use MBAM alongside ESS (now EIS) without any trouble what-so-ever for years (Win 7 x64 machine). That was until MBAM v3 came out (which MBAM is touting as an A/V program replacement).

    I have tried to use them together many times without success as there were always issues when MBAM was introduced. So even though I have a lifetime MBAM license, in its current state, I cannot/will not use it.   

    I agree with Marcos as to the exclusions/uninstall for testing. Then you may need to choose one over the other.

  9. Update 6.28.18 11:46EDT...apparently my results may have something to do with using my (new) VPN. I don't understand as I am in the USA and the VPN server I use is also in the USA. I am still learning about VPNs.^_^

    I just re-ran ERAR and noticed that the internet was showing "inactive" at the beginning. Once I turned my VPN off, and tried ERAR again, I then got internet "active" and was also asked if I wanted to send the previous report to ESET Live Grid...which I did do.  I may have missed the "inactive" alert previously as I am pretty sure I had my VPN on.

    Anyone have any thoughts on this? And is ERAR still a relative download? And what about the "warnings" that were indicated to me at the conclusion of running ELC? Should I be concerned and open a ticket up:unsure:?

    Any input would be appreciated.:)

  10. I just complete a run of ERARemover and it came back clean, however it showed a message about submitting a report to ESET which I have never seen before. It did not give me an option to do so at the time (in it's window).

    So how should I proceed? Sorry I do not have a screen shot and was not able to reproduce it with subsequent ERAR runs. I did do a log collection (using ALL with ELC).

  11. 1 hour ago, Shane said:

    Perhaps I can give some insight into this.

    @TomFace Occasionally, the Security Center service can take some time to initialize after a reboot (I've noticed it can take slightly longer after updates). I've personally seen this range from 30 seconds up to nearly 15 minutes. As long as the service isn't running, we are are in the "waiting to register state". This is why despite how many times you may restart, you will still see this issue, as each reboot means the service will have to start again. That is also why occasionally after reboots (relating to your 1 out of 10 mention).

    There is also the other scenario, in which case I can see from the initial poster's image, that we are in the process of updating. Once the update is done, and as long as the security center service is running, registration should be fine and the message should disappear.

    If the issue is still occurring with the two above scenarios out of the way, I suggest putting in a ticket so we developers can take a look at it.

    Thank you Shane for the information. It is appreciated. At this time it's only a minor (on occasion) inconvenience and I will be monitoring it.

    I do make a habit of checking Windows (in this case 7) Security Center to be sure all is well. 

    Thanks again & best regards.

    Tom

     

    P.S....welcome to the Forum!;)

     

     

  12. On 5/22/2018 at 4:57 PM, Wesky149 said:

    I have to ask for that how many people or users can use only one of those products that are made for mobiles (Android phone version)? I'm talking about the normal home use. Because I am owner of one of those products and I wish to be it possible for these products.

    Hello Wesky149. Take a look at this https://support.eset.com/kb2393/#question2 ...in particular,  #2.

    Hope that helps.

  13. 11 minutes ago, nexon said:

    From where you know about new version 11.2?

    Some of it may be speculation....some of it may be fact. It all goes through official channels.

    It is against forum rules to announce releases...see #17 https://forum.eset.com/topic/76-rules-of-the-eset-security-forum/

    ESET will release information when it is ready (no sooner...no later). ;) Granted we are talking about beta testing here, if you've signed up to participate in that, you should see it here (or perhaps get an e-mail). I'm not sure as I do not do A or B testing anymore.

     

×
×
  • Create New...