Jump to content

Can't Stop Scheduled Scan


Ken1943
 Share

Recommended Posts

With all of the processing happening in the background, sometimes it can take a few minutes for Emsisoft Anti-Malware to respond to you clicking the button to stop a scan. An SSD can actually make that worse, since files can be loaded into memory faster, and thus there is more CPU usage during the scanning process.

Link to comment
Share on other sites

21 minutes ago, JeremyNicoll said:

Would that be worse if scanning in an archive was being done - would EAM unpack the whole archive first?

The BitDefender scan engine will unpack an archive to the TEMP folder if the option to scan in archives is turned on (it can only be turned on when doing a Custom Scan).

Link to comment
Share on other sites

22 hours ago, JeremyNicoll said:

Unpacking: Ah ok, so that  couldn't be happening in a scheduled scan.

It can if the scan type is configured as Custom, and the scan options have been changed to enable scanning inside archives.

 

22 hours ago, JeremyNicoll said:

In a custom scan, would the BD engine respond to a Stop click in the EAM gui?   Or would the gui wait until the unpack was complete before next testing to see if Stop had been clicked?

Both scan engines are controlled by the UI.

I expect that unpacking would not stop until the entire archive was unpacked, however I don't know for certain. Regardless, when the worker threads are too busy, sometimes it takes some time before they can check whatever variable tells them to continue/stop to see if it has changed, and that is what causes the scan to continue after the 'Stop' button has been clicked.

 

22 hours ago, Ken1943 said:

Does Anti-Malware do it's own schedule or use Task Scheduler.

We have our own scheduler built in to the Emsisoft Protection Service.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...