Jump to content

MoRbIdBoY

Members
  • Content Count

    14
  • Joined

  • Last visited

1 Follower

Profile Information

  • Location
    U.K.

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. No, I haven't created a support ticket... at this stage, if I had a box, I'd throw the damn stuff out of the window. I'm about another 30 minutes trying to sort it out, then it's the studio manager getting his had in his wallet for some decent stuff. - just one other question itman - and cheers for your support, i appreciate your help, version 8 used to work fantastic, can you still download it and get a/v updates through it?
  2. So, updated my VMWare as per guidelines prior to 1909 Windows update. Uninstalled ESET (also as per general guidelines). Did Windows Upgrade to 1909. Reinstalled ESET, Got all these problems. I haven't marked anything as a public network. I believe windows firewall did that automatically just on the default VMWare NAT adaptor when I upgraded (which I believe is probably a good thing right? - I don't particularly want VM's to be able to access my LAN unless I need it, never thought about it before). So I just "stuck with it". Never had anything this stupid in my life. How do I get it back to "self populating" then if it's "by design", it's not a design I particularly favour or understand. The whole POINT of antivirus and firewall software is to make this stuff easy, otherwise I may as well go clunking through Windows Firewall. Design is OK as long as I can figure out W*F is going on. (And I don't think good design lets people populate their firewalls with garbage that lets anything through it). - I only say all this by the way, because it might be interesting to see if it clears up the non-existent zone problem. They both happened at the same time.
  3. Yep, just as I thought. Even when I fill in the Trusted Zone myself as follows: When I physically add a rule to the firewall using "Error: nonexistent zone", thinking I've clicked on "Trusted Zone" (that's what the default option in the drop down list is telling me remember, I only see "Error: nonexistent zone" if I double check what ESET has just added to my firewall, then I get this as the actual firewall rule - and ESET lets me proceed and add it in without any kind of warning. So just to be clear - the second rule (in which I intended to let this application only communicate in the "Trusted Zone" - has automatically now become a rule which allows complete local and internet access. "Remote" column above should say "Trusted Zone" in the second entry, or at least "nonexistent zone". As you can see above, I've filled in the Trusted Zone details myself, so there shouldn't even BE a nonexistent zone. If THAT isn't a serious software bug that needs fixing yesterday I honestly don't know what qualifies to you guys. Personally, right now, I'm looking at alternative solutions for firewalls. 1. This box isn't populating correctly. 2. ESET isn't warning me I'm mistakenly adding a zone which does not exist (AT ALL). It's actually making me think I'm adding Trusted Zone because that's what it says. 3. Trusted Zones isn't self populating (I've used ESET for about 15 years and I've NEVER ONCE had to populate Trusted Zones manually). 4. This is a completely fresh install of ESET. Everything was uninstalled prior to this error. Registry cleaned of EVER ESET entry (your cleaners used - PS, your uninstallers miss HKEY_CLASSES_ROOT\eComServer.EsetHC and HKEY_CLASSES_ROOT\eComServer.EsetHC.1) as well as any remnants from the driver store using PnPutil.exe. - ITS GONE. 5. End up accidentally adding a firewall rule which potentially allows full access to my network. Just because I've gone VMWare 15.5.1 installed?
  4. OK, so, coming back to this thread after a while off (because I dont like to see them unresolved if I may have answers to help someone else in the future). Uninstalled ESET, removed any directory remnants, used avremover_nt64_enu.exe and the old esetuninstaller.exe. Used the script I mention here AND didn't import any old configs (started again with my firewall rules, which - I might add - hurt): Thought I'd cracked it - couple of reboots later the problem came back. Tried the following on an elevated command line (I found after a lot of searching around): "C:\Program Files\ESET\Internet Security\ecmd.exe" /registerav This apparently registers the firewall with Windows Security Center through WMI (Windows Management Interface). Every time I tried the command a windows notification came up immediately informing me Both Windows and ESET Firewall are both turned off. That was clearly wrong, because ESET Firewall was most definitely ON by this time (all green). But it did lead me to think that clearly WMI was suffering with early onset dementia. Then I came across THIS TREASURE. https://support.eset.com/en/kb217-windows-security-center-is-not-detecting-my-windows-eset-product Believe me, when I say I've searched there, and the entire internet, 1000 times and could not find that. It seems to have sorted the problem. I have to say though, everything after version 8, has been complete garbage bloatware. It's been far more trouble, far more complicated and far more frustrating and more unreliable. I honestly used to feel very safe with everything up to version 8. Since 9 onwards... not so much. Anyway... here hoping another problem has been fixed. PS. It is worth mentioning that nothing else had a problem with WMI on my system and I did check the WMI integrity with: winmgmt.exe /verifyrepository As explained here: https://support.quest.com/vworkspace/kb/88861/how-to-repair-or-fully-rebuild-windows-wmi-repository and it came back consistent. So the question really is WHY did I have delete a perfectly good verified repository? * (Rhetorical). PPS. FFS. Please TAG or RENAME the BELOW link: https://support.eset.com/en/kb217-windows-security-center-is-not-detecting-my-windows-eset-product With Both Windows and ESET Firewall are both turned off because THAT IS WHAT THAT ADVICES ERROR MESSAGE ACTUALLY ELUDES TO - IT IS NOT MENTIONED ANYWHERE - AND SO OTHERWISE PEOPLE WILL NOT FIND THAT ADVICE - AND THEREFORE, WHAT POINT IS THERE TO IT !!!!
  5. Exactly the same as jimmerthy above, but I'm not going to gangbang his thread or write "same problem". Problem is.. it's a security risk. People sometimes add firewall rules like automatons, because it's a "routine thing". If this "none existent zone" problem happens (pops up) and ESET actually LETS you add it to a firewall rule do YOU know what implications that has on the rule or the software? Do you know if I've just given the entire world access to my local area network? Does anyone actually know what a none existent zone actually is? I don't. Hardly trustworthy is it? I'm used to Trusted Zone automatically being populated (by ESET) with "Trusted Zones" determined by my network configuration (or Connected Networks settings). Never had to populate Trusted Zones myself before. Never seen none existent zones before. Clearly having VMWare 15.5.1 (which was recently updated - a pre-requisite / requirement of upgrading to Windows version 10 1909's HyperVisor- which may have caused this problem) causes some kind of conflict with ESET. It's only a 192.168.0.1/24 LAN with the "default" VMWare VMnet0, VMnet1 and VMnet8 network config. Hardly "socket" science is it (bum bum!). Anyway, might be an idea just to close the thread, it's clearly one of "those" problems that's going to hang about like a bad fart.
  6. So my physical network adaptor IS listed as a "Home" network and my VMWare virtual adaptors are listed a "Public" because I dont want or need them on my local network (just need them to be able to have internet access). But... remember... After removing EVERYTHING and doing a clear down (removing virtual adaptors using VMWare virtual network manager) resetting windows networking (flush DNS - everything!) - all I was left with was my physical adaptor (set as a Home network). I then installed ESET from fresh and got the nonexistent zone error and the trusted zones not populating (that was with my virgin media dns server - IP and DNS set to obtain automatically). After that, I just set MY defaults back up (they clearly aren't causing the above problem). The reason the same DNS is listed multiple times is that I set the AdGuard DNS addresses up in the default two VMWare Virtual network adaptors as well as my physcial network adaptors. I've undone this (set both the virtual adaptors back to obtain automatically), mainly because they'll be getting their IP lookups from the primary network adaptor anyway (so whats the point). They are the default VMnet1 (Host Only) and VMnet8 (NAT). So, the one that's host only won't even be able to contact the external DNS. Guess that's my "got to mess with it" OCD kicking in. I'll check and see how many DNS are listed after I reboot with defaults back to normal. (See if it updates). Additional trusted addresses I dont use. All those ESET settings are default. I set up my network adaptors though (in ESET Edit Network) as shown in your graphic. Windows doesn't let you set your physical network adaptor up on the "private" network while being able to set your virtual adaptors up as "public". ESET does, so I uncheck "use windows settings) and set the virtual adaptors up as using a "public" network (physical as "home"). I also remove identifying networks with DNS, using instead, IP address and gateway address. The Trusted Zone option I use a lot, because I have the firewall set up as Interactive. There is quite a lot of software I set up as being able to only communicate in the local network (trusted zone) while denying internet or sometimes subnet access. As for DNS servers (I think we are getting away from the point of the thread, but) - they scored as follows (think those ruskies get a hard time personally). They seem to score pretty well compared to Virgin Media's default DNS servers and they do a pretty decent job of blocking garbage. Adguard IP4 and IPV6 DNS servers are used. https://adguard.com/en/adguard-dns/overview.html AdGuard DNS Servers 45.32.184.119.vultr.com - Excellent, 78.141.223.194.vultr.com - Excellent. 141.101.64.* - (This class-C network has no associated domain name) - Moderate. 172.69.52.* - (This class-C network has no associated domain name) - Moderate. Default Virgin Media (obtain automatically) DNS servers. brad-dnscache-1b.server.virginmedia.net - Moderate.
  7. I don't know if its applying them, but it certainly isn't showing them in the Zones. As you can see. Most worrying really, is the fact that I've removed EVERY single trace of ESET after uninstall, from Registry (searching for ESET in registry mechanic), ProgramData, Users, Common folders, etc. (there wasn't much left) - Then I did a complete network reset, using Windows Settings / Network and Internet / Network reset. Reset my C:\WINDOWS\SYSTEM32\DRIVERS\ETC\HOSTS file to: # Copyright (c) 1993-1999 Microsoft Corp. # # This is a sample HOSTS file used by Microsoft TCP/IP for Windows. # # This file contains the mappings of IP addresses to host names. Each # entry should be kept on an individual line. The IP address should # be placed in the first column followed by the corresponding host name. # The IP address and the host name should be separated by at least one # space. # # Additionally, comments (such as these) may be inserted on individual # lines or following the machine name denoted by a '#' symbol. # # For example: # # 102.54.94.97 rhino.acme.com # source server # 38.25.63.10 x.acme.com # x client host # localhost name resolution is handled within DNS itself. # 127.0.0.1 localhost # :: localhost Even run a PowerShell script I converted to remove any remenant drivers (sometimes it leaves the ESET firewall helper - but not since a few versions back): # Remove-ESET.ps1 # # Remove all eset drivers from the driver store using PnPutil.exe Param( [switch]$Yes, [switch]$Help ) Function Show-Usage { Write-Host Write-Host "Usage: Remove-ESET.ps1 [-Yes] [-Help]" Write-Host Write-Host "Parameters:" Write-Host " -Yes Remove drivers instead of just showing what would get removed" Write-Host " -Help Display this help message" Write-Host Write-host "Disclaimer: USE AT YOUR OWN RISK." exit 1 } $driverlist = Invoke-Command -ScriptBlock { & C:\Windows\System32\PnPutil.exe -e } $tap_found = $false if ($Help) { Show-Usage } foreach ($line in $driverlist) { if ($line.StartsWith("Published name")) { $published_name = $line.Replace(" ","").Split(":")[1] } elseif ($line.StartsWith("Driver package provider")) { if ($line.EndsWith("Eset spol s r. o.")) { $tap_found = $true if ($Yes) { & PnPutil.exe -d $published_name } else { Write-Host "Would remove ${published_name}" } } } } if (! $tap_found) { Write-Host "No ESET drivers found from the driver store." } After I rebooted, the only thing left was my router wired Network Adaptor after it got re-installed from the reboot / network reset. Then I ran: ipconfig /flushdns ipconfig /registerdns I reinstalled ESET, fresh as a daisy. Tried to add a firewall rule, using "Trusted Zone" and got the nonexistent error straight away - and the Trusted Zone not populating (as seen above). I'm only hoping that when you do add "Trusted Zone" to the firewall rules, it's having the sense to fall back to either "nothing" (don't allow) or local addresses (at least), so as not to compromise security. Apart from re-installing windows (which is RIGHT out - lol), trusted zones appears to be completely stuffed. Only other thing I can try is exporting a fresh ESET configuration from a different (or even virtual) machine and try importing that.
  8. Following on from this problem (which was never really resolved - apart from exporting and re-importing a modified eset configuration xml file, I had / have / exactly the same problems. I also use the latest version of VMWare and had a virtual NAT VMWare adapter (VMware NAT8). I think it got introduced (the problem) of Error: nonexistent zone appearing in new firewall rules - when I changed both my real network adapter and this virtual adapters IPV4 and IPV6's DNS details to AdAware's DNS Servers (they support both IPV4 and IPV6 DNS servers, so I changed those in both the real and virtual adapters IPV4 and IPV6 prefferences). I also note that it appears to be a problem with the ESET software "populating" this "Add zone" dialog box properly (red box area). As seen below. The "Trusted zone" is the "top" or "default" options. So if I just click "OK" to add the "Trusted zone" to a firewall "Zones" rule area, I get the aforementioned problem I.E "Error: nonexistent zone". However, if I click on the drop down, in the "Add zone" dialog box, to select a different zone (for example the next zone down - "Addresses excluded from IDS" - not actually adding it in, but just changing the option) - THEN I go back and select "Trusted zone" again in the list of dropdown options, THEN the "Trusted zone" is added to the firewall rule correctly. (As shown in the demonstrated graphic above). So essentually, if you just click "OK" thinking your adding "Trusted zone" (because thats what is shown in the dropdown) you get "Error: nonexistent zone". If you change the option shown by selecting something else in the dropdown, but then go back to "Trusted zone" THEN click add, "Trusted zone" is added and shown in the firewall rule. Very strange. No idea whats causing it (nonexistent zone), but it's definitely a bug in the software. I've tried changing my IPV6 network card adapter options back to their "Obtain default DNS server" options (I'm retaining my IPV4 AdGuard DNS options), because I think changing my IPV6 parameters from default DNS to AdGuard IPV6 DNS is what caused to problem to start appearing. I've changed the IPV4 lots of time before without getting this problem, but I seem to recalled I also changed the IPV6 this last time as well (so I did something different and the problem started appearing). (AdGuard DNS process / servers are shown here) https://adguard.com/en/adguard-dns/overview.html
  9. HA HA HA HA HAR!!!! YES!!!!! Really have sorted it this time. So, I turned off HIPS and noticed Both Windows and ESET Firewall are both turned off message completely disappears. Turned it back on, read through the various HIPS options and found "Enable Deep Behavioral Inspection" and thought to myself "anything with the word deep means slow". So I turned it off. Now ESET firewall registers correctly with WMI Security Center without time out. I'm guessing that ESET Deep Behavioral Inspection keeps a list of all your uncommon or none standard exe files (probably compares exe files to to see which ones not many people have) and keeps scanning them. Anyway, on my system, it prevented ESET firewall registering with the WMI Security Center in time, prompting the aforementioned message, You might want to look into that and alter your programs priorities. Registering the firewall with Windows should come pretty top of your list, before any scanning.
  10. Think I may have solved this. Just testing it out now and it seems a hell of a lot faster. I cleared down HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Compatibility Assistant\Store - which listed virtually every single exe on my system and disabled compatability assistant in the group policy editor. gpedit.msc Computer Configuration Administrative Templates Windows Components Application Compatability Telemetry - off (Enabled) Compatability Assistant - off (Enabled) Inventory Collector - off (Enabled) Steps Recorder - off (Enabled) I've also disabled "Customer Experience" for good measure Administrative Templates System Internet Communication Settings Turn off Windows Customer Experience - off (Enabled) Disk activity has gone down to nothing and I'm getting to the desktop almost immediately (was scanning hundereds of mb before - for about 5 minutes) on my SSD. No firewall both turned off messages as yet, I'm just rebooting and few times to check, it's brilliant! Network protection section on ESET still has 3 red "disabled" sections for about 2 minutes after boot, but then they go green.
  11. OK, I'll have a go at logging I think. itman, yes all detection parameters section are at their default and the full scan was allowed to complete across all drives. running process monitor (procmon) and logging through that, it appears that ESET is going through the entire registry (software and installation sections) looking for installed programs, taking note of executables and the like and then performing a scan on those related files (procmon registry and file logging). repeatedly, it seems to be doing this every time I start up (like it will first scan through and get to -example- Steinberg registry entries and then scan the same dll and exe files mentioned in that registry section on my hard drives steinberg folder).
  12. Hello. I have a quite heavily loaded system I used for audio production (lots of drivers, lots of data). Being able to "get to work" on the PC (without ESET) takes about 30 seconds after the desktop initially loads. With ESET it's taking about 10 minutes. Even though it's booting from EVO-850 SSD. I'm using ESET 13.0.24.0 which I beleive is the latest and Windows version 10 Pro, 10.0.17763. I HAVE TWO PROBLEMS 1. Message shortly before the system actually lets me do some work. Message: "Both Windows and ESET Firewall are both turned off". The "Network Protection" section appears in red the entire 10 minutes I'm unable to work on the Desktop. It then appears to go green about 1 minutes after receiving the firewall turned off message, and the ESET firewall functions throughout this period. 2. Even though I have both the "System startup file check" options turned off, ESET still appears to be doing a huge scan of my registry and then my entire file system, in refference to any executable files it finds in the registry. I have A LOT of executable files on my file system, I have A LOT of applications installed on it. It also does this when I resume from sleep. So besides taking an absolute age to boot, it takes an absolute age to resume from sleep. What is wrong with your Antivuris and Firewall solution? This started happening when ESET Smart Security went past version 9 and started with this "modern interface" - which is complete garbage by the way. ESET 9 firewall was much better (and MORE IMPORTANTLY CLEARER) at showing you what was going on with you firewall and EDITING changes. Have we come to a point where ESET has so much bloat, it is taking most of my VALUABLE system resouces? I don't upgrade my PC so that ESET's software can suddenly start using it all up. I expect your software to GET FASTER and USE LESS RESOURCES, not the other way around. I've tried uninstalling and re-installing ESET's software. I've tried using the ESET removal tool (in safe mode). I've tried installing the software and then waiting for it to finish it's entire scan of my PC before doing anything else. I've tried starting from fresh with ESET and not importing my existing settings. Same problems. So - Both Windows and ESET Firewall are both turned off - and - NOT respecting my option NOT to perform a startup scan and doing an entire scan of my registry and all associated executable files. Thereby reporting a false warning that both firewalls are turned off (because it's taking so long to boot to desktop) AND taking an age before I can start working or launch firefox. Sometimes taking 10 to 15 minutes to load to desktop. IS IT TIME I DUMP ESET - WHICH I'VE BEEN USING FOR 10 YEARS AND LOOK FOR AN ALTERNATIVE?
×
×
  • Create New...