Hello,
we noticed a few of our Windows computers to have network issues similar to the already described ones in here too.
One Windows 7 and two dozen of Windows 10 with primarily update 1909, but also 2004. ESET Versions 5.0.2237 to 5.0.2272.
We can reproduce the network issues by (either automatically or manually) running the "automatic startup file check" under schedule manager on the clients. This explains the different times after a reboot, when the problem occurs. ESET seems to not run the scan instantly and runs it a little bit delayed after system boot or latest on update of the virus signature database.
The scan then starts and continues to run seemingly without any problems. At some point the memory usage of ekrn.exe drops and at that point outgoing TCP connections are blocked. The scan also doesn't complete and the ESET client is showing the loading symbol in the taskbar.
A possible workaround I found is to disable the systemintegration for HTTPS and POP3 scans (via advanced settings on the client). [This obviously disables scanning network traffic which degrades the overall security. Be warned!]
I haven't managed to get a dump via the tool described before, but will try again tomorrow.
I have a screenshot of the running threads attached right after the memory usage drop where ekrn.exe seems to hang. Also a screenshot of the memory usage during the scan.