ESET's FIREWALL on Windows version 10.1.2046 blocks network connections (e.g., DHCP acquisition)
The problem is not reproduced on the previous Windows version 10.0.2045.0.
Problem: A network connection is blocked when ESET Windows version 10.1.2046 is running on a terminal that is not connected to the network.
Workaround: Temporarily disabling ESET FIREWALL will allow network connections. Thereafter, the network connection will remain open even if ESET FIREWALL is enabled. However, if the network connection is turned off, the computer is started, and ESET is running, the network c
I have not found a drastic solution at this time, but I have found a tentative workaround.
After updating to 10.1.2046 version, I checked the Firewall log and noticed that DHCP (69/udp -> 69/udp) is blocked. Then, looking at the default rules of firewall, I noticed the following permissions for inbound, but not for outbound. So I added a rule that grants permission to outbound, and the problem was solved.
Allow DHCP for svchost.exe
Local ports: 67, 68 /udp
SYSTEMROOT\system32\sv