Sammo

It might just be a coincidence, but I just restarted the router and all of my devices and Eset is just fine now. Updates and LiveGrid connect okay. 😀

I have not been able to connect to the LiveGrid or get updates for several hours. Are the servers down?

Thanks, that's good to know.

I have Windows 10 and got the patch but I still get this test failure. 😒

Thanks! Will this be addressed in future updates to EIS?

Thanks for the reply. I have created a registry entry with the value of 0: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Hashes\SHA This has made no difference. It must be related to the browser as when I use a vpn I don't get this insecure connecton.

This happens with all of my browsers at the Dashboard on badssl.com How can I set Eset to block this kind if connection?

I fixed the issue. I had a different AV last year and Windows Defender would not turn off. I created registry entries to disable it and had forgotten this. After removing those entries I no longer get that error message. 😀

I am still getting this error with Windows 10 64 v1909.

Yes, the license was accepted several months back when I first installed it and again when I reinstalled it three months ago.

Man, I am one unhappy camper right now. I uninstalled Eset, rebooted and reinstalled it. Now I am totally unable to activate it at all. I keep getting erro code ACT.33. I have 2 1/2 years left on my license I purchased from Amazon. I need this fixed ASAP!

I have the latest Windows version 64 bit. See attachments. Everything is as it should be. Also, I am not the only one here that has this exact same issue.

Nope, doesn't work. I tried these steps twice, no joy. I only get this notification with Eset installed, no other security app. It's clearly a bug in Eset. Please fix.

Didn't work. Still getting the same notification as before.

Is anyone from Eset going to get us answers?

I have the exact same issue. It's really annoying.

I'll probably just live with the issue. I already tried uninstalling and reinstalling Eset. Didn't make a difference. As for the Security Center service startup, it can't be changed anymore because it is greyed out. Damn Microsoft! 😀

It's now grayed out by Microsoft, but it is set at Automatic (delayed start).

When I open Security Center it does show Eset as active. As long as it's working is all that really matters. Just a bit annoying though.

Every time I boot my computer this notification shows up after about 5 minutes. I can verify that Eset is indeed working just fine but it is really annoying anyway.

Thanks

This is nothing to be concerned about is it?

Same problem with me. I use Privacy Eraser and that will delete the sandbox contents.

Try changing it's scanning option from Auto to Scan.

I fixed the issue by changing the SSL scanning option from Auto to Scan. Now Eset detects phishing sites and malware just fine.