Sammo
-
Posts
51 -
Joined
-
Last visited
-
Days Won
2
Posts posted by Sammo
-
-
I have not been able to connect to the LiveGrid or get updates for several hours. Are the servers down?
-
40 minutes ago, itman said:
As long as you have the patch, you can't be at least exploited by this SHA1 vulnerability.
Thanks, that's good to know.
-
I have Windows 10 and got the patch but I still get this test failure. 😒
-
5 hours ago, itman said:
Correction - this is not a cipher issue but an Eset root certificate issue. Looks like it still accepts SHA1-intemediate certificates.
Can be verified by disabling SSL/TLS protocol scanning. Then the badssl.com SHA1-intemediate test passes.
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?
-
On 11/25/2019 at 9:22 PM, Marcos said:
Do you have v13.0.22 installed? Have you tried uninstalling it and installing it from scratch? Should the problem persist, please provide screen shots to demonstrate the issue you are having. Besides that I'd recommend raising a support ticket with customer care so that the case is tracked and dealt with properly.
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.
-
5 hours ago, itman said:
There is one thing I am confused about here.
I assume that license was used initially a while back to install EIS. As such, an Eset account would have been established on the Eset registration servers reflecting this license. The OP would have also received an e-mail confirmation. All the above indicates the license was accepted as valid at that time?
Yes, the license was accepted several months back when I first installed it and again when I reinstalled it three months ago.
-
1 hour ago, itman said:
Based on the responses to date on everyone who has installed ver. 12.2.30, you do seem to be the only one still having an issue.
You might try installing ver. 12.2.30 stand alone after uninstalling ver. 12.2.29. Make sure you export Eset settings first if you have made customized settings and/or rules. You can then import those after 12.2.30 is installed.
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!
-
6 hours ago, itman said:
What ver. of Win 10 are you running?
If this was a "bug" per se, everyone with Eset 12.2.29 installed would be receiving the Windows Security Center notification which is clearly not the case. This leads me to believe that on select Win 10 installations, there is something not right with Security Center's initialization processing at boot time.
Using Control Panel -> Administrative Tools -> Services, make sure the Security Center service Startup type is set to Automatic(Delayed Start) as shown in the below screen shot. Additionally noted per the description given is that this service is heavily dependent upon COM for third party AV and firewall registration. If that Win feature is corrupted in some way, that also could be the problem.
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.
-
10 hours ago, itman said:
Not really surprised to hear this. I never had the issue with the Win Security Center popup notification; prior to 12.2.29 or with 12.2.29 installed.
Try running the Win 10 image integrity utility from an admin level command prompt window at see if that helps:
DISM /Online /Cleanup-Image /RestoreHealth
Note that this will run for some time. Also, an additional OS verification utility you can run from admin level command prompt window is:
sfc /scannow
This will check the integrity of all OS system files. This also runs for some time.
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.
-
13 hours ago, Marcos said:
V12.2.30 with fixes is available in the Early access download section for download: https://forum.eset.com/files/category/3-early-access/
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! 😀
-
6 hours ago, itman said:
This is a long known Win 10 issue caused by Windows Security Center not properly initializing and the issue has nothing to do with Eset being installed. It has manifested when Windows Defender was the only AV installed.
This old fix shown below appears to be no longer available since Microsoft has locked down these service settings in later Win 10 versions. The same could possibility be done by modifying the associated service start value setting in the Registry. But, that also might be locked down.
What you might try doing is uninstalling Eset and see if the alert disappears with only Windows Defender running. If so, then reinstall Eset and hopefully the issue is resolved.
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.
-
2 hours ago, itman said:
This is what I referred to previously as far as Quantum ver. 68 goes. What FireFox is informing you of is Eset is not a recognized root CA certificate issuer which obviously it is not.
If you were to see this same wording for an Eset non-SSL protocol filtered web site, then that would be cause for concern.
Thanks
-
This is nothing to be concerned about is it?
-
On 7/4/2019 at 10:05 PM, hulduet said:
I can confirm this issue. It started a few days ago. I am unable to delete the content of the sandboxie because something is stopping the deletion(ESET). Very easy to reproduce this problem by just having sandboxie and ESET together since a couple of days ago.
Same problem with me. I use Privacy Eraser and that will delete the sandbox contents.
-
6 minutes ago, BeanSlappers said:
It is indeed.
Try changing it's scanning option from Auto to Scan.
-
2 hours ago, Azure Phoenix said:
Did you checked if uBlock isn't blocking part of the website? Perhaps that's the reason why ESET isn't detecting phishing there.
I fixed the issue by changing the SSL scanning option from Auto to Scan. Now Eset detects phishing sites and malware just fine.
Eset LiveGrid and Update Servers Down?
in ESET Internet Security & ESET Smart Security Premium
Posted
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. 😀