- Updated: Network Inspector - small changes
- New: Multithread scanning
The Network Inspector change is, in fact,
the removal of Radar View.
Regarding the Multithread scanning, this feature is poorly implemented. Running the Initial Scan upon a fresh install now renders my computer nearly unresponsive until the scanning ends. As it is, the scanner is too aggressive and opens up way too many file handlers, maxing out any of my SSDs and making it impossible to launch applications, browse web pages... pretty much anything. Scanning HDDs is also faster, but forget about using said drives while the scan is in progress since it caps out any disk resources while the scan is running. While the scanning speed is much, much faster than before, borking the entire system while it doing so is not an acceptable tradeoff.
Another change is the HTTP/3 (QUIC) scanner, and it's not without its own set of issues (affects EIS/EAV/ESSP)
[1][2][3][4][5]. Disabling it is the recommended workround, and I ran into some issues with it as well with pages breakings and general slowness while browsing.
Another issue I have noticed is that I have two network cards in my system with two ISPs. I set my primary network interface by configuring the interface metric on Windows. I've been running this setup trouble-free for years, and since EIS version 17.1.9 the primary interface keeps jumping between both NICs, breaking my configuration. No idea why this happened, but not only it affects my work environment, but it also renders some software unusable. A trace program like WinMTR is no longer able to distinguish on which network it is running, thus it can no longer report the host names along a trace path. VPN software I use for work is also unable to properly connect through the correct network.
Another problem is with wake on lan software, like WakeMeOnLan, which can no longer send the magic packet to the LAN, so I can no longer wake up my local computers.
All in all, I'm now moving all my systems away from Eset and back to Kaspersky. The amount of issues with each release has reached the breaking point for me, and this has been going on for over an year. Half-baked, poorly tested updates that break more than they fix/improve each time. Issues that are found on day one after any update, yet nobody at Eset seems to notice it.