Jump to content

lezboyd

Members
  • Posts

    20
  • Joined

  • Last visited

Posts posted by lezboyd

  1. Hi Marcos,

    I opened the link for Log Collector in your signature, and noticed an Alert similar to the problem I was facing.

    hxxp://support.eset.com/alert6383/

    I followed the steps in there and now its working again. Thanks.

    However, this has led me to a different issue.

    The issue is, while most of my banking/payment portals work fine when I disable ESET B&P Protection altogether from the settings OR choose to open them in a regular browser by configuring the same in the settings, one of my bank's website refuses to work outside ESET's secure browser instance, even when I have disabled B&P Protection from settings and/or chosen to open the Bank's website in a regular browser. I am not comfortable giving out further details about my bank here, so I was wondering if you can help me troubleshoot the same in PM.

    Thanks again.

  2. Since the last two days, ESET Banking & Payment Protection does not work. When I activate it (either manually or by trying to access my bank's site), it gives the following error:

    (see attached file ESET-BUg-1.png)

    I restarted Firefox and tried again. Same message.

    I cleared all history and cache and tried again. Same Message.

    Firefox is updated to latest stable version, i.e., 51.0.1 (32-bit).

    On clicking 'Close Firefox' button in the above message, it then throws this message.

    (see attached file ESET-BUg-2.png)

    I have no idea what this means. My normal Firefox windows and tabs are working just fine.

    Hoping an admin here can help. Thanks.

    ESET-Bug-2.png

    ESET-Bug-1.png

  3. 4 hours ago, Marcos said:

    We have received an initial response to our open case at Microsoft and they confirmed that it looks like a bug in wfplwfs driver. ... The problem is that L2802_3ParseMacHeader function in wfplwfs Microsoft’s driver does not handle this scenario well which may result in BSOD.

    Thanks for the update. Have they given any timelines for the resolution?

    Meanwhile, I will try using a Wi-Fi router instead of a direct connection and see if that helps.

  4. @itman : ESET firewall is running in Automatic mode with 'Evaluate also rules from Windows Firewall' turned OFF (since I have the Windows Firewall service Disabled; relying solely on ESET's firewall).

    Currently I am testing my theory by not using any of the apps I have set a firewall rule for and seeing if I get a BSOD. A couple weeks later (last time I tested for only a week, declared everything solved and fell flat on my face), I will test by deleting the custom firewall rule for one of the apps and then using that app for a prolonged period.

  5. On 19/1/2017 at 2:35 AM, Marcos said:

    Epfwlwf.sys is the firewall driver used by v9. V10 doesn't use it on newer Windows. We don't need you to do anything as it will be Microsoft's turn after we report the problem (probable Windows bug) to them.

    Just adding one more thing I have noticed. So far, I have got BSODs whenever I have run apps for a prolonged period for whom I have set an application-based Firewall rule (allowed an app, for example) in ESS. If I am using apps for which I have not set a deliberate rule in the firewall, I get no BSODs. Just something I noticed. It might still be a Windows bug, as in how Windows drivers reacts to ESS drivers handling an app-based firewall rule.

  6. 2 hours ago, Marcos said:

    We assume that the issue should not occur with v9 as it uses epfwlwf which does not register in Microsoft's wfplwfs driver. Could you confirm?

    Thanks for opening the ticket with Microsoft. Hopefully that'll lead to a resolution.

    Regarding the second half (quoted), not sure exactly what you need me to do. From my side, I've checked the Windows drivers folder; did not find epfwlwf.sys there. It has epfwwfp.sys and epfw.sys among other ESET drivers that do not start with "epfw".

    Nothing with that name found under Local Services either. Please advice. 

    Just to be clear, I'm currently on ESS v10.0.369.0. The BSOD problem has started since v9 and continues in the latest version.

  7. 10 minutes ago, Marcos said:

    We have come across numerous cases when issues began to manifest after installing ESET but the root of the problem was elsewhere. It used to be either a badly written 3rd party software, a bug in the software and at least 2-3 times it was a bug in Windows itself.

    I don't doubt that. But I would imagine that experience would have made this process easier and would not entail having to wait weeks for an uncertain outcome. I have also noticed that no one from ESET has asked me for a single thing to help identify the issue. Whatever I have provided, I have done so voluntarily. If the dumps are not enough, is there something else I can provide that would help?

    I have been using ESET since v3 and have been using most other softwares on my laptop for years too, across multiple laptops, never running into a problem until I upgraded to ESS v9 and beyond. It's a fact.

  8. 28 minutes ago, Marcos said:

    In a few weeks the firewall developers are going to pay visit to Microsoft and inquire them as to why they think the issue is caused by ESET. It's not obvious from the dumps that ESET is the culprit.

    From my side, it makes sense. The BSODs started after I installed ESS. They went away for a month when I uninstalled ESET and worked with Windows Defender (which has to be the worst app around) and resurfaced when I installed ESS.

    At this point, I am updating all the device drivers from scratch, updating Windows components, and running DISM/SFC. I have also turned off the Windows Defender and Windows Firewall services, in case ESET clashes with those. If this does not solve it, I suppose its money wasted on a 3-year ESET license. I will be forced to uninstall it and go with something else.

    I shall keep you informed.

  9. On 5/1/2017 at 7:35 PM, Marcos said:

    As soon as I have some news from devs, I'll let you know. Could you try (at least temporarily) uninstalling PeerBlock which uses a driver from 2013 and see if the problem goes away?

    I spoke too soon in my previous posts :(

    Just received another BSOD today, this time with no PeerBlock running. Linking to dump files below:

    https://1drv.ms/f/s!Avzd_Hgdj4WQe9ujeToGujFKRe4

    Please help.

  10. I have been running ESET without running Peerblock for the whole of last week and till the time of this writing, and have not got a BSOD. I suppose it is safe to assume that the 2 drivers are not getting along. However, ESET is in active development whereas Peerblock is not. Also, previous versions of ESET have worked without issues with Peerblock.

    So I'd like to ask if there is a way to make the 2 drivers play along with one another, as in previous versions.

    Peerblock has the ability to work with blocklists for malicious, malware and ads domains. This is a pretty cumbersome, complex and manual process in ESET. On the other hand, ESET has application specific firewall rules, which is very handy. So currently I need both.

  11. 2 minutes ago, Marcos said:

    I see "Probably caused by : wfplwfs.sys ( wfplwfs!L2802_3ParseMacHeader+87 )" in the dump. Wfplwf.sys is Microsoft's driver. After the New year, our devs will check it out to definitely confirm or deny that the crash is caused by ESET.

    Thanks for the reply, Marcos. If you read the above thread, the Microsoft specialist replying to me in the topic is very certain it is the ESET driver after analysing the same dump.

    I also did not face any BSODs when I had uninstalled ESET and was working with (the horrible) Windows Defender.

    I shall await a reply from your devs in this regards, and shall help them with any additional info they desire.

  12. Today, I got a BSOD related to epfwwfp.sys, which is an ESET Personal Firewall driver.

    I have faced this problem a few weeks before also, but at the time, I had upgraded directly from ESS v6 to ESS v9, so I thought that might be the cause. I uninstalled ESS and used Windows Defender for a few weeks to make sure that ESS was actually the cause. I then did a fresh install of ESS v10 on Dec 5 and faced no issues since. But today I got a BSOD again, and it was again traced back to ESET driver.

    Here is the troubleshooting done at Microsoft's website.

    https://answers.microsoft.com/en-us/windows/forum/windows8_1-performance/wfplwfssys-related-bsod-need-help-updating-driver/95b928b1-2ffe-4050-b2d4-2e5ee06f2329?tm=1482582489401

    I have a 3 year license key that expires in 2019, and I have used ESS for the past 6 years with no issues. This issue has started since v9. I am hoping someone here can resolve this issue for me so I can remain loyal to ESET. Thanks in advance.

×
×
  • Create New...