Jump to content

LarryF

Members
  • Posts

    5
  • Joined

  • Last visited

Everything posted by LarryF

  1. This morning I installed NOD32 V10 over V9 on a Windows 10 system with all available updates installed. I let the initial scan run to completion, watching the paths of the files it was scanning. And I noticed that in several cases the same directory was scanned multiple times, an apparent bug. NOD32 is treating links to directories as if they were the actual directory. The four paths C:\Documents and Settings\myusername\Documents C:\Documents and Settings\myusername\My Documents C:\Users\myusername\Documents C:\Users\myusername\My Documents to the same directory each resulted in scanning all of the files in that directory four times, as did the two paths C:\Documents and Settings\myusername C:\Users\myusername result in all of the files in that directory being scanned at least twice. The "Documents and Settings" and "My Documents" are links to other directories on the same drive, and each of those only needs to be scanned once. Similarly, other paths which are links to directories on the same drive should be skipped. Scanning these directories multiple times resulted, of course, in the initial scan taking much longer than necessary. Larry
  2. I had another instance of the tray icon not showing, and the procedure in the quote of my previous post above worked just fine to get the icon back. And just to be clear, the problem that I am seeing is not related to the issues covered in the ESET FAQs or KB article. Larry
  3. I think ESET is aware of the issue, as Marcos has posted in this thread. I have also had the missing tray icon once since I last posted in this thread, but did not discover the following until I had rebooted the next day and the tray icon was back. I think I have found a way to get the tray icon back when it is missing. Egui.exe resists being killed from Task Manager or Process Explorer (access denied), but you can end the running instance that is supposed to provide the tray icon (at least when running Windows 7) by opening a command prompt window and entering "taskkill -im egui.exe" (without the quotes) and then responding Yes to the prompt "Are you sure you want to quit ESET NOD32 Antivirus?". Now if you restart egui.exe from the Start menu (Start, All Programs, ESET, ESET NOD32 Antivirus, ESET NOD32 Antivirus), the tray icon is created. Larry
  4. Just for completeness, my NOD32 tray icon is now showing, after a reboot. But apparently, when egui.exe is running (hidden) and the tray icon is not showing, something is not working correctly in the code that periodically tries to detect if it is there and to create it if it is not. Since this happens fairly infrequently, I guess no one at ESET has ever seen it happen. The next time I see it happen, I'll try using SysInternals Process Monitor to see if I see anything interesting. I could also try attaching a debugger to the process, but lacking any symbols I doubt that would give me anything useful. Larry
  5. I am currently having the same missing tray icon on one of my systems (Windows 7 Ultimate 32 bit fully updated). In my case when this happens, egui.exe is running (started from the registry, with arguments "/hide /waitservice" according to SysInternals Process Explorer), but the icon is not showing. The Notification Area Icons settings are correctly set to show the icon. As a Windows developer of a company internal program which runs on thousands of Windows computers and uses a tray icon, I learned over the years that the Windows function which creates the tray icon (Shell_NotifyIcon()) may fail during Windows startup, and the failure is apparently due to the amount of startup activity going on at the time. To ensure that I can almost always create my tray icon I check the return code from that function, and on failure wait three seconds and try again, up to five retries. Since modifying my code in that manner I have had no further reports of my tray icon not showing. Perhaps is the ESET developers are not using such a technique they could modify their code in a similar manner. It's the sort of change that can't hurt anything regardless of whether that is the real problem. Larry
×
×
  • Create New...