Quirky

Member
  • Content Count

    95
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by Quirky

  1. Quirky

    Few questions about application rules.

    About rule self-cleaning, I'd like to ask if this is also valid for scanning/monitoring exclusions. For example, if I've added a folder/file exclusion that it's no longer there (the excluded file or folder), would the exclusion be auto-removed at some point?
  2. Hello everyone, a couple of questions: 1. I have a fairly lengthy range of IP addresses (both single addresses and some IP ranges) stored in a .txt file that I want to block. This older post suggests that the Firewall should be used for this instead. Is this still valid? I imported this .txt file into Surf Protection, everything seems fine and the IP's are listed normally. I cannot find something similar (file import) in the Firewall and it'd be impossible to import them one by one. Unless there's another way? 2. About Surf Protection: does it block the list entries globally at OS level or only via web browsers? Thanks.
  3. Quirky

    Surf Protection or Firewall?

    Thanks GT500, but that includes application rules ("Application and global firewall rules"). From a quick look in the exported a2rules.ini file, the application and firewall rules are mixed so it's not easy to separate them. Perhaps copy/pasting firewall-only rules into a separate a2rules.ini file might work for importing them, I don't know.
  4. Quirky

    Surf Protection or Firewall?

    Thank you, commas and ranges work fine. Hope you can consider adding an option to export/import Firewall rules only, separate from the Application rules (unless there's a way?). Firewall rules should be easy to transfer to another PC but with the Application rules included in a2rules.ini, it doesn't seem like a good idea to try (32/64-bit systems/paths, different applications etc.)
  5. Quirky

    Surf Protection or Firewall?

    Thanks Ken1943, yes I know about the Surf Protection file import and mentioned it. The main question though is whether the Firewall is supposed to do this instead for better protection and if so, in what way. Also, other threads suggest that Surf Protection does not work globally and since AppContainer is not supported, I am guessing Windows 8 and especially Windows 10 are not fully covered by Surf Protection (not talking about Edge, but W10 as a whole). I'm not technical on this stuff, just asking.
  6. This will allow users to have a "basic" protection list always enabled, and to quickly enable/disable a second -or more- custom list when required, without having to give up the main list protection by globally disabling everything. The ability to name the lists will make this even nicer.
  7. As in v11, I've noticed that EIS performs its auto-updates (signatures and software updates) during system startup. While it makes sense to do this as soon as possible, in practice it causes problems on older systems and even newer systems with slow HDD drives (many laptops). There's too much hard disk activity during startup (especially with several programs present in the startup list) and the system can become unresponsive (even unusable) for some time (usually short, but still an issue). EIS can add a significant amount of HDD activity during startup. My suggestion is to add a small delay and perform these updates after the startup sequence is well complete (similar to the "Automatic/Delayed Start" option found in Windows Services). It could be added as a performance option, close to "Activate memory usage optimization" for example. I don't believe it would be a security issue to delay the updates for 1-2 minutes or so.
  8. Quirky

    Notifications look blurry on high DPI

    I meant the latter (for EIS to enforce scaling prevention on its own, perhaps via a user-selectable option) but anyway, thanks for looking into it. I re-enabled custom scaling which solves the issue for all applications (including EIS) and Windows components, and only rarely revert to standard/default scaling for the one application that needs it.
  9. Quirky

    Notifications look blurry on high DPI

    You are right, that's probably the cause. Perhaps adding an option within EIS itself would be easier to implement than using Windows' file properties system?
  10. Updating Windows might solve your issue (you should update anyway). Another option would be the excellent Windows Repair, make sure to read and follow all instructions. Read the descriptions of each repair and select the ones that could help (don't just select all of them).
  11. Quirky

    Notifications look blurry on high DPI

    Thanks GT500, I know about the general blurring issue but the particular problem of the a2guard compatibility setting auto-disabling itself (and thus causing the blurriness that can be bypassed) seems specific only to Emsisoft. I don't recall other exe's not maintaining the "Disable scaling" setting, unless you are saying that that's how Windows 10 works for some programs, and that setting is not retained after a restart in some cases. If that setting was retained as one would expect (and it does on the programs I've tried), we could bypass the problem for Emsisoft software, too. About the blurring issue in general: that tool has been very helpful but now is only rarely required because after the W10 Anniversary Update, selecting a custom scaling level in W10's settings, achieves the same effect as that tool and solves the problem. Using the older scaling method in Windows 10 (described as "custom"), might cause other issues with some programs but that's irrelevant here.
  12. Quirky

    Notifications look blurry on high DPI

    This works, but unfortunately after the second restart that a2guard compatibility setting is automatically disabled/unticked and the blurriness comes back (W10 x64). Hope you can fix this.
  13. HTTP/2 is fully supported. Also, I wouldn't trust automated tests more than user experience It could well be the user agent sniffing that causes further unnecessary problems, instead of detecting browser features properly.
  14. Forum also seems a bit slower/more sluggish now but that could be just my impression.
  15. Doesn't look it's related to ShutUp10. Try the suggestions here.
  16. Quirky

    CLOSED Suggestion: delay updates during startup

    This seems to be correct, EIS performs the auto-update a little later when Fast Startup is not used. If you could change it to behave like this in Fast Startup mode too, it would be an improvement. However, as Windows 7 users still experience PC startup delay issues (there is no Fast Startup in W7) it would probably be best to delay the initial auto-update a bit further (for example, 3-5 minutes after startup sounds reasonable).
  17. With the new version, I noticed that quite often this message pops up: (wording is not exact) "You seem to dig this wi-fi network, would you like to disable App Lock... etc." This essentially allows any user to bypass all app locks with one click. What's more, it keeps coming back rather annoyingly, even if the user refuses. Please consider completely removing this security-hole message, the Settings are perfectly adequate to handle this. Also, the ability to lock EMS itself seems lost.
  18. Quirky

    App Lock vulnerable

    If I remember correctly, the feature activated without requiring the PIN, which urged me to post here. I have the "do not ask the PIN for 30-seconds..." option enabled and I probably had unlocked an App just before that. Will it not ask for the PIN in this case? Can't remember if I had already adjusted the settings, but it now seems the message is not reappearing. In any case, I still think you should remove that pop-up for both security and user-annoyance reasons. Your decision, of course.
  19. In the Application Rules list if I try to type anything in the search bar, the keyboard presses are not reflected immediately but in a slow-motion fashion, the a2start.exe process will spike at 25% CPU usage and EIS will not respond at all until all keyboard presses are acknowledged and completed. This happens whether "Hide fully trusted applications" is on or off. Searches in other UI lists seem to perform better (Surf Protection, Behavior Blocker).
  20. Small issue: all EIS a2xxx.exe processes are described as Emsisoft Anti-Malware components. Can lead to mild confusion with applications that list installed programs/running processes based on their description. (I cannot see my attachment - "no permission" message)
  21. Quirky

    EIS processes described as EAM

    Then it would only be a matter of maintaining two separate installers with just a few renamed descriptions differentiating them. Unless this involves too much extra work, I don't see why it can't be done. Anyway, I'm not insisting (hardly a big issue) but since these are clearly separate products -even if using same code base- they should be described as such, even in the esoteric processes properties.
  22. Quirky

    EIS processes described as EAM

    GT500, I never argued about all of them being the same, not sure why you insist on that. My only point was: that (same) Product Name should be EIS, not EAM. It is just wrong, that's all.
  23. Quirky

    EIS processes described as EAM

    The same applies to the other processes.
  24. If you have several security software installed, you are asking for trouble and problems are bound to appear. This is known, well-documented territory and certainly not specific to Emsisoft (which I think is one of the most compatible ones anyway). The main purpose of security software is to protect your computer, not to be compatible with each other. It would be nice if they all played along together, but by their own technical nature, it is almost impossible (and understandable). Having said that, it'd be good to know exactly which programs cause problems, for the benefit of other users who might encounter similar issues.
  25. As in version 11, if I add a folder in the "Exclude from monitoring" list, all programs (.exe processes) that are inside that folder and its subfolders will still be reported as Monitored ('Yes') in the Protection/Behavior Blocker list. The only way to *not* have all processes inside a single folder -and its subfolders- monitored is to add them one by one in the Exclude from monitoring list. Folder exclusion seems to only work for scanning, not monitoring (same problem in v11).