Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Security Apps
ESET
ESET v17.0
Message
<blockquote data-quote="cofer123" data-source="post: 1081957" data-attributes="member: 92976"><p>The Network Inspector change is, in fact, <a href="https://forum.eset.com/topic/40544-version-17190/?do=findComment&comment=182373" target="_blank">the removal of Radar View</a>.</p><p></p><p>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.</p><p></p><p>Another change is the HTTP/3 (QUIC) scanner, and it's not without its own set of issues (affects EIS/EAV/ESSP) <a href="https://forum.eset.com/topic/40431-nod32-17190-not-allowing-vpn-to-connect/#comment-182362" target="_blank">[1]</a><a href="https://forum.eset.com/topic/40527-eis-17190-and-http3-scanning/" target="_blank">[2]</a><a href="https://forum.eset.com/topic/40539-1719/" target="_blank">[3]</a><a href="https://forum.eset.com/topic/40551-eset-causing-issue-for-using-protonvpn/" target="_blank">[4]</a><a href="https://forum.eset.com/topic/40522-eis-17190-and-internet-slowdown/" target="_blank">[5]</a>. Disabling it is the recommended workround, and I ran into some issues with it as well with pages breakings and general slowness while browsing.</p><p></p><p>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.</p><p></p><p>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.</p><p></p><p>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.</p></blockquote><p></p>
[QUOTE="cofer123, post: 1081957, member: 92976"] The Network Inspector change is, in fact, [URL='https://forum.eset.com/topic/40544-version-17190/?do=findComment&comment=182373']the removal of Radar View[/URL]. 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) [URL='https://forum.eset.com/topic/40431-nod32-17190-not-allowing-vpn-to-connect/#comment-182362'][1][/URL][URL='https://forum.eset.com/topic/40527-eis-17190-and-http3-scanning/'][2][/URL][URL='https://forum.eset.com/topic/40539-1719/'][3][/URL][URL='https://forum.eset.com/topic/40551-eset-causing-issue-for-using-protonvpn/'][4][/URL][URL='https://forum.eset.com/topic/40522-eis-17190-and-internet-slowdown/'][5][/URL]. 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. [/QUOTE]
Insert quotes…
Verification
Post reply
Top
