Alessandro Cacciari

Sorry for the delay.... @Marcos I did not followed the detailed instructions you provided. "Working without antivirus" on that Windows 10 client was better than "not working with antivirus", at least for the short period. Solution you provided worked for a other computers (Windows 11 and Windows 10), on the problematic client I decided to reset Windows Firewall configuration, then allow every service was needed. That had to be done "offtime", due to the necessity of working computer as expected. Recently I updated both Windows 11 and Windows 10 computers with Nod32 17.1.11 and the "workaround" you suggested for 17.1.9 was indeed not needed. Thansk for the support, if not needed this thread for my opinion can be closed.

FWIW I have the same question too 🙂 However currently I'm more interested realizing (and apply) a working solution for the issue. At least for Windows 11 my test confirm that workaround works as suggested.

On the first computer, Windows 10 based, which had 17.0.16 before. Unfortunately changed nothing. Test on Windows 11 has done on a VM created from scratch.

Update, just tested with Windows 11. Change the OS into upper post, then apply this And... worked.

For helping reproduce the issue. Windows 10 fresh installed mark connected network as "private" allow file sharing (40bit encryption on file sharing allowed) share a folder mark "allowed" in windows firewall file and printer sharing services ping should be responded from the same subnet folder should be accessed from other computers Install ESET Nod32 17.1.9 Reboot ping is not responded from the same subnet

Good morning, Marcos Yes, indeed. Removing NOD32 17.1.9 "solved" the ping issue. And it reappered after was reinstalled.

Thanks for sharing, might help other people having the same issue. On this computer, before (Nod32 17.0.16) ping was working nice and as intended. Then I updated to 17.1.9, then reboot, and the ping stopped working. None Windows Firewall parameter has changed while upgrading.

I'm not that lucky. Sorry for poor quality screenshot and not-english language.

That's fair, i can do the same thing. However: from your router (if capable) can you ping your computer? Or from another computer/smarphone/device/whatever. Devices should be on the same subnet. IMVHO, NOD32 should not "mess" with firewall setup...

Thanks for the suggestion, however nothing changed. Computer has to be rebooted for the workaround to work? For avoid misunderstandings: I'm trying to ping the computer with ESET Nod32 17.1.9 installed, but i receive "timeout" as answer.

Greetings, recently my computer updated to current version of Nod32. Since update 17.1.9, neverthless the computer classify the subnet as "private", does not respond anymore to ping/ICMP inputs coming from other hosts in the same network, while allowing that on 17.0.16. Is this the intended behaviour? Is this a behaviour which can be changed in some way, better by subnet basis? (I wondered for half an hour into advanced settings and I found no obvious way to allow ping/icmp). I also tried to uninstall Nod32. As a user with administrative privileges, I were able to star the uninstall, however did not succeed due to "lacking permissions" for uninstalling some service/kernel driver. Is this also the intended behaviour? Using Eset Uninstaller currently is a no go for me (I currently don't have phisical access to the computer). Thanks for your time.