As for NSSM, it's detected / classified as a potentially unsafe app which is correct. It is not detected with default settings. If you use it for legitimate purposes, you can add it to detection exclusions.
As far as nssm.exe, I would be leery of it regardless of where it is located. As noted here: http://www.herdprotect.com/knowledgebase_resource.aspx?sha1=548eba9213b1d5b74df061ab755bda3d4cfb56b9 , 14 AV's detect it as malicious.
« The problem is that with each update, there is a different element in the process path, so there is an alert to each VPN update. ». I cannot...
Again in regards to nssm.exe: https://www.file.net/process/nssm.exe.html I again see no legit reason why Surfshark updating should be running nssm.exe from the %Temp% directory. Nssm.exe is an extremely potential dangerous process since it allows for creation of Win services outside of normal Win service installation processing.
I agree with this. If it is malware then it is malware. If it is not then this process is so poorly executed that it might as well be. I would refuse to let anyone I work with install this.
Version 14 seems to be on the pre-release channel. According to Marcos it will be released on the regular update channel in a few days. https://forum.eset.com/topic/25632-eset-internet-security-14-version-release-date/ (Scroll a bit down there in that thread). I would suggest that we start a new thread when it is on the regular update channel; called: ESET Windows home products version 14 Thank you.
I used to as well, until I tried to uninstall it! It took me over a week, with many posts, trials and errors, and much searching to finally get rid of all vestiges of Eset off my computer. Even now, several months later, I'm still paranoid that parts are still lingering. It totally messed up my firewall and the ability for Outlook to access the internet. I had planned on installing Norton 360 in it's place, but I haven't yet done that. For now, I'm only using Windows Defender as everything appears to finally be working ok. I'm paranoid now to install Norton 360 or any other AV, because of fear of what I went through with Eset. Edit: In fairness, I should add that uninstalling Eset off my wife's computer worked with no problems or issues. I was so worried that it wouldn't, which kept me from trying it for quite a while. But, her license expired and it was either renew it (which I was not going to do) or eventually uninstall it. Thankfully, uninstalling Eset off her computer went very smoothly.
Did you use the ESET's uninstaller tool? It removes all remaining traces after you've manually uninstalled ESET products. I highly recommend running the vendor's uninstall tool, after uninstalling any antivirus, unless they do no provide one.
Yes, actually, multiple times. While it removed all the traces, it left my windows firewall corrupted. Then, I was left with trying to figure out how to fix my windows firewall. Even though all traces of Eset were gone, windows firewall kept reporting that it couldn't work due to Eset controlling the firewall (or something like that).
Yes, absolutely. But, going back to an image with Eset installed was not an option as my license for Eset had run out. That would have just ended up with me either having to now purchase another license for Eset (which I didn't want to do as I had already purchased a license for Norton 360) or going through the uninstall process all over again (and just probably end up back at the same point).
If ESET did not uninstall cleanly and the removal tool did not fix your issues... I have had luck in the past with reinstalling ESET again and then uninstalling. It might be a good idea to create an image first in case it causes more problems that it solves (always a possibility with anything) but if things are still broken it is what I would try next.
When Eset is uninstalled cleanly, it will un-register itself in Win 10 Security Center. At that point, the Win 10 firewall and Windows Defender should be what is shown in Windows Security Center as the active firewall and real-time AV solution. If NOD32 was installed initially, this would have no effect of the Win firewall since it would remain registered in the Win Security Center. Only an Internet or Smart Security install would result in them being registered in the Win Security Center. Most Windows Security Center issues arise when the initial Eset install for some reason; there a multiple ones, doesn't register itself properly in the Windows Security Center. This is the first thing one needs check after an Eset installation; that it is registered as the real-time AV solution and firewall if applicable.
They've released a video announcing new version on FB: https://www.facebook.com/eset/videos/1034687760327098/
If you're on per-release updates and have ver. 14 installed, "strap on your seat belts." Gory details here: https://forum.eset.com/topic/25900-...y-center/?tab=comments#elControls_122500_menu
I had v14 and pre-release updates but as my license will expire soon and I make daily incremental backups I am just going to give up on paying for AV software and having the issues related to it. I wasn't having any major issues with the v14 I had installed but if this turns out to be a bigger issue I'm glad I missed it.