Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


zamar27 last won the day on May 8

zamar27 had the most liked content!

Profile Information

  • Location

Recent Profile Visitors

755 profile views
  1. Check next time if these files are Read Only, and your user has Write permissions.
  2. At changing settings, Eset may be saving several files to different dirs, so it looks like some of these files may be saved with Read Only flag, which may be visible in ProcMon log, and also in Resmon.
  3. Try to relogin to Windows instead of reboot after the error happens.
  4. Since Trusted zone is computed correctly in Eset Network Adapters window, this seems to be rather broken config file or Registry key issue likely caused by numerous Eset updates, or possibly relevant Reg cleanups.
  5. For the test, I manually added some IPs to various default Eset Zones. Then I tried to add any of default Zones to any Firewall rule. The above error persists for *any* default zone in *any* rule despite the zone being populated with some extra real IPs. But if I create a new zone, it can be added OK to rules, which accept Zones. I wonder if Eset periodically needs remnants cleanup and reinstall, since regular program updates possibly leave conflicting settings in Registry or config files. I'm always shocked by some programmers culture to leave garbage everywhere at uninstall, like its their own system, and not the user's.
  6. No, the error occurs when submitting this Form. Also, the actual issue is its impossible to add Trusted Zone to firewall rules in some installations.
  7. Adapters use can change: today its Ethernet wired, later its WiFi, then VPN virtual adapter. Eset install may happen long ago, internet provider and their DNS IPs may change by then too. Can you refer to an article that says inherited from Windows DNS IPs must be visible in Firewall Zones? I sent a request to tech support using the form since Marcos never replied, but Eset server replies "store.esetme.com’s server IP address could not be found."
  8. I tried all possible profiles already as reported above. The error persists. Did you manually enter DNS server IPs into the adapter IPv4 Properties in Windows? Or Windows obtains them from your gateway modem?
  9. There are many fields in Eset Settings inherited from Windows and not visibly populated. The OP runs Eset in a VM, but I don't, and still have the same error. I don't know whom you address your replies, but this is a public forum, many folks often report same bugs. 😋 Eset doesn't pass all traffic freely, I can see it in Interactive mode, it popups windows at each request. I can create new rules, just not with Trusted Zone. I noticed interesting practice though. Eset staff often fixes bugs based on forum reports, and at times pushes fixes through daily updates. Folks still debate the bug, but it may gone already. I think Eset staff should notify about fixes in such threads.
  10. If you believe they need to be populated because they are on your PC, they are not on mine, and Eset Firewall functions somehow, I can see it in Interactive mode. They might be inherited from Windows settings as well, and hidden for that reason. I now switched off VPN, changed WiFi to Private, noticed changes in Eset Network Adapters (it now shows local WIFI as Trusted Zone), switched from Interactive to Automatic Mode: and still no smoking cigar, the same error persists when adding Trusted Zone: "nonexistent zone". One might assume some portions of Eset code require relogin or reboot while others don't. I also agree that a VM may represent challenge to Eset when calculating Trusted Zone, unless defaults are populated by staff, since VM network connection types vary, and generally differ from physical PC connections. But I just run Eset on a physical hardware, no VM, therefore its safe to assume this is a bug. 😊 The question then is, why your settings are populated, and mine aren't? What's so special about your network or may be other relevant settings? Can you try the same in Interactive mode? Does relogin or reboot play into it? For starters, my DNS server IPs come from provider through hardware chain and therefore not visible to Eset, while yours may be manually entered into adapter IPv4 Properties?
  11. I'm using Eset Firewall now in Interactive mode. I changed a network connection to Private in Windows, got the adapter in Trusted zone in Eset Setup-Network Protection-Connected Networks-Network Adapters, and still got the same error in Eset adding a Trusted Zone to any Firewall rule. There're some terms variations here: in Windows the term Zone is used in Internet Options-Security, and aims at setting Security Levels at Internet browsing, initially by IE, but it applies to any browser now. Same term is not used in Windows Network Settings, being replaced with Private and Public networks with other set of rules. This might be a consequence of earlier IE integration by MS into Windows, where Internet Options become part of OS settings. Windows Firewall and Defender seems to have a default set of rules (security levels) for each Zone defined in Internet Options, but a user can change the level for any zone. I wonder where Eset Firewall zones fit into this? It defines Trusted Zone somewhat similar to Network Types in Windows, i.e. Trusted Zone seems to correspond to Private or Office network type, while inheriting Windows Network Adapter (connection) settings, which may include hidden Windows Firewall rules related to Security Level (zone) in Windows Internet Options. It looks, an Eset staff Firewall expert should give a more accurate reply how Eset Trusted Zone is calculated. Anyway, the trusted zone was not added to Advanced Firewall rules in my tests, showing "Error: nonexistent zone" despite Private network present, which seems to be Eset Firewall bug.
  12. Its allowed, but not required for a user to add anything in Eset Firewall Zones. Active network connections if exist are auto imported from Windows to Eset with their profiles, as well as all network adapters. Trusted zone should be computed by default for Private network connections if exist, such as Home or Office network, but not for Public networks.
  13. Did you mark any of your LAN or WiFi adapter profiles (network connections) as Private in Windows Settings - Network & Internet - Adapter Type - Adapter Name - Profile, or Eset Setup - Network protection - Connected Networks - Properties?
  14. Is it possible in the next ESS version to add "Remove Threat" or "Select Action" button to a last scan log of each scan type, even if a user did not select any action immediately after the scan was completed and instead rebooted the PC? In this scenario, if ESS removed a threat upon reboot, the Action button would no longer be visible against this threat in the log. If the treat file was later manually moved by a user to another folder, upon selecting an Action the user would get an Error "no file found". Also, a user should be able to select multiple threats from the log to choose a common action. Now there's a problem with manual threat removal. I scanned my PC yesterday, and got a long list of "potentially unwanted application - action selection postponed until scan completion" records in the Eset Smart Scan Log done with default settings (i.e. Default Cleaning Level - no auto removal of unwanted apps). BUT... there was no way upon scan completion to choose an unwanted app from the log and select an Action!!! In addition, probably due to ESS yesterday's module update, my PC went to sleep and failed to wake up properly, so I needed to reboot. Upon reboot I could access the last ESS log, BUT... there're again NO ways to select any action (like: Remove) in that Log window or any other window. Why then I did the 2-hour scan, if no ways to do any action after that?
  • Create New...