ESET Windows home products version 13

Basically it's enough to download the uninstall tool and run it in safe mode. However, it's recommended to back up your network interface settings first by running "netsh interface dump > netcfg.dat" in case network issues occurred after running the tool. The interface configuration could then be restored by running "netsh exec netcfg.dat".

 

Absolutely follow these instructions. Though it is rare for there to be any issues I have experienced them personally. I didn't know to do this at the time and if I hadn't had a second working PC to download and copy files from it would have been impossible to fix until I had access to a working PC. If you have system restore enabled it might be a good idea to create a restore point before doing this.

 

I do take daily images with Macrium Reflect. So, I can go back to before I uninstalled Eset, but I'm not sure what that will ultimately accomplish as my Eset license has expired. My intention was to either go with Windows Defender or install Norton 360 (I purchased). I did use Windows add/remove programs (or apps) to uninstall Eset, so I'm not sure why this has happened.

 

I was a bit surprised when I received a notification from this site today linking to a conversation and I get a warning from ESET that this is a malicious site when I clicked the link. False positives are rare but I have to wonder why they seem to suddenly think that links to this site in an email are dangerous. I'm too lazy today to post on their forum and it's not a huge deal but I found it odd all the same.

 

I am going to try and duplicate this. Reply to this posting.

 

Test

 

Testing

 

No problem with Eset blocking the e-mail link.

Now I do use Thunderbird e-mail client. Maybe Eset already removed the FP?

-EDIT- Also tried web mail. No problem with Wilders link blocking.

 

I have used the Eset uninstall tool and I ran it in safe mode. After doing so, I am still having firewall issues. Therefore, I ran it again. This time, it stated that I had no Eset programs on my computer. According to the instructions for the uninstall tool, it states the following:

If you continue to experience issues..., delete the ehdrv driver using device manager and then repeat the steps above to run the ESET Uninstaller application again. Since ESET is designed as a security application, in some instances multiple attempts are required to uninstall the product completely.
​

I cannot file the ehdrv driver either in My Computer or in Device Manager (as recommended in the above link). And, the MS firewall diagnostic cab utility also still states that Windows Firewall cannot be made the default firewall because of ESET being installed. I am open to other ideas?!

I have submitted a support ticket via ESET's website. My ESET license expires tomorrow.

 

Did you check for in C:\Windows\System\Drivers and delete it from there as noted in Section I of the Eset KB article you linked to? If it doesn't exists in the Drivers folder, then the Eset uninstaller removed it from there.

What I suspect is there might be remnants of another AV you previously uninstalled and wasn't fully removed. This is what is preventing Win Security Center from now registering WD as your your active AV. Eset has an AV remover utility you can try to run and see if it detects and other AV installations present: https://support.eset.com/en/kb3527-...applications-and-instructions-to-run-the-tool

 

I can't duplicate it at this point. I assume it didn't last long.

 

I did not find that driver in C:\Windows\System\Drivers and I could not find any heading or category in Device Manager called "non plug and play drivers". That folder or category doesn't exist in my Device Manager. So, I couldn't find it there; though I looked through all of the other headings/categories.

I will try that in the morning. It's late here now. Thank you for your assistance and willingness to give me suggestions/ideas.

I will mention that the program found here: https://antivirus-removal-tool.com/ does show that ESET is still installed. Yet, when I click on "add/remove programs" there is no listing for ESET. (Is it possible that ESET could be listed in "add/remove programs" within Safe Mode?)

Finally, the Windows Firewall Diagnostic tool found here: https://support.microsoft.com/en-us...agnose-and-fix-problems-with-windows-firewall still shows this when I run the file:

 

The only thing that this tool found was VoodooShield; which is not a supported application. In other words, it can't or won't do anything with VoodooShield; which is fine.

(This is probably a crazy thought, but is it possible that VS or Whitelist Cloud is somehow hooking into the firewall and causing this? I guess I could uninstall it and see.)

 

Here is a picture of my Device Manager. No "non plug & play" devices:

 

Here is what I have:

 

Try using Revo Uninstaller to clean out any remnants left by the Eset uninstall.

My best guess is there are registry remnants left which is making the OS believe that the Eset firewall is still installed.

 

Version 13.2.18.0 released

I got it offered via the internal updater (on regular release channel).
Reboot required as usual.

Changelog
No changelog as for now, as far as I know.
https://www.eset.com/int/home/internet-security/download/
No changelog there as for now, but the full off-line installer looks to be available there, and that site does mention version 13.2.18.0
(go to the advanced download option there)

Not yet mentioned at the ESET forum https://forum.eset.com/
I guess that will come later.

 

During the upgrade/install via the internal updater I got a bit strange error message from Eset Internet Security on my Win 7 Pro 64-bit:
"26-8-2020 14:32:03; Device control; An error occurred during installation of the edevmon driver.; SYSTEM"
This was before I rebooted. After the reboot there was no more such an error message.

Anyone have any idea about this? Thanks in advance!

I think that I'm going to do the following and see what will happen then.
I have already downloaded the full off-line installer.
I'm going to put back a backup-image from yesterday (thanks Macrium!).
And then using that new installer for 13.2.18.0 (while being off-line) install it over the top of 13.2.16.0
It will be interesting to see what will happen then.

 

Thanks FanJ just updated my home machine. I did not receive the error as you did but I am on Windows 10.

I think ESET is dropping support for Windows 7 by the end of the year yes?

Sounds like a good plan for your issue. If that does not work maybe go for the old uninstall/reinstall routine.

 

I just installed this. When it gave me the option to explore new features there was a dot on Tools that took me to the Connected Home Monitor. I have to assume something has changed there but I guess we'll see when they release a changelog.

 

In the meanwhile I did what I described. Same error in the Eset event log. And after the reboot no more such an error (which is also the same as I noticed when I upgraded via the internal updater).
I don't know why it happens, having upgraded now in two different ways on Win 7.
What exactly this edevmon driver does, I don't know.
I looked at C:\Program Files\ESET\ESET Security\Drivers\edevmon\edevmon.inf but for now that doesn't seem to tell me much.

 

I don't know about that. If someone could tell more about that, then please by all means!

 

If someone finds the changelog, if and when it will be released, then please let us all know (with links). Thanks much!