Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Quirky last won the day on September 20 2018

Quirky had the most liked content!


6 Neutral

Profile Information

  • Gender

Recent Profile Visitors

3907 profile views
  1. With saying "only a2service.exe is still running" I meant that a2guard.exe and a2start.exe were not running. I am not sure about eppwsc.exe (didn't check) or anything else.
  2. I'm seeing this on two PCs. Reminded me of the infamous integration issue but it's probably unrelated. Right after system startup, the EAM tray icon disappears and only a2service.exe is still running. WSC reports the 'no protection' issue. Manually launching EAM solves the problem, until the next time. It does not happen very frequently, but it does. "Start on Windows startup" setting is enabled. I've tried uninstalling (2x restart) but it didn't help. I've created a log with the Emsisoft Diagnostic Tool, right after the tray icon disappeared. Please let me know if you want it and where to send it.
  3. Thanks for the beta. I've clean-installed 20H2 on both my main PCs and don't plan to feature-upgrade Windows 10 any time soon, so I can't really test it currently. Unless the issue appears on these PCs too, that is.
  4. Well, Windows 10 "feature upgrades" tend to mess some things up. I guess this can be added to the list...
  5. So, you are confirming what I said in the previous post.
  6. Clean 1909 install, without having upgraded from earlier versions?
  7. I tried several times, but it seems almost impossible to reproduce the issue with logging enabled. The issue soon reappears when logging is disabled. For what it's worth, I've noticed this: On a PC with a clean Windows installation that has NOT underwent any Windows 10 upgrade (i.e. 1909 to 2004, 2004 to 20H2 etc.), the issue will NOT occur. At least it has not occurred once here. On a PC that's had at least one of these upgrades, the issue will keep occurring.
  8. No, I have managed to collect logs (and send them) from the older PC. EAM logs, that is.
  9. Thank you David, although I'm a bit confused! The Chrome version of what? Do you mean the Emsisoft Browser Security extension? I am talking about the Emsisoft Mobile Security Android app. I can see how the extension might apply as a nice workaround though. I'll try it.
  10. Any plans to include it? It's popular, Chromium-based and with a New Zealand reference, too. I am not really sure if all Chromium-based browsers are covered by Web Protection. Probably not, since EMS shows a specific browser list. Kiwi Browser At least 3 Chromium-based browsers may enable extensions support thanks to Kiwi Browser
  11. Both my PCs (2008/2015) have 8GB of RAM. edit: also note that sometimes several days can pass before the issue makes a reappearance. It doesn't always happen often. Might be placebo, but I think that once the issue is triggered, it will frequently occur 2-3 times. Then, it will go back on 'hibernation' for a while, until the next time it's triggered.
  12. Thanks for the info, JeremyNicoll. As marko said, it does happen here too with logging enabled, albeit far less frequently. But perhaps that's what you meant.
  13. Also, the issue seems to occur way less often on my newer laptop (2015 i5 CPU), than on the old desktop (many more programs/services installed, 2008 Core2 Quad CPU).
  14. Yes, it's the same thing. I was looking at the Services list, not process names. You mentioned possible timing issues. Don't know what that means exactly, but it always seemed unusual (way before this issue appeared) that WSC takes its time to detect and report the system status after boot. It usually does so a few minutes AFTER system startup, so if you try checking the status before that (in Windows Security), you will get a "Getting info..." message along with a spinning wheel.
  • Create New...