Jump to content

heyyahblah

Members
  • Posts

    19
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by heyyahblah

  1. On 9/26/2019 at 3:41 AM, Marcos said:

    It'd be good to get the logs and analyze them first. Make sure that you collect them with "All" profile selected in ESET Log Collector.

    Also please enclose the file C:\ProgramData\ESET\ESET Security\versions.csv which is not collected by ESET Log Collector.

    There's a chance that it could be fixed by editing a particular value in the registry.

    Hello @Marcos sorry for my late reply, but had a computer problem.

    I won't be able to send the logs unfortunately. 😪 My boot-drive SSD died before I had a chance to collect any information so I had to send the drive in for R.M.A. I will have to re-install everything from scratch when I get my drive back so I will be redoing everything from fresh Windows. 

    When my drive comes back I will install ESET again and see what happens. 

    Thank you all for the help.

  2. 16 hours ago, Marcos said:

    Please provide me with logs collected with ESET Log Collector. Prior to collecting logs, select "All" from the template drop-down menu in ESET Log Collector.

    @Marcos From what everyone is telling me on this thread, it looks like my install is broken and I have to uninstall ESET and then reboot and reinstall fresh copy and reconfigure everything from scratch.

    Also I will be away from my main PC for a few days so hopefully I will be able to do something when I'm back and a new version of ESET will be out hopefully soon. 

    Do you still want me to save files and send logs via ESET Log Collector when I get back, it seems I need to download ESET software form website to collect the logs, is this still important? Or should I just uninstall ESET and try to reinstall FRESH copy and see what happens? Or are log files important to you? What would be better? I would have to send an update when I get back after a few days.

    Thank You. 

  3. 8 hours ago, Swamp Yankee said:

    @heyyahblah Here is the thread from July that I read and then commented in about this problem, and then after reading the comment by @itman about in program Version upgrades (ie V11 to V12) possibly being a problem, I just did a clean install, then went thru and reconfigured everything how I wanted it.  It's good to do that once in awhile, you relearn your software. It's also good to save the old version installers some wheres since ESET does not.

    Hey man, thank you for taking the time out and directing me to links to the other threads about this. I guess regarding what you said and what @itman posted this looks like my only way out.

    I guess I have no other option and I will just run the un-installer of ESET and remove it from my computer. Then I'm guessing a reset and visit the website and do a fresh install and just configure everything from there again from scratch and it will solve the problem? That is what worked for you?

    Thanks for the info about ESET not saving old installers. Since v12.2.29.0 is buggy and I don't have v12.2.23.0 saved anywhere I guess I will wait for a fixed update release? I'm guessing ESET is pushing a new version soon since so many people have posted issues with WNC and Windows 10 that they will be releasing an updated version soon. I'd rather fresh install from that version, I'll also be away from my main PC for a few days so hopefully I will be able to do something when I'm back and a new version will be out hopefully soon. 

    Thanks for the information on this and will keep you guys posted in this thread. Thanks for everyone that came out for the help. Appreciate it.   

  4. 11 hours ago, itman said:

    I was going to post this might be a way to fix the issue. However, you would have to import settings from a prior export where the Eset GUI was properly configured. And of course, you will lose any GUI changes such as new rules created and the like that occurred subsequent to when the export was performed.

    OK, I understand. Since the program seems to be borked like @Swamp Yankee mentioned to me then I guess I will just take screenshots of my settings, and make sure I have my key ready and uninstall ESET and then re-install ESET from a fresh install and configure it then and hopefully it will work and go back to normal. Probably something got messed up with the in product updates and I never realized it.  Thanks for the info. 

     

    7 hours ago, Posolsvetla said:

    The notifications are not shown anymore, if our blocking web page is shown directly in a web browser.
    Those notifications are redundant in such cases. It involves anti-phishing and PUA protection, to name a few cases.

    OK, thank you for that information. I wasn't sure about that either. I guess my install is botched and I probably will have to uninstall and reinstall ESET to fix the problems I am having. 

  5. 1 hour ago, Marcos said:

    Please post information about installed modules (e.g. Update -> Show all modules).

    Here is the information you requested @Marcos

    Detection Engine: 20075 (20190925)
    Rapid Response module: 14957 (20190925)
    Update module: 1018.1 (20190709)
    Antivirus and antispyware scanner module: 1555 (20190911)
    Advanced heuristics module: 1193 (20190626)
    Archive support module: 1292 (20190911)
    Cleaner module: 1200 (20190916)
    Anti-Stealth support module: 1154 (20190614)
    Firewall module: 1390 (20190712)
    ESET SysInspector module: 1275 (20181220)
    Translation support module: 1755.2 (20190913)
    HIPS support module: 1371 (20190906)
    Internet protection module: 1376 (20190806)
    Web content filter module: 1071 (20190605)
    Advanced antispam module: 7820.1 (20190910)
    Database module: 1110 (20190827)
    Configuration module (33): 1777 (20190613)
    LiveGrid communication module: 1053 (20190321)
    Specialized cleaner module: 1013 (20190627)
    Banking & payment protection module: 1158 (20190905)
    Rootkit detection and cleaning module: 1019 (20170825)
    Network protection module: 1680 (20190403)
    Router vulnerability scanner module: 1063 (20190724)
    Script scanner module: 1054 (20190905)
    Connected Home Network module: 1031.1 (20190621)
    Cryptographic protocol support module: 1040 (20190913)
    Databases for advanced antispam module: 3526 (20190925)
    Deep behavioral inspection support module: 1079 (20190614)

    modules.png

  6. 1 hour ago, Swamp Yankee said:

    I had the same problem as you, and I think it got borked during an in program version upgrade.

    So I'm gonna guess you did an in program version upgrade.

    I never noticed it until I was reading a post about someones problem with 'Desktop Notifications', and when I looked at my setup trying to find 'Desktop Notifications' it wasn't there, just 'Email notifications' just like yours.

    Fix-Do a clean install and all was good again.

     

    Oh wow. Yea I only update ESET when I get a notification that a new version is available then I click update and it asks me to restart and I restart and I figure all is well. I haven't re-installed ESET ever because I've had no reason to on my main PC. Oh wow, so the only solution is a clean install? Ugh. Is v12.2.23.0 still available? I don't want to upgrade to the latest version, as its buggy right now. 

    Thanks for letting me know you had similar problem, is that how you fixed it clean install only? Can you still export/import settings or no? I wish there was an easier way ... 

     

  7. 39 minutes ago, itman said:

    I am using 12.2.29. But there should be no change in regards to that section from 12.2.23.

    Also your screen shot shows "Email notifications." In that slot should be "Notifications." So it appears to me there is something not right with your Eset GUI setup. Click on Email notifications and see if that brings up the screen @Marcos posted.

    I checked everywhere and I don't have the Notifications menu like you do for whatever reason. It doesn't come up anywhere at all .... wth is going on? How would I lose the Notifications menu and only have it show email notifications. 

     

     

    wtf.png

  8. 22 minutes ago, itman said:

    When you click on the Notifications settings under Tools, Eset should display the screen @Marcos posted. From your screen shot, it appears that setting is missing. Suggest you either do an Eset repair install if that option still exists for 12.2.23 or uninstall/reinstall 12.2.23. Make sure you export your Eset settings prior to uninstalling if you have made custom changes to the Eset GUI settings. You can then import those settings after 12.2.23 is reinstalled.

    Which version of ESET are you using and what operating system? Is your advanced setup screen the same as the one @Marcos posted or is it like mine?

  9. Has anyone been experiencing this issue or not. I'm using EIS v12.2.23.0 here and Windows 10 and I've come to notice that I don't get a notification message or sound beep from ESET anymore when modules are updated or when website URL's have been blocked for security reasons on certain websites. I have not made any changes to the advanced setup or disabled any notifications. 

    I even went as far as hitting the 'DEFAULT' button in advanced setup and ESET pop-up message said this will revert all settings to default, this action cannot be undone just to make sure I didn't un-check anything, so I restored to default and rebooted Windows and same thing. No notifications or sound notifications on updates or web page blocking. I purposely have been testing a websites that should show notification messages about being blocked and nothing is coming up by the action center on the bottom right as it should. 

    Is anyone else experiencing this issue of no notifications from EIS? This is on my main rig that I have not updated to v12.2.29 because of the bugs. I have left it at previous version but have noticed I am not seeing messages anymore. Suggestions?

    Thank you.

     

     

  10. 27 minutes ago, Pete12 said:

    Yes, its a well known bug by now ..........it appeared with this buggy update to 12.2.29 .

    Rolled back to previous version 12.2.23 , with NO BUGS at all !!

    I dont understand why (!) ESET still did not react .............WHEN WILL THESE TROUBLES GET FIXED !!!   :angry:

    I contacted support already , they want to look in my PC , but whats the use without a new update , its not our OS , this is an ESET-problem ...................!!

    @Marcos I'm forced to agree here. I did my own testing here on a separate computer I have here that I strictly use for testing software, troubleshooting, etc.  I've invested the last 3 days with this. This is an ESET v12.2.29 issue and is not related to Windows 10 or Microsoft WSC whatsoever, it is clearly a buggy software update at the fault of ESET. 

    I have installed 3 previous/older versions of Windows 10 on this machine from fresh install media. Windows 10 v1709 (Nov 2017) and Windows 10 v1803 (April 2018) and Windows 10 v1809 (October 2018). The WSC issue is a common problem in all the versions of Windows 10 I have tested. It is not strictly related to v1903 (May 2019). 

    When v12.2.23.0 is installed on any version of Windows 10 ... everything runs fine. When v12.2.29 is installed at each cold-boot or reboot Windows 10 says firewall and AV is turned off, just like the screenshot the OP has posted. There is an error in the code and the developers need to roll back to v12.2.23.0 to figure out what went wrong in the changes. If I am seeing this from fresh install media, then I am sure this issue is widespead and affecting pretty much everyone. 

    I just wanted to share my thoughts on this. 

     

    On a side note ... I am making a separate thread because I noticed that ESET notifications do not show up for me anymore on my main machine. 

  11. Hello again, yes ... all links that @itman and @Marcos posted the links do not work. When I click on any of them they open up in a regular browser window or new tab.

    If you click any of these links like on the American sites:

    https://www.bankofamerica.com/

    https://www.wellsfargo.com/

    I am prompted to open the website in a secure browser. All of my banking websites worked fine last week as I was doing the banking then. As I mentioned. No Windows 10 updates have been installed. No new hardware or software has been installed or modified. No viruses or malware (I have done full scans). ESET IS has been working normally. Just noticed yesterday when I tried to do online banking. I thought it was just my bank that was targeted but any banking Canadian website I do not get a prompt to open the website in a secure browser. I have to do it manually via ESET now. I can post the links of sites, and they have stopped working for me. Same links as @itman posted but I can add more.

    https://www.cibc.com/en/personal-banking.html

    https://www.scotiabank.com/ca/en/0,,2,00.html

    https://www.td.com/ca/en/personal-banking/

    https://www.rbcroyalbank.com/personal.html

    https://online.citi.com/US/login.do

    All of these websites prompted before and now it just stopped.

     

     

    ESET.png

    ESET2.png

  12. Is this something that just happened recently??

    Last week I was using this feature just fine. Never had a problem with ESET banking. I have not made any computer changes. No updates, no new software, no new Windows updates, nothing. 0 changes to the system. All is fine and running as it should be. Banking always worked. Now when I type in any Canadian banking website that I open doesn't work anymore (auto-direct) or auto-detect with ESET Internet Security 12.0.27.0 

    This was always working fine for me. Just checked my bank last week. I test in Google all major Canadian Banks, and none of them work, (all Canadian banking sites) but when I type in Google Bank of America or Wells Fargo to test a different bank ... it works. What happened?? Did something get changed in ESET over the weekend? New modules or new website coding? It just stopped working last week. I can still get it open manually via ESET > Banking and Protection. Then I get the green sandbox window of my default browser (firefox) but I still have to type the url manually. Until last week I have never had a problem with this.

    Tried all my browsers. Edge, Firefox and Chrome. All with 0 extensions. Just stopped working. And I know it not a browser issue or computer issue because if I type Bank of America or Wells Fargo it works in all 3 browsers just fine. This happen to all Canadian banking website. Just stopped working.

    Error with modules? This problem just started. I tried all the troubleshooting steps, before posting. Such as disable banking, reboot computer, enable, clear sites, and everything. Did not fix the problem. I do not think ESET is corrupted because everything else works.

    Suggestions? Thanks.

  13. Is this something that just happened recently?

    Last week I was using this just fine. Now any Canadian banking website that I open doesn't work anymore (auto-direct) or auto-detect with ESET Internet Security 12.0.27.0 

    Was working fine next week. I test in Google all Canadian banks, none of them work, but when I type bank of america to test a diffrent bank it works. What happened? Did something get changed over the weekend. It just stopped working last week. I can still open manually via ESET > Banking and Protection. Then I get the green sandbox window but I still have to type the url manually. Until last week I have never had a problem with this.

    Tried all my browsers. Edge, Firefox and Chrome. All with 0 extensions. Just stopped working. And I know it not a browser issue or computer issue because if I type bank of america it works. This happen to all Canadian banking website. Just stopped working.

    Error with modules?

    Thanks.

  14.  

    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.

     

    Do not ignore these updates, these updates are real and its a bug with WINDOWS 10 not with ESS v9 !!!!

     

    Actually, these are not bugs. It's just that the update system is Windows 10 is stupid. If that was Windows 7 or Windows 8.1 ESET would run the old Windows Update and update all the necessary drivers for you automatically as they would be listed in the old Windows Update section under recommended updates or optional updates.  That has been removed in stupid Windows 10 and placed into the settings menu. I thought the same thing until I thought hmmm .... maybe ESS is right. Why do I have 16 recommended system updates? This can't be right .... this has something to do with device manager drivers not being updated by Windows 10 properly and ESET is correct, I do have driver updates.

     

    So I took a screen shot and did it myself, I had 16 of those recommended updates and stupid Windows 10 update could not find any of them but ESET v9 did, and it kept saying I had 16 recommended updates. So thank god it did, because it updated all my drivers, thanks to ESET.

     

     

    Don't believe me?

     

    Go to CONTROL PANEL > DEVICE MANAGER > SYSTEM DEVICES

     

    Most of those recommended updates you have there cyberhash will probably be under system devices. Find the exact same name that ESET gave you, right click properties on that particular driver, check the date (write it down if you have to) and click update driver. You will see that it will connect to the internet and download the driver and install it and then it will ask you to reboot the system. Even that broadcom driver you have listed with either be under network adapters or whatever bluetooth adapter goes under. You will see, right click it, check properties, check the date and driver version, do update driver and you will see it updates and ask for a computer reset.

     

    This is not a bug in ESET, this is a bug in Windows 10. When you update all your drivers via device manager, you can thank me later, and thank the ESET team that it still finds updated drivers for Windows 10, because Windows 10 is still BETA garbage that cannot even update recommended drivers by ESET, even though this works on Windows 7 and Windows 8.1.

     

    I know because I have an 8.1 machine and a W7 machine and ESS v9 works properly with it. Windows 10 is the BUG here. Not ESS.

     

    If you get these messages, do not ignore them !!!! Manually update your drivers via CONTROL PANEL > DEVICE MANGER.

     

    Depending on what updates you have, most of the updates will be under the SYSTEM DEVICES tab in DEVICE MANAGER!!! Don't ignore the warnings. ESS is good at detecting outdated drivers on your computer.

     

    hxxp://i63.tinypic.com/2myntqp.jpg

     

     

    post-10772-0-45653600-1459323339_thumb.jpg

    post-10772-0-92829400-1459323659_thumb.jpg

  15. In order to pinpoint the culprit, we'll need a complete memory dump from the state when the system is unresponsive. Please refer to hxxp://support.eset.com/kb380/ for instructions how to configure OS to generate complete memory dumps and how to trigger manual crash so that a dump is generated.

    Once you have a complete memory dump created, compress it, upload it to a safe location and pm me the download link.

     

    This is not a bug. The notifications tell you that your hardware manufacturer has a newer version of drivers available. I'm not entirely sure but I guess these should not be displayed if you select to be notified only about critical updates.

     

    Hello Marcos, sorry for the long reply. After vigorous testing I have determined that ESS v9 is not the problem and WINDOWS 10 FAST BOOT was causing the issues on the computer. When I disable the WINDOWS 10 FAST BOOT the problems went away. Looks like WINDOWS 10 operating system is buggy and is a piece of O/S.

     

    Also, thank you again for the notifications. Again, ESS v9 was nice enough to tell me that my DEVICE DRIVERS were not up to date, WINDOWS 10 did report no update available but when I went into DEVICE MANAGER>CONTROL PANEL I clicked update driver for the 16 RECOMMENDED UPDATES from ESS v9 and it did update all my drivers in DEVICE MANAGER accordingly which WINDOWS 10 did not, I had to do it manually.

     

    Again, Windows 10 being a piece of OPERATING SYSTEM.

     

    If it was not for ESS I would have not had UPDATED DRIVERS on my COMPUTER which I manually had to UPDATE via DEVICE MANAGER. Windows 10 is a beta and buggy O/S that is causing this problems.

     

    Once again, people that are having freezing issues, DISABLE FAST-BOOT in WINDOWS 10 .... IT IS BROKEN!!!

  16. Hello all,

     

    I am posting in these forums because for years I have been using ESS security software, since my XP Machine and the days when it was called NOD32. I loved it and never had any problems with any version of ESS up until now v9. All the previous versions worked flawlessly on my computers.

     

    Now here is the thing. I waited and waited and finally updated my system to Windows 10 TH2 OS Build 10586.71 in November. Now this is a clean install.

     

    I realize I did a stupid thing by removing ESS v9 before making this post so I could be able to send some logs but the freezing was driving me insane that I had to remove it. So basically my problem is that with ESS v9 on some occasions when I boot up the computer it just freezes right at startup after I login. The system becomes unresponsive. The only way I can get back into the system is by holding down the power key and power down and then restart. Sometimes after the 2nd try I get in.

     

    Now the reason I am thinking that ESET is the culprit because this is my 3rd install on this machine. Clean format install. First I thought it was a drivers issue, then I blamed and diagnosed the hardware. After doing these steps for the last 2 months and up until today I did another format and descovered that my ESS v9 is the culprit.

     

    Now how do I know this? Well this format around, I installed nothing. I did a complete clean install from the USB ISO created by Microsoft installer. Then once I installed I added 3 programs, Firefox, Chrome and Winrar. Also added Flash for Firefox, let Windows update install all the rest by itself, drivers and etc.

     

    This laptop is a Lenovo ThinkPad x220 series laptop. So the hardware is decent. i5-2520M CPU, 4GB RAM, 256GB SSD, Intel HD Graphics 3000. All drivers and everything are WHQL signed and work just fine, no problems in display manager.

     

    So, I installed ESS v9, completed setup, activated trial license 30 days, reboot working OK, reboot again, working fine. Shut down, leave for a few hours, startup. Boom, frozen at desktop with the ESS logo on the desktop, system completely unresponsive.

     

    Had to hard shut-down the computer via power button. Now this had been happening for the last 2 months and I was troubleshooting the out of the laptop, thinking its a driver error, Windows 10 error, some other software, nothing. I am not a n00b when it comes to computers so I couldn't believe it was ESS v9, it was my last resort.

     

    Anyways, I uninstalled ESS v9 and low-and-behold!!! The system doesn't lockup anymore!!! All is back to normal. So, there is something in ESS v9 that is causing my W10 machine to freeze at boot for no apparent reason.

     

    As I make this post I am going to install ESS v8.0.319 and activate a trial license and see how the system responds. I never had any problems with ESS v8, it always worked just fine. I went to v9 because I figured new Windows (w10) I should update the software to ESS v9 for Windows 10 because its probably made for it.

     

    So I am going to keep this thread active and see how it goes. As it stands now, ESS v9 has been removed from my system, I have no A/V and the computer is not freezing at all. I am booting up, shutting down, restarting, everything, no freezes. This is now my 4th clean format and quite frankly I am sick of formatting the computer trying to troubleshoot it, thinking it was something else.

     

    I will monitor this for 24h and proceed to install ESS v8 and see what happens to my system. As far as I stand ESS v9 is locking up my computer because as soon as I removed it, the freezing stopped.

     

    This is an official release of Windows 10 PRO v1511, no insider editions nothing. And no other software or drivers have been installed. I have left this as basic as possible, to see what is causing the freezing at boot. So far no ESET, no freeze, so its starting to make me really wonder about ESS v9 and W10 compatibility. I don't think ESS v9 is W10 ready yet IMO.

     

    Also ESS v9 kept on asking for operating system updates to W10, that were non-existent. It would suggest 20 or so critical updates (mostly hardware) but when clicked to update, the notification would just disappear and Windows Update would come back saying no new updates are available. So this is a bug in v9 for W10 machines.

     

    I hope an ESS Tech Support team/agent will take a look into this and follow up with me. So far as I type this ESS v9 has been removed. I'm sorry I didn't keep it for log purposes but if you need me to reinstall it, I will to find out what is causing these errors.

     

    So far I want to monitor the computer and abuse it, see if there are any lockups at boot without ESS v9 installed so I can 100% rule out that it is the cause of my system lockups. Thanks.

     

     

     

     

     

     

     

×
×
  • Create New...