Jump to content

Quirky

Member
  • Posts

    125
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by Quirky

  1. Your attachment is unavailable to me, I assume it's the same tool available here. EAM seems to start fine, but sooner or later it will quit (crash?) on its own. I am sending it via PM.
  2. This is from yesterday - Reliability details/Critical events/a2service.exe/technical details: Faulting application name: a2service.exe, version: 2021.10.0.11201, time stamp: 0x61544003 Faulting module name: a2core.dll, version: 2020.5.0.47379, time stamp: 0x5eab77f0 Exception code: 0xc0000005 Fault offset: 0x00000000000199b0 Faulting process id: 0x6f8 Faulting application start time: 0x01d7c9d71079a6dd Faulting application path: C:\Program Files\Emsisoft Anti-Malware\a2service.exe Faulting module path: C:\Program Files\Emsisoft Anti-Malware\a2core.dll Report Id: 5194f300-e3a7-4820-a1b9-cd1a038f7832 Faulting package full name: Faulting package-relative application ID:
  3. It now happened way after startup, at a seemingly random moment. EAM tray icon disappears and WSC goes red. I re-launched EAM, the UI appeared (all green/OK), WSC still red. a2start.exe is now there but no a2.guard.exe and still no tray icon. Closing the window and launching EAM again does not solve it. What solved it in this case: disabling one protection element (e.g. Web Protection). The tray icon appeared and so did a2guard. Re-enabling Web Protection brings back WSC green status, too.
  4. 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.
  5. 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.
  6. 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.
  7. Well, Windows 10 "feature upgrades" tend to mess some things up. I guess this can be added to the list...
  8. So, you are confirming what I said in the previous post.
  9. Clean 1909 install, without having upgraded from earlier versions?
  10. 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.
  11. No, I have managed to collect logs (and send them) from the older PC. EAM logs, that is.
  12. 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.
  13. 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
  14. 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.
  15. 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.
  16. 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).
  17. 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.
  18. Perhaps these errors are related to Defender being permanently disabled? Never disabled the Windows Security Service myself. Its current status is: Manual/Running. What I usually do once (after installing Windows), is disable Tamper protection and then use O&O ShutUp10 to disable Windows Defender. I believe that changes a group policy. I've recently read that Microsoft intends to make disabling Defender more difficult (impossible?). I ran that command (btw it only worked in cmd, not Powershell) and restarted. Didn't notice any difference and Defender remained disabled. Windows Security Service remains Manual/Running. I'm not seeing a service with 'Health' in its name.
  19. I did the uninstall + 2x restart + install 2020.9.0.10390. Issue soon reappeared. More specifically, it reappeared right after the restart that followed the automatic cumulative W10 update to 18363.1082. Can't say if the update process is related and of course, issue does not only appear after Windows updates. As usual, EAM works (all green, UI+EAM tray), WSC reports it as off with a red tray icon (I've manually/permanently disabled Defender). 1. Shut down EAM 2. Wait for its process/services to close. Re-launching EAM without waiting for this, seems to cause some trouble (EAM will not start properly -no UI- and only a PC restart solves it) 3. Re-launch EAM. Usually, WSC will now report correctly (until the next time, unfortunately)
  20. Yes, I've noticed a similar thing with logging. I did manage on one PC to reproduce the issue with logging enabled, but it seems to occur more often when logging is off. Can't say if it is related of course, only Emsisoft can find out. On my second PC, I did not manage to reproduce the issue with logging enabled.
  21. Yes, problem unfortunately remains and the old trick of quitting and restarting EAM doesn't seem to work consistently anymore. a2service and a2start are running, but the UI and tray icon will not appear (after quitting and restarting). Nothing happens (I've switched to stable btw). andrewek, may I ask what is your CPU? Is it an old one? I wonder if this is somehow performance-related.
  22. Usual issue occurred 5 minutes ago, just sent few more logs. All EAM components enabled, WSC icon red, Security providers=EAM+Defender both turned off. As always, I've manually turned off Tamper Protection + Defender.
  23. Got a similar problem with the current beta. WSC again reports [EAM=off] but this time, all EAM modules are indeed turned off in the EAM UI. Seems more like a crash though, since I cannot interact with EAM. It's very sluggish and the UI responds more than a minute after I try to do anything. "Fix Now" did not work. I'll re-enable logging. edit: this occurred on 1909.
  24. Good news, thank you. Perhaps I'll try it on my laptop. As for the main PC, I reverted to 1909. Another good lesson learned: never install Microsoft's first W10 release of each year (around March). If you have to update, go for the second one (around September) which is more like a service pack. Way more reliable (but still buggy, make no mistake) In any case, I will report back if this problem re-appears whether in the beta, or the next stable EAM release.
×
×
  • Create New...