Jeroen1000

Sorry, I had missed that solution! I've tried it and gave it a test run and it looks like the dectections are no longer happening. Many thanks!

Hi Marcos any idea as to when you can expect news on this topic?

Any more ideas? I'm not looking forward to using other software for this small issue. Can't the virus definitions be corrected?

Hi Marcos, I've excluded a whole bunch:-) see the 2nd screenshot. But the startup-scanner keeps complaining (see the 1st screenshot).

I think it is properly excluded however, I cannot exclude things from operating memory. I can give you remote access to check for yourself in case I missed something.

Thank you Arakasi. I'll check what exactly it is being flagged as, as I thought it was being flagged as "unwanted" rather than as "unsafe". Do note it is flagged in Operating Memory and not whilst downloading although I can easily try downloading it again and see what happens. The application is quite safe, I've been using it for many years. The offending executable is called "rserver3.exe" with the file path in the "SysWOW64/rserver30/" folder (don't know why there is a path when the exe is in operating memory). So you need radmin server and not the client application. It might, and I say might, be flagged because I have a version that does NOT display a tray icon (not for the wrong reasons:-)) edit: flagged as unsafe indeed, not unwanted! You were right

Dear Marcos Dear support, Since we are going around in circles with the ticket, I was wondering whether you could offer a more in depth explanation / analysis on the matter and also a solution. I'm using Radmin (hxxp://www.radmin.com/), a remote control utility, that NOD32 keeps detecting as a potentially unwanted program. It states the threat is in the Operating Memory (which is correct, the executable is loaded as a service on start-up). I've excluded the detected exe at disk level but that does not help as it keeps detecting it in memory. Support is suggesting disabling detection for unwanted programs as a whole and even adding the system folder to the exclusions list. Neither is satisfactory and bluntly put just bad advice from a security perspective. There has been a time the manufacturer got Eset to remove this false detection but apparently it is back. I've been a paying customer for a very long time. Surely, you can remove this "threat" from being detected or fix the virus defintions? Many thanks, Jeroen