Jump to content

Hydro

Members
  • Content Count

    13
  • Joined

  • Last visited

Profile Information

  • Location
    Netherlands
  1. Even when creating the rule within 1 of 2 seconds (selecting option “Create rule and remember permanently” and then pressing the Deny button), the initial connection is never blocked (TcpTestSucceeded result is always True). The issue occurs regardless of the user timing, regardless of the network adapter (ethernet or wifi, docked or not) and regardless of the application. It also occurs with a clean install of EIS, with default settings (except for the firewall filtering mode, which is set to Interactive mode).
  2. My firewall driver appears to be identical, although my “Date modified” differs (see below). But the ESET digital signatures are OK (dated Friday, November 3, 2017). In essence, the firewall driver seems to be functioning correctly, apart from the occasional BSOD (doesn’t occur that often anymore) and a traffic leak issue when using interactive mode (see other thread). I’ve disabled all virtualization options in the BIOS and disabled all Hyper-V features with the following two actions from an elevated Powershell prompt: bcdedit /set hypervisorlaunchtype off Disable-WindowsOptiona
  3. Currently at Firewall module 1373.1 (20180103), but the EIS firewall still leaks outbound traffic when a new deny rule is created in interactive mode, regardless of the application and regardless of the network adapter being used. In essence, the EIS firewall driver seems to be functioning correctly, because when I click “Deny” with the “Ask every time” or “Remember until applications quits” option, the outbound traffic is being blocked, as expected. Existing deny rules are also functioning as expected. However, the EIS firewall fails to block traffic when I click “Deny” with the “C
  4. A few days ago I’ve disabled all Hyper-V features on my Windows 10 notebook, as suggested by itman, and it appears to have improved the stability. Unfortunately, today another computer freeze + BSOD (DPC_WATCHDOG_VIOLATION) occurred, while using Chrome: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. Probably caused by : epfwwfp.sys ( epfwwfp+39fc ) DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT FAILURE_BUCKET_ID: 0x133_ISR_epfwwfp!unknown_function Image path: \SystemRoot\system32\DRIVERS\epfwwfp.sys Timestamp: Fri Nov 3 15:53:40 2017 (59FC82F4) Product: E
  5. I just noticed that the DPC_WATCHDOG_VIOLATION (SINGLE_DPC_TIMEOUT_EXCEEDED) BSOD that I previously encountered, is almost identical to the issue that’s described in this article: https://kc.mcafee.com/corporate/index?page=content&id=KB90097 STACK_TEXT of my BSOD with the pre-release version of EIS 11.0.159: fffff800`7f19dbc8 fffff800`7f62a607 : nt!KeBugCheckEx fffff800`7f19dbd0 fffff800`7f4e8666 : nt!KeAccumulateTicks+0x140207 fffff800`7f19dc30 fffff800`7f41d3c5 : nt!KeClockInterruptNotify+0xc6 fffff800`7f19df40 fffff800`7f537da5 : hal!HalpTimerClockIpiRoutine+0x15 fffff800
  6. No, I was running the pre-release version of EIS, with Firewall module 1373 (20171206), when the BSODs occurred. Now I’ve returned to the regular version, with Firewall module 1372 (20171027). Both versions leak traffic in interactive mode. I’ve also encountered some computer freezes/hangs with both EIS versions (after I’ve updated to the Fall Creators Update). Not anymore: 16299 has become the standard build, see https://techjourney.net/windows-10-fall-creators-update-rs3-v-1709-build-16299-15-rtm/ (latest standard build is now 16299.125, since KB4054517). I’ve never installed the Win
  7. Similar issue here: multiple ESET related BSODs occurred on my Windows 10 Dell notebook (Precision 3520). I think the problems started after updating to the Windows Fall Creators Update (version 1709, build 16299) and EIS 11.0.159. First received a DPC_WATCHDOG_VIOLATION on epfwwfp.sys, during the installation of an Intel Wifi driver update (latest Proset software for AC 8265 adapter). Could not start Windows in normal mode since that moment, due to BSODs occurring on em008k_64.dll (firewall module) each time during startup, with one the following errors: ATTEMPTED_WRITE_TO_READONLY_MEM
  8. The latest pre-release version of EIS 11.0.159, with Firewall module 1373 (20171206), is also affected. When a new Deny rule is being created from the "Outbound network traffic" popup, the firewall does not block the initial outbound connection! Steps to reproduce: 1. Set the EIS firewall to Interactive mode 2. Open Powershell from the Windows start menu and run the following command: Test-NetConnection -ComputerName bing.com -Port 80 3. Choose "Create rule and remember permanently" -> "Deny" from the EIS "Outbound network traffic" popup The Test-NetConnection cmdlet will no
  9. For those who don't have telnet enabled on their machine, it's also possible to test with the following Powershell command: Test-NetConnection -ComputerName ad.doubleclick.net -Port 80
  10. Tried different things, including Marcos' suggestions, but the issue persists. I think this is a bug in the firewall. Easiest way to reproduce: run "telnet ad.doubleclick.net 80" (or similar) from a cmd prompt, with the firewall in interactive mode, so that EIS will display an "Outbound network traffic" popup. If you click "Ask every time" -> "Deny", the connection is blocked, as expected. Normal behaviour. However, if you click "Create rule and remember permanently" -> "Deny", a connection is established! Very undesirable behaviour. (to terminate the telnet http conn
  11. Product: ESET Internet Security 11.0.159.0, Firewall module 1372 (20171027) OS: Windows 10 Enterprise v1709 64-bit Firewall is set to "Interactive mode". No custom rules have been created yet. Windows application tries to access the internet. EIS displays "Outbound network traffic" popup. So far so good. However, when choosing "Create rule and remember permanently" -> "Deny", the application is still able to access the internet! A valid Deny rule will be created, but it is ignored the first time! Subsequent connections are refused, as expected. When choosing "Ask every time
  12. ESET, please fix this firewall bug! The firewall is virtually unusable in ESS v10.1.204 (on Windows 10 Enterprise v1607 x64). And a downgrade isn’t an option for me, because with the previous ESS version I experienced network protection problems (just like user Arash in the other thread).
  13. Same problem here, running ESET Smart Security v10.1.204 on Windows 10 (v1607 x64), with the firewall in interactive mode. It’s driving me mad, the ESS firewall is ignoring all rules and just keeps asking if I want to deny or allow traffic, again and again. Rules are being saved properly, but the firewall just ignores them (causing confusion and resulting in many duplicate rules being created). Happens with all applications: Windows Store, Chrome, Outlook etc. The problem sometimes disappears for a while (maybe after restarting the computer or after opening all ESS firewall rules and
×
×
  • Create New...