Daedalus

If you click on the question mark top right you get to this page: https://help.eset.com/eis/12/en-US/idh_config_devmon.html

Thunderbird is not supported. https://support.eset.com/kb2138/

You should actually go back to version 9 to be in an supported situation from ESET: https://support.eset.com/kb358/ https://support.eset.com/kb3678/ Older versions: https://support.eset.com/kb2885/

Maybe not advisable but I would very much welcome such a feature. I have had my firewall in interactive mode but for example Microsoft often only tell you the FQDN's that need's to be reachable instead of the IP ranges. So you keep editing the firewall rules.

See this KB article: https://support.eset.com/kb2138/

Also Win 10 Pro: https://docs.microsoft.com/en-us/windows/deployment/update/waas-servicing-channels-windows-10-updates And it is up to 365 days regarding the delay option (feature updates): https://www.thewindowsclub.com/delay-the-windows-10-anniversary-update (security updates is 30 days)

You can delay the updates a bit read this: https://blogs.technet.microsoft.com/surface/2017/07/28/the-windows-semi-annual-channel-and-targeted-deployment/ See also this schedule: https://www.microsoft.com/en-us/itpro/windows-10/release-information

There are two more commands that you can run to see if there is any system file corruption: sfc /scannow and after that DISM /Online /Cleanup-Image /RestoreHealth https://answers.microsoft.com/en-us/windows/forum/windows_10-update/system-file-check-sfc-scan-and-repair-system-files/bc609315-da1f-4775-812c-695b60477a93

This is why you should have back-ups...

I would suggest to use something else other than Daemon Tools: hxxp://www.tomsguide.com/answers/id-3569486/daemon-tools-virus.html

Windows XP is not supported anymore since version 10.x https://support.eset.com/kb358/?locale=en_US

You can see if OpenWRT does support your router: https://openwrt.org/toh/start And if so maybe install that on your router. I am using it too, works fine!

Maybe it is worth the try to uninstall ESET in safe mode using the Uninstall tool and try installing it from scratch.

It could also be your TP-Link router see this link for an list of impacted routers: https://www.tomsguide.com/us/vpnfilter-router-malware-check,news-27545.html You can also run this test: hxxp://www.symantec.com/filtercheck/

Make it possible to use FQDN in Firewall rules. I saw an post from a while ago that it would not be possible but see the following link, it is: hxxp://help.fortinet.com/fos50hlp/54/Content/FortiOS/fortigate-firewall-52/Firewall Objects/Addresses/FQDN Addresses.htm