Quirky

Member
  • Content Count

    103
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by Quirky

  1. 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.
  2. 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.
  3. 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.
  4. I have a second PC (a laptop) with Windows 1909 which I think never displayed the EAM integration issue. Yesterday, I clean installed W10 2004 on it. Today, I'm getting the same EAM integration issue. I'll try to log this as well.
  5. I'm not sure. The issue appeared yesterday (07/25) when the logs were collected and sent but perhaps it starts occurring during the shutdown process (previous day, 07/24) and the consequences appear on the next startup? Can't say.
  6. Logs sent. The EAM logs were sent while the issue was occurring. Rather unusually, the issue sorted itself out this time so when FRST logs were being collected WSC was working normally. I was in the middle of rebooting my router during the log collections, but it should be irrelevant.
  7. I'm a bit confused with the EAM logs procedure. I thought it'd just collect them right AFTER the issue occurs (or while it is occurring), but your instructions seem to indicate that I should first enable logging (when the issue is NOT occurring), and then wait for the issue to appear. Remember that I cannot trigger it reliably. Restarting the PC will not always initiate the problem.
  8. I will attach those, but not here. I'll send you a PM (or email if you prefer). You'll also have to wait until I see the issue again, it works fine at the moment.
  9. Exactly, although in general WSC does seem slow in getting the system "status", so the issue will appear 1-2 minutes after startup has fully concluded. I have a slow PC anyway.
  10. Some more info. The problem does not go away from Windows' own controls i.e. trying to re-enable protection from within WSC. Nothing happens. The problem does go away if I shut down EAM (right-click/shut down protection) and relaunch it. This session will keep working fine. This is not permanent though, since on a future PC restart the problem will eventually reappear.
  11. I said on my previous post that I did perform the complete uninstall/reinstall 2x restart procedure, after having already tried several other suggestions (clean uninstall with single restart, sfc /scannow etc.).
  12. Problem just reappeared and eppwsc.exe is running.
  13. Admittedly, I had not tried the second restart. I wonder why this extra restart makes a difference. Isn't one restart enough to unload drivers etc.? Anyway I did try it and for now, the issue has not reappeared. As marko mentioned though, the issue does not happen always. If it reappears, I will post again. Eppwsc.exe is running now but as mentioned, at the moment everything is working fine. I do not know if it was running when the problem was occurring.
  14. I've permanently disabled Defender so even if EAM is uninstalled, Defender will not kick in automatically. On Manage Providers, both EAM and Defender are reported as 'turned off'.
  15. Same problem here, most probably since 2020.6. None of your suggestions work. EAM 2020.7.2.10280
  16. Thank you both. Yes, I restarted several times. No, not using the beta. I meant that it I disable Defender manually, usually via the reliable O&O ShutUp10 tool. So, even if I temporarily disabled or uninstalled EAM, Defender did not kick in automatically. This is probably why I don't ever remember seeing those processes at all in Task Manager, Defender was permanently turned off. I think I've solved this though, hopefully. I tried accessing Defender's settings but couldn't, so: 1. Uninstalled EAM 2. Enabled Defender, restarted 3. Turned off Tamper Protection, disabled Defender, restarted (never had to do this in previous W10 versions - not sure if it's recommended to do, even if using another protection software) From this point on, those two processes were finally gone. Re-installed EAM and restarted a few times. Everything looks good. Next time I see these processes, I'm back at 1909. 😬
  17. So, I was feeling adventurous and updated to the new Windows 10 2004 version (19041.264), released yesterday/today. I know, I shouldn't have. All seems ok, except that I'm noticing high CPU usage from both MsMpEngCP.exe and MsMpEng.exe. Not constantly high. but in spikes. Aren't these Windows Defender and its scans? What's strange is that I've always had Defender disabled entirely. It looks like it doesn't want to stay disabled? Perhaps there's some sort of conflict with EAM and the new Windows version?
  18. I personally wouldn't touch any Chromium-based browser. Apart from the obvious privacy issues, I never liked the limited UI and monoculture design and mentality.
  19. Caring about privacy and paying attention to browser extensions is perfectly fine, but you seem to ignore the main component: the browser. Google Chrome is possibly the worst choice you could make.
  20. For the moment only Delayed helps, but I can't complain about your support which remains excellent.
  21. Yes, you should turn it off. No, the tooltip is correct (although indeed somewhat confusing) because performance issues are most likely to come if you turn it on (= pagefile used, more disk activity, Windows becomes slower etc.). We want to use the RAM here, not the pagefile. Some confusion may arise because a user intuitively assumes that "performance issues" could be caused by the ~300MB needed by EAM so the user feels the option should be on (= less RAM used). It seems like extra, unnecessary RAM usage. But it is not. Most systems can spare 200-300MB of RAM nowadays and that option should only be enabled in critical situations, like not having enough RAM to even open and run programs, for example.
  22. Am I wrong in assuming that EAM initially decides on its own whether to enable that option or not? I seem to remember on a PC with limited memory that it was turned on by default. Tarnak, if you have enough memory you should let EAM use it and leave that option disabled - everything will work better this way.
  23. I also confirm an unusual amount of issues (already reported) with some programs crashing or displaying high CPU usage, all caused by the recent EAM updates. 2018.8 is fine. Excluding/disabling doesn't work (this makes me wonder about the effectiveness of these options), only a full EAM uninstall does, or a switch to 2018.8.
  24. That is not a given at all. They are very different browsers now and distance in only growing. Such a "merge" might not even be applicable due to the aforementioned differences, both in underlying technology and even developer mentality. In any case, we will see. Now Surf Protection works, as always. The future? No one can predict that.
  25. Try Pale Moon, one of the few sane browsers left. Zero issues with Surf Protection, too.