itman
-
Posts
12,200 -
Joined
-
Last visited
-
Days Won
321
Posts posted by itman
-
-
12 hours ago, geetee said:
And can anyone tell me what the RS Voluum A. is as I have tried to look online and I think it appears to be an ad tracker
Correct. Voluum is ad tracking software.
When you added the uBlock Origin extension, it blocked the ad from being displayed on the web page. Additionally, UBlock Origin uses a default TPL that can detect and block voluum.com attempted access; refer to this posting: https://forum.eset.com/topic/37661-jsvoluuma-pop-up/?do=findComment&comment=171600 .
If no further Eset alerts occur with the uBlock Origin extension installed, your problem has been resolved.
-
If you still get the Windows installer error w/Eset uninstalled, refer to this article: https://medium.com/@windows10help/how-to-fix-windows-10-installer-error-1601-6fc92be4a2ac .
-
21 hours ago, Hardq said:
If you have any questions or require further clarification, please don't hesitate to reach out.
Referring to this alert, do you have a HIPS rule that monitors child process startup from PowerShell? If this is the case, you will have to exclude conhost.exe since a number of Win internal maintenance PowerShell scripts invoke conhost.exe.
-
Another recent posting on this issue here: https://forum.eset.com/topic/39433-antimalware-scan-interface-amsi-integration-has-failed-endpoint-11020320/?do=findComment&comment=178892
-
On 1/16/2024 at 12:32 AM, thoraxi said:
went to microcenter and they told me I had to buy these keys for my pc so it can be secure but they gave me two
Unless things have changed, MicroCenter offers their PC purchaser's a free one year license for either NOD32 or Eset Internet Security: https://store.eset.com/us/offers/mc/ . If this is still their policy, I would discuss with the store manager why someone sold you a license for Eset.
-
1 hour ago, Marcos said:
As far as applying these updates, use the following links;
https://www.catalog.update.microsoft.com/Search.aspx?q=kb4474419
https://catalog.update.microsoft.com/search.aspx?q=4490628
Download the KB4490628 update first since it's the service stack update and needs to be installed prior to the KB4474419 update.
The main question is if these updates will install w/o issue on the Win 7 Superlight ver.. I assume they will.
-
On 1/14/2024 at 10:01 PM, Peaceful guy said:
I was using essp till yesterday on my windows 7, but when I re installed the superlite version of windows 7
I am getting the error
Appears the ver. 16.0.28 installer does support this Win 7 non-standard ver..
-
More info on this ransomware here: https://www.bleepingcomputer.com/forums/t/771041/rcru64-ransomware-idid-random-6-mailemailrandom-4-support-topic/ . If anyone can come up with a decryptor, this would be the place. At present, appears no one has been able to do so.
-
2 hours ago, cleiton santos said:
So this alert, isn't important at all?
It depends on if you purposely disabled the Windows firewall on all your network endpoint devices which is doubtful.
-
Assumed here is your endpoint devices are using the Windows firewall since Eset Endpoint AV does not contain a firewall?
Also assumed is WSC most likely is warning that the Windows firewall is not running on your endpoint devices for some reason. This can be verified by opening WSC on one of the endpoint devices and then opening Virus & threat protection. Next, mouse click on "Manage providers" which will show current device firewall status.
-
5 hours ago, JohnnyMusso said:
Procexp - Shows the process is running
Who is the parent process? Ekrn.exe?
-
2 hours ago, 100 said:
itman mentioned the port 8888. On the linked page it is 8883, but that is probably because they are different products.
It was a typo on my part. I corrected my above posting to show 8883.
-
15 hours ago, Glassertje said:
In Chrome i get a warning from Chrome itself, but not from ESET. In Firefox if i ignore the warning of Firefox, the website is blockt. No idea what the difference is.
It appears Chromium based browsers interface with Google Safe Browsing differently than done in FireFox.
In Firefox, Safe Browsing detection causes Firefox to display a full red web page alert with option to Go back or override the warning. Perhaps the override causes another full domain lookup which then allows Eset detection to process correctly.
-
12 minutes ago, hobbitman said:
in my chrome and pc, not blocking
Well, Chrome is detecting it. Notice the "Dangerous" tag prior to the domain name?
Might be an issue with Eset phishing detection "kicking in" on a Chrome connection override situation.
-
Do you have Sticky Keys option enabled?
-
Google SafeBrowser detects the domain in Firefox and I assume also in Chrome.
-
Also, I tried to run the script. As the below screen shot shows, the script has a syntax error and will not run;
I have to believe that this PowerShell activity at system startup is being created by something else.
-
1 hour ago, Marcos said:
I prefer using SSL Labs' checker which is most reliable according to my experience
Here's what's weird. Using both Firefox and QUALS SSLab Server test, windows.dns.nextdns.io would not resolve when I originally tested. Now, both have no issues.
-
On 12/29/2023 at 12:28 PM, JohnnyMusso said:
"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" -NonInteractive -Command if (((Get-AppxPackage -Name 'EsetContextMenu').length -ne '1') -Or ((Get-AppxPackage -Name 'EsetContextMenu').version -ne '10.39.34.0')) { Get-AppxPackage -Name 'EsetContextMenu' | Remove-AppxPackage; Add-AppxPackage -Path 'C:\Program Files\ESET\ESET Security\EsetContextMenu.msix' -ExternalLocation 'C:\Program Files\ESET\ESET Security\' }
It appears the PowerShell command is removing an existing AppxPackage ver. of EsetContextMenu.msix and replacing it with a new ver. of the same.
This might have been created to be run as a run once maintenance activity by Eset at system startup time and then be removed. It appears the removal activity got borked in some way and the command is running at each system startup plus not terminating itself.
Suspect there is a scheduled task that is performing this activity. Or, a registry run key is the source for the activity.
-
6 minutes ago, Marcos said:
Name: steering.nextdns.io
-
Quote
windows.dns.nextdns.com.io
This is not a valid domain name. It won't resolve in Firefox or any of the SSL server validation web sites I tried.
-
Appears you purchased a boxed version of Eset. Standard retail practice with boxed software is once the box seal is broken, the software is not returnable for a refund. However, the assumption here is that the software is usable in that it can be activated and the license has not expired.
Eset can't help you in this matter since you did not directly purchased the software from them. Your only recourse here is to escalate the issue to the retail store management. If they still refuse the refund and you purchased with a major credit card, you can dispute the purchase with the credit card issurer.
-
On 12/30/2023 at 6:05 AM, Alasedo said:
i restored Eset firewall settings to default state and enable Interactive mode again. My all firewall rules removed. And after system boot back to normal.
Let's refer back to this posting.
I also had Eset firewall issues when upgrading to ver. 17. They didn't cause this black screen issue; but other problems. All my issues were resolved by resetting Eset firewall rules back to default settings which of course, wiped out all my custom firewall rules.
Now as far as I am concerned, the issue isn't directly related to the ver. 17 upgrade; rather the ver. 16.2 upgrade with the problems surfacing in the ver. 17 upgrade.
After the ver. 16.2 upgrade, I observed that the Eset default rule ordering had changed. Most notably, the first 6 rules or so. Since these are default rules, there was no way to revert to the normal default rule ordering other that a full firewall rule reset to default which I did not do since I didn't want to lose my custom rules. Also, export and import of rules did not fix the issue. All this was very odd to me, but I did not report the issue in the forum.
-
14 minutes ago, Marcos said:
Does temporarily pausing or disabling the ESET firewall in the advanced setup make a difference?
I'm not having or ever had any issues in this regard. I just posted one way to try to diagnose the issue.
Additional refs. on the subject here:
https://www.techtarget.com/searchenterprisedesktop/tip/Steps-to-fix-a-black-screen-in-Windows-11
https://www.windowscentral.com/how-fix-black-screen-problems-windows-10
Neither article mentions AV software as a possible sourec.
Activation Failed "ECP.4096"
in ESET NOD32 Antivirus
Posted
Try this;