Using

We have got license for ESET product in HOME product family. However not able to contact ESET as their contact form https://www.eset.com/int/support/contact/ does not accept my e-mail address which is in my own private domain within .online TLD. Does ESET read this?

Well there is ESET KB article with more details kb3509. SysRescue was tested under Windows 10 but still not officially released, some issues might arise during use. Not exactly stated there if Live USB/CD Creator affected too.

Live CD/USB creator download page claims the creator was for Windows version up to 8.1. Really not compatible with Windows 10? No hints in user guide.

I invested in purchase of the 5 years duration license pack for up to 5 devices each device of any platform and os type. I use two of them on Linux however regretting this invest as Linux version of NOD32 receives highly infrequently updates and it is unclear how well can Linux version detect threats in file formats typical for Windows platform (executables, other binaries, Microsoft Office documents, other). Scanning files for Windows on my Linux machines is major use-case. There is also great debate in public on efficiency, conflicts with Windows native design of AV solutions generally, this regarding my invest for Windows based machines.

I know Vista is end-of-life and this topic quite vantage. I have migrated to current Windows version, and Vista had been converted to virtual machine (isolated from I-net and got rid of software showing extraordinary frequently security gaps) just for the case user will like to have a short look how some stuff was used, was running, looked like in the days as regular/production job was done on Vista. Problem described in this thread is not solved. Unfortunately all hints given here miss the problem. So i like to reword the issue once again. Usually when someone starts the on-demaind scan some kind of NOD32's graphical feedback comes up on screen. Here in this case such feedback is missing. No feedback received confirming that NOD32 conducts the ordered scan. Additionally NOD32 icon in system tray is not present (from OS start time on), even it is not under hidden system tray icons. If to proceed in following way and sequence the on-demand scan works fine: start the on-demand scan (as always - from file's to be scanned contextual menu) then start ESET gui from Windows Start Menu.

I know Vista is end-of-life and this topic quite vantage. I have migrated to current Windows version, and Vista had been converted to virtual machine (isolated from I-net and got rid of software showing extraordinary frequently security gaps) just for the case user will like to have a short look how some stuff was used, was running, looked like in the days as regular/production job was done on Vista. Problem

Thanks for your input. Actually my concern is quite different. Please accept my apologize for not been accurate enough. I afraid NOD32 for Linux operating on Linux does not conduct real scan if the file is an exe (executable built for Windows). This conclusion raised from observation that a tarball file of same size takes significantly longer. Put in other words, for instance to apply any kind of heuristics on Windows exe files NOD32 needs to emulate Windows environment in some extend. If I am right (???) it is a question of feasibility.

The behavior described below have being observed since Ubuntu 14.04 LTS and keeps to exist with Ubuntu 16.04 LTS. Described behavior is encountered only while NOD32 AV for Linux Desktop is installed, 4.0.82. Used setup is a Ubuntu virt. machine running on VirtualBox or VmWare Fusion, in both cases problem reproducible. After the OS shutdown have been initiated by user from Ubuntu gui or from shell frequently OS needs very long time to complete shutdown, it seems to been got stuck in Ubuntu shutdown screen. How to fix it?

This or quite similar behavior encountered last few days after had applied updates (security, recommended updates) to OS Ubuntu 16.04.1 LTS. Plenty of "socket read" errors in syslog. OS (a virt. machine) poorly responsible. Got rid of these problems by uninstalling NOD32 for Linux. Since that removal no AV solution installed till now.

This machine is provided with latest updates. If it was an issue of hidden system tray icon why the start of on-demand scan does not result in any reaction too, no sings of on-demands scan start got, see initial post? As mentioned on-demand scans work if to start nod32 from start menu in prior of this. If ESET service was not running would this work?

NOD32 AV does not auto-start after had completed the upgrade from 8.x to 9.x. Currently the last official 9.x release installed. Host OS is Vista 32 Bits. Before the upgrade NOD32 AV auto-started without any problems. Use could interact with it via the system tray icon. Now the icon is not there. Furthermore, if to invoke on-demands scan for some file(-e) or folder(-s) by file/folder right-click NOD32 AV does not give any signs of life. All is fine if to start NOD32 AV manually from Start menu, also on-demand scans work in that case. Please help.

Is it a good, or just in opposite, a bad idea to scan exe files (executable binaries for Windows family platform) using the Linux version of NOD32 AV? One can see that such scans take a tiny fraction of one second (unable to observe the scan in progress) while a scan of tar ball of similar size needs noticeable time.

To be honest it's not the user's concern where the reason is placed. Can not follow back in short time what the use case were. However, we can remember the feature had to be disallowed cause to often the addressed issue as obstacle in daily work.

I guess once in the past, yet in the days of 7.x or 6.x major version of ESET security products for home user there was an issue with SSL protocol filtering and Firefox. An issue in that way both together did not comply. So in the end effect for users who use Firefox as standard browser the SSL protocol filtering was practically useless. How does it look today in this regard? I mean if to take ESET security products with 8.x major version for home users and Firefox/Thunderbird of current official builds. Still not compatible?

Thank for your hint! Is this the best solution for these probs? Unfortunately no signs in the web of similar probs on pc's of other jzip & nod32 users? Are we alone?