cutting_edgetech
-
Posts
336 -
Joined
-
Last visited
-
Days Won
3
Posts posted by cutting_edgetech
-
-
I keep getting this alert, "Antimalware Scan Interface (AMSI) Integration has failed. Antimalware Scan Interface is not integrated into your system. This means that Powershell Scripts and Scripts executed by Windows Script Host will not be scanned for malicious content".
It occurs shortly after boot. I have to reboot Windows to fix the issue each time.
I'm using Eset Internet Security 17.0.15.0 on Windows 10 Pro x64
My Windows Stats Below.
Edition Windows 10 Pro
Version 22H2
Installed on 5/28/2023
OS build 19045.3693
Experience Windows Feature Experience Pack 1000.19053.1000.0
-
10 hours ago, itman said:
It would have helped if you originally stated you had set the Eset GUI to full screen mode. By doing so, I was able to duplicate the issue.
It doesn't matter on my system if you are in full screen mode or default mode. The problem is still the same. Most of the images above show the Windows in default mode without being maximized.
-
20 hours ago, Marcos said:
Thanks for the heads-up, the issue has been tracked internally for developers.
P_ESSW-16881
Thanks for letting me know.
-
1 hour ago, itman said:
Test one or more of your custom firewall rules and see if they still work.
I think maybe you misunderstand the problem. It looks like Eset has created a design flaw in the GUI. When you have a firewall rule for an application that has a long application path it moves all the data located in the second field too far to the right margin to be seen. Then you have to scroll to it in order to see it. Then you can't visibly see which data belongs to which field because the field names are no longer visible after you scroll to the right. The longer the application path the farther it moves that data over to the right margin. The user should be able to see that data without having to scroll to the right.
Take a look at the rule you have for SearchApp.exe and you should see what I mean if the same thing is happening on your system. Here is what the sidebar looks like for SearchApp.exe on my system. It moves the data almost completely out of view for SearchApp.exe on my system. I can barley see where the beginning of the second field begins. Many of my other firewall rules are moved much farther over to the right margin than SearchApp.exe
-
5 minutes ago, itman said:
I double checked my custom firewall rules and the fly-out populates correctly.
Try returning to default GUI color mode to see if black mode is the issue.
I changed to Light Mode and still the same problem.
-
23 minutes ago, reisender1967 said:
If the application path is too long, a scroll bar appears at the bottom (see yellow box).
Click on it with the mouse and drag it to the right, then you will see the missing information.
I know about the scroll bar. The point is the user should not have to scroll so far to right margin to see that information. That information should be listed right next to the field names. There really should be no reason for the user to have to scroll at all to see that information. Once the user scrolls over to the right the user can not visibly see which data belongs to which field because the field names are out of view then.
-
All the info that should be listed where the red squares are is hidden far to the right of the margin. No application name, no port number, etc...
-
Ok, I just discovered the info is actually there but out of view far to the right margin. One has to scroll far to the right to see the information listed for Availability, Action, Direction, Times Applied, Profile, Protocol, Local, and Remote for some Firewall rules. This same information is easily visible for most rules without having to scroll to the right. Below shows what the sidebar looks like when the user does not have to scroll far to the right to see the information listed for Application, Availiability, Action, Direction, Times Applied, Profile, Protocol, Local, and Remote.
-
I Just updated to Eset Internet Security 16.2.11.0 and everything is blank in the sidebar for some application rules. Application, Availability, Action, Direction, Times Applied, Profile, Protocol, Local, and Remote are all blank. This is shown in the 2 screenshots below. I can send Eset logs if requested by PM.
My System Specs are as listed.
Edition Windows 10 Pro
Version 22H2
Installed on 5/28/2023
OS build 19045.3208
Experience Windows Feature Experience Pack 1000.19041.1000.0
-
23 hours ago, itman said:
On this regard, let's talk about FUD malware;
https://thehackernews.com/2023/06/cybercriminals-using-powerful-batcloak.html
Full Trend Micro analysis here: https://www.trendmicro.com/content/dam/trendmicro/global/en/research/23/f/analyzing-the-fud-malware-obfuscation-engine-batcloak/tb-the-dark-evolution-advanced-malicious-actors-unveil-malware-modification-progression.pdf .
If the user monitors cmd.exe they will be able to block the execution of the batch file. If the user blocks powershell.exe and powershell_ise.exe then the malware will not be able to execute at the later stage in the event the batch file is allowed to execute.
These attacks might make it past a traditional antivirus, but they can be easily blocked in a home environment using ERP or AppGuard. It's more difficult in a Corporate Environment were vulnerable executables are actually used often, so they can't be blocked as easily without creating problems. Things like Powershell, Remote Desktop, and batch files are used often in a Corporate environment. It's a hell of a lot easier to secure a home network than a corporate network.
-
Users that don't use Powershell or Remote Desktop should block it using Policy Restriction or Whitelisting technologies. They can probably block over 90% of attacks by blocking the most commonly exploited executables like powershell.exe, powershell_ise.exe, rdp.exe, wscript.exe, cscript.exe, vbs.exe, cmd.exe (monitor this one using whitelisting), etc... This want be an option for most users though because it takes self initiative to learn more about security, Windows OS, and configuring security software. I believe most users don't care about security until they are victim.
-
My settings in Security Center were the same as yours.
I guess this thread will serve no purpose now that I am participating in Eset Insiders again, so I am going to mark it resolved for now. I am beta testing the latest alpha build of ESS since they finally decided to do a major overhaul of a certain features that looked horrid to me, and I was very outspoken about it for quite some time. I don't think I can say much about it due to the None Disclosure Agreement. The changes they made was not what I was expecting, but it looks much better than what is currently being used. I think you will like the changes.
-
It seems that simply disabling and reenabling Eset's Firewall fixes the problem with the connection timing out for Eset Updates, Live Grid, and Webpages. I'm now able to visit all the webpages that I have been trying to visit all day, Eset finally updated, and Live Grid is working again. I was just restarting the computer to resolve the problem before this. I will just disable and restart Eset's Firewall until the problem can be identified and fixed.
-
The Internet was working fine before I installed Eset. The problem started shortly after installing Eset. I tried changing my DNS to Google and that did not help, so I switched my DNS back to my ISP. I was trying to visit a popular news website just now and the connection kept timing out. I disabled the Firewall by right clicking on the try icon and the website loaded instantly. I will start disabling the Firewall each time i'm unable to access a website. If disabling the firewall allows me to access the website, then I can be pretty certain that Eset is the problem.
-
Internet access is failing for Eset Internet Security Updates, Live Grid, and most Internet Sites with EIS 16.1.14.0. I recently formed my computer and installed EIS 16.1.14.0, and the Firewall is set to Automatic Mode. I will be changing the Firewall to Interactive Mode after I resolve my internet connection issue. Where do I send my Eset Logs to, and what log settings should I use? I believe Eset Firewall may be the culprit.
Below are my OS Stats.
Edition Windows 10 Pro
Version 22H2
Installed on 5/28/2023
OS build 19045.3031
Experience Windows Feature Experience Pack 1000.19041.1000.0 -
If they are going to verify the user's email address, then they should verify the email address the user has listed for their account. I checked my current email address for my account, and it has no typos in it. It seems to me to only make sense to verify the email address the user has listed for their account. The email address listed in my account is correct as you could see from the screen shot I sent you. Maybe you could suggest to Eset that they should verify the email address the user has listed for their account.
-
Marcos has resolved the problem where I was unable to verify my email address. It seems Eset's email system was truncating an "e" from my email address. All issues have been resolved now. Thank you to everyone that offered feedback!
-
4 minutes ago, Marcos said:
Public license ID is called public because it's not secret and can be posted publicly to identify user's license.
2FA (via email verification) is required to enable or disable auto-renewal for security reasons. Entering just the license key would not be enough because in case of a leak other people could activate auto-renewal without your knowledge.
First we'll need to check if the verification email was actually sent to your email address, hence we need your public license ID (PLID).
My public license ID is 3AJ-P9V-9HP
-
21 hours ago, Marcos said:
Please start off by providing your public license ID the form of XXX-XXX-XXX. As I've been told, auto-renewal can be turned off after verifying your email for security reasons. We need to find out if the verification email was delivered to your email address, hence we need info about your license.
Is that license ID safe to post on this forum, or did you mean to send it by pm? Also, I don't understand why Eset makes me verify my email address each time I renew my license. I verify my email address once a year, and it's always a major pain to deal with.
-
It was also a nightmare last year when I had to renew my license, worse than it was this year. I received an email from Eset support saying they removed me from auto-renewal. I checked my spam folder many times after not receiving the verification email; my spam folder has been empty the entire time.
My account still says my email address needs to be verified, but I'm still not receiving the verification email. I checked the email associated with my account, and it is the correct email address. I was able to receive an email from Eset support to the same email address. I still need to verify my email address so I can remove my card info from my account. I never save my card info on any of my accounts, in case they ever get hacked, I want have to worry about my card info being compromised.
-
I'm not being given any option to remove my card info. I'm being redirected from buy.eset.com to home.eset.com now. It wasn't doing that before. I don't even see my card info listed anywhere, but I know it must be listed on my account somewhere. I don't understand why I am being redirected from buy.eset.com to home.eset.com now. It wasn't doing that before. My card info is nowhere to be found, so I can't remove it.
Well, I have to go, I have already spent 2 hours on this tonight, and that's not including the time I spent trying to rectify this yesterday. I will check back tomorrow. -
Thank for the response Nightowl! Come to think of it, I removed my payment info the last several years in a row after having the same or similar problems with the auto-renewal. I just got done chatting with Eset support at buy.eset.com first, and they had me send an email to some other support department. Also, I don't understand why I need to verify my email address so many times. Good grief, I keep having to deal with the same purchasing problems every year. I will go ahead and remove my card info, thank for reminding me!
-
Eset will not allow me to disable auto-renewal for my license. When I attempt to disable auto-renewal it says, "Only certain license actions are available as you logged in. Verify with your email to reach full access." That's a bad English translation, in case you want to correct that on your site, but that's a little off topic. I have already verified my email address; the last time I verified it was about a year ago. If I click on the link for Eset to send me a verification email, Eset fails to send the email. I have tried multiple times over the past 24 hours. Eset will not send the verification email.
Also, issues with disabling auto-renewal has been a problem for at least a few years now . There is a thread from me on the forum from last year when Eset would not allow me to disable auto-renewal. Last year Eset did not even inform that I was enrolled in auto-renewal at the time of purchase. I always purchase my license directly from Eset. This year Eset informed me about the auto-renewal, but I have no way of disabling it again. What will I have to do to get auto-renewal disabled? I'm logged into buy.eset.com -
Eset Internet Security 15.2.11.0 says it has been updating for the past 2 hours! I've been using version 15.2.11.0 for about 2-3 weeks. I tried canceling the update without any success. I can't reboot right now because i'm encrypting a disk which will take another 3 hours to complete. I assume this is some sort of bug with Eset. Is 15.2.11.0 the latest stable release of Eset Internet Security? I don't have beta releases enabled.
Eset Internet Security 17.0.15.0 AMSI Integration has failed!
in ESET Internet Security & ESET Smart Security Premium
Posted · Edited by cutting_edgetech
I have collected Logs. Where do I raise a support ticket at? Do you also want the logs?
Is this the right place to create a ticket? I purchased my License through Eset's Store Website.
https://www.eset.com/int/support/contact/