Jump to content

cyberhash

Most Valued Members
  • Posts

    728
  • Joined

  • Last visited

  • Days Won

    30

Posts posted by cyberhash

  1. Has this problem sorted itself out ?? Looking at the TV guide using ESS from within the UK with no issues at all.

    Marcos replied to another similar issue with NOD32 blocking sites and if you have an OLD V9 installer, then it can cause issues with sites after a major update.

    If your issue still persists, might be worth downloading the newest v9 download and installing that one (if you dont already have it). hxxp://www.eset.co.uk/Download/Software/Product/EAVH

  2.  

    As long as Eset firewall is running properly, you can turn off windows firewall.

    I wonder how it came to be that Windows Firewall is even on. I suspect there is a bug in Eset Smart Security for not turning it off. I think maybe Window Firewall became enabled when I disabled Eset Firewall from the tray icon, and then reenabled Eset Firewall from the tray icon. When I turned Eset Firewall back on again I assume Eset should have turned Windows Firewall back off.

     

    Just looking at another post you have made about the GUI taking a long time to load as well since upgrading to v9.

    Might actually be a good idea to uninstall v9 normally via add/remove programs , then run the eset uninstall tool per the guide on this page. hxxp://support.eset.com/kb2289/?locale=en_US. You need to run windows in safe mode for the tool to work properly.

    Remove any remnants of v8 or v9 that are listed using the tool

    Once you have done that, then re install v9 again. This will probably cure all your problems at once :)

  3. I think Microsoft learned their lesson over the years where people took the "Device Updates" that were showing as available and got "Burned" as ken1943 worded it.

    So they took away the possibility of people rendering a system unusable with a "Dubious Hardware Update" and moved it into a troubleshooting section within windows 10, where it is much safer for the less technically minded to "Break" what is already working.

    This troubleshooting "Box" is where ESS is getting its information from and can not only be misleading as to hardware updates, but could also take people back to the older windows update problems that previous versions of windows had.

    Everybody "Should" go directly to the website of the hardware manufacturer for driver downloads for "Any" hardware, that is running under "Any" version of windows.

    Even dedicated applications like "Driver Booster" get it wrong and offer to overwrite non-whql drivers, with older whql approved drivers.

    Like you, i believe that only "Critical" updates should be listed within ESS. Showing hardware updates is not a bug as i worded it earlier, but wandering into realms that can cause more problems than it is curing.



     

  4. Maybe this was the case for you both where the updates were actually available and needed installed. This was not the case for me and there is clearly a bug.

    I update my chipset drivers from the downloads available from Intel , which are currently on V10.1.1.14 . The updates ESET were displaying are the default chipset drivers that were built into the release build of windows 10. Version 10.0.10586 to be precise.

    And all my other drivers i update manually from the manufacturer/s too.

    When i used the update feature within ESS , i was prompted that the drivers it was trying to overwrite were OLDER than the ones i currently had on my system.

    Like i said, there is a bug somewhere. Looks like ESS is advising me to install WHQL drivers over versions that are not yet WHQL tested.

    And from the 2 times this has appeared on my system, a reboot or closing the window cleared it.

    Maybe its ESET's policy to use/list only WHQL listed drivers, but there will be millions of users around the world that use drivers newer than versions that have still to pass WHQL.

    This may not have been the case for you heyyahblah & planet , and im not saying either of you are wrong.






     

  5. Thanks.  That link is what I'm talking about as well. I understand that ESS merely notifies and this seems to be a Windows 10 issue, but it's clearly getting that information from somewhere.  It just seems like Windows 10 is being totally unhelpful. Why bother reporting it if you can't direct the user to the exact driver?

    Carl, i know what you are talking about. This has happened to me twice over the past 2 months or so. It shows there are things like "chipset drivers" and other non critical updates available in eset notifications and when you go to windows update there is none available.

    Either reboot or ignore it, it will dissapear ;) . I don't know where this information is being pulled from either but its some sort of weird bug.

    post-933-0-88476300-1459264759_thumb.png

  6. I note that most issues mentioned seem to be connected to the firewall of ESS. Well, why not go with NOD32 + Win OS Firewall or some other 3'rd party firewall - if the firewall in ESS causes too much problems for certain users.

     

    I use the Firewall in Policy-based mode myself cause I want control, but I have not noticed any issues when I have used Automatic mode either.

     

    We also now have the Firewall "Troubleshooter" (I forgot its real name) in V9 that has been implemented to help with the firewall issues one may get. Other times an hour in Learning mode may solve issues automatically.

    Before ESS was created, i used a combination of NOD 32 + OUTPOST firewall. That worked pretty much the same as ESS does now.

    Use "Interactive" mode on ESS , run the 3rd party apps on the machines that you need to communicate ...... when you get the notification window pop up that shows the application name. Click allow and remember and that is all that's needed.

    There WONT be any firewall out there that knows the name & intent of every application created since time began in any sort of "Automatic" mode, and you will always have some manual work to do. Even windows firewall needs user interaction for every non windows/system application.

  7. Had exactly the same problem with my (GMAIL) account & outlook 2016 when i had changed over to v9. Yet my Hotmail and Yahoo accounts worked fine.

    If memory serves me correct i had to change the setttings on my GMAIL account online (from POP to IMAP/SMTP), and change the account settings within outlook to IMAP/SMTP . You will also need to change the ports for incoming and outgoing servers too.

    Was all fine under v8 using pop , so its definitely something in v9 that's causing the problem.

  8. Waited about 4 hour hours for the folders to sync from gmail, and it still never completed. So left outlook running overnight to see if it eventually managed to sync all the folders while i was sleeping. Woke up this morning and it had actually completed.

    Has there been a change in the way that v9 scans IMAP, that is causing it to run slower (crawl) on these type of accounts ??.

    It's still slower to check this gmail account under v9 now (15 seconds) rather than (2 seconds) it used to take under v8, using the same computer/connection/setup/mail client ..........

     

  9. Just tried temporarily disabling all protection from the GUI, and even that has no effect.

    I have just tested sending an email using outlook 2016 (From gmail account, to a hotmail account) , and the email is sent fine.

    Tried it in reverse (From hotmail account, to gmail account) , gmail stuck on "synchronizing subscribed folders".

    So whatever is causing the issue, its not there on OUTGOING mail and only on INCOMING.

    Like i said before i had no issues on v8 , the problem only presented itself on v9.

    Have also checked the settings within web based gmail to see if it was maybe an issue with the "Allowed apps" feature on gmail, but even using "Allow use less secure apps" does not resolve the problem.

  10. I reported this on the BETA forum nearly 2 months ago, and also filed a bug ticket for this when beta testing. Especially annoying as its intermittent. Was Firefox & windows live mail i was having the issues with.

    Got this email back on the day v9 final was released ....................... And they never fixed the issue
     

     

     

    Dear Customer,

    Several days have passed and we have not received a response from you regarding your request No. #TICKET 154344.

    If you managed to resolve your request in the meantime, please let us know.

    In case anything comes up, please get in touch with us if you would like - we are glad to help.

    Sincerely,
    Customer Support Team at ESET


     
×
×
  • Create New...