High CPU usage

[Minimalist]

For some time now I have problem with high CPU usage from Emsisoft Anti-Malware whenever I install Emsisoft AM.

Emsisoft Security Center (or emsisoft Anti-Malware serrvice) starts to use 15-20% of CPU. When I open Interface it hangs with Not responding indicator and you can't do anything. Only way to stop this is to right-click on systray icon and shutdown protection. After I turn protection back on, problem happens again after a while.

How can I find cause of this problem?

 

 

[Minimalist]

Some additional information. I run Windows 10 21H2 with all updates till April 12 installed. I use EAM latest version with stable release feed.

I don't use any other real-time security software, except Macrium Reflect with it's Image Guardian component installed and configured.

It looks like I can trigger this behaviour with opening EAM's interface, navigating through settings and then closing it down (without changing any settings). It doesn't happen every time but sometimes a2start.exe starts consuming CPU.

I've created a2start.dmp file during high CPU usage. Tell me how to safely send it for analysis if needed.

[ShadowPuterDude]

Hello @Minimalist,

You can send the dump file to [email protected]  If it is too large to email, you can send the file to us via https://wetransfer.com/

Be sure to reference this thread in your message.

[Minimalist]

I've sent you email with link to download dump file.

Currently I have  EAM uninstalled to avoid high CPU usage but will reinstall it to test possible solutions.

[ShadowPuterDude]

We have received your dump file.  I have alerted our Development team.

Additionally, it may be beneficial to obtain a set of debugging logs from Emsisoft.

1. Open Emsisoft Anti-Malware, then click the Settings tile, then the 'Advanced' tab. Scroll down a bit, then use the last option in the advanced section, 'Debug logging', to enable debug logging for one day. Leaving it on always isn't recommended because logs will fill the hard drive eventually. Close the Emsisoft Anti-Malware window after making your selection.

2. Restart the computer. This is mandatory for the logs to be created completely.

3. Reproduce the issue you are having, twice if possible. The issue must occur, or the logs won't be of any use.

4. (Please read the note below before continuing) Once you have reproduced the issue, open Emsisoft Anti-Malware again, and click on the Support icon which is the chat bubble in the lower-left corner, then click on the button that says "Send an email". Select everything in the right-hand column that shows today's dates. Fill in the e-mail contact form, then click on "Send now" at the bottom once you are ready to send the logs.

Note: If you like, you may just compress and email or upload to a file-sharing location the following folder instead of using the in-program form, skipping step 3: C:\ProgramData\Emsisoft\Logs\ (note ProgramData is a hidden folder) and also C:\Program Files\Emsisoft Anti-Malware\Logs\Logs.db3.

5. *Important* Please be sure to turn off debug logging after sending us the logs. There are some negative effects to leaving debug logging turned on, such as reduced performance and wasting hard drive space, and it is not recommended to leave debug logging turned on for a long period of time unless it is necessary to collect debug logs.

[Minimalist]

I've sent you collected logs using built-in option. I left a2start.exe using CPU (one core -12,5%) for few minutes to collect enough data.

[ShadowPuterDude]

I'll let you know what our dev team determines.

[ShadowPuterDude]

Could you please enable the Beta channel, and let me know if that resolves the high CPU usage issue.

Please enable Beta updates and see if it helps:

  1. Open Emsisoft Anti-Malware.
  2. Click the blue Settings tile, then click Updates in the top row.
  3. Find the Update feed drop-down menu and change it to Beta.
  4. Click the 'home' icon in the top left to return to the overview screen, then press the Update now link.
  5. It may be necessary to reboot the computer when it's finished updating for the beta's fixes to work, but this is normally not needed.

Please switch back to the stable version after a week has passed, or when we contact you with information, even if the beta works. Beta releases are just that, beta, and may be unstable in some cases. You may learn more about when releases come out, here: http://changeblog.emsisoft.com/

[ShadowPuterDude]

Actually, please ensure that you are on the latest stable release, which is 2022.5.1.11474.  As we pushed the the beta release to the stable channel a couple of hours ago.

[Minimalist]

Hello.

I installed latest version and so far could not reproduce the problem. So it seems to be fixed.

One additional question. After install I noticed new shortcut pointing to a2guard.exe. I don't remember seeing that in previous versions. Is this OK?

[ShadowPuterDude]

Thanks for the feedback on the latest stable version fixing the high CPU usage issue.

The new shortcut, is just a change is naming convention.  You can safely delete the old shortcut.