Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 11/03/20 in all areas

  1. That's not correct - there's been several attempts, and discussions about it here and on the Beta forum. And for many of us the problem did seem to be fixed. You've posted several times in this thread so - unless you didn't stay uptodate reading it between your posts - you should have known that.
    1 point
  2. We thought this was fixed. With no one reporting that the issue was still happening, we had no way to know it was still a problem. We're going to need to know which process is using too much CPU time. If you're on Windows 10 then please be sure to switch to the Details tab in Task Manager so that you can give us a process name that ends in .exe rather than one of the "friendly" names that appear on the Processes tab. We will also need debug logs from anyone still having this issue. Here's how to enable debug logging: Open Emsisoft Anti-Malware. Click on the little gear icon on the left side of the Emsisoft Anti-Malware window (roughly in the middle). Click Advanced in the menu at the top. Scroll to the bottom of the Advanced section, and change the option for Debug logging to Enabled for 1 day. After that, close the Emsisoft Anti-Malware window. Restart your computer. If you're on Windows 8.1 or Windows 10 then restart by right-clicking on the Start button, going to Shut down or sign out, and selecting Restart from this list to bypass Fast Startup. Reproduce the issue you are having (wait until the CPU usage gets high). Here's how to send us the debug logs once you've been able to reproduce the issue: Open Emsisoft Anti-Malware. Click on the little icon in the lower-left (right above the question mark) that looks like little chat bubbles. Click on the button that says Send an email. Select the logs on the right that show today's dates (if you try to send too many logs, then we may not receive them). Fill in the e-mail contact form with your name, your e-mail address, and a description of what the logs are for (if possible please leave a link to the topic on the forums that the logs are related to in your message). If you have any screenshots or another file that you need to send with the logs, then you can click the Attach file button at the bottom (only one file can be attached at a time). Click on Send now at the bottom once you are ready to send the logs. Important: Please be sure to turn debug logging back off after sending us the logs. There are some negative effects to having 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.
    1 point
  3. It seems to be fixed for me now in 2020.11.0.10501 stable release.
    1 point
  • Who's Online   0 Members, 0 Anonymous, 51 Guests (See full list)

    • There are no registered users currently online
×
×
  • Create New...