stapp Posted November 24, 2016 Report Share Posted November 24, 2016 EAM on Win 7. After autoupdating to a new build I always do a malware scan. It took 15 minutes I think I will do a reboot and try again. Link to comment Share on other sites More sharing options...
stapp Posted November 24, 2016 Author Report Share Posted November 24, 2016 Rebooted and doing another malware scan.... it's taking ages Seems to be really struggling in c\windows Link to comment Share on other sites More sharing options...
JeremyNicoll Posted November 24, 2016 Report Share Posted November 24, 2016 What sort of times do you see normally? Link to comment Share on other sites More sharing options...
stapp Posted November 25, 2016 Author Report Share Posted November 25, 2016 Around 4 to 5 minutes on first malware scan in a windows session. Link to comment Share on other sites More sharing options...
redactor Posted November 25, 2016 Report Share Posted November 25, 2016 FWIW, manual malware scan immediately after auto update to 6956 took 39 seconds (Win10 Pro x64 installed on a SSD) -- minus Documents folder contents, which I've hard-linked to a separate HDD. Also, the problem of non-functioning Stop and Pause buttons during scan, which I reported in another thread a few days ago, has gone away in this build. Link to comment Share on other sites More sharing options...
stapp Posted November 25, 2016 Author Report Share Posted November 25, 2016 I need some help here with the malware scan on Win 7 using EAM. I have tried rebooting etc but nothing helps, It just crawls through C\Windows\Installer for instance. It goes fast through the first 4 stages and then on stage 5 it seems like it's using a different method. Will debug logs show anything? If not what can I send you to help you understand what I am experiencing on Win 7 using 6956? Link to comment Share on other sites More sharing options...
Siketa Posted November 25, 2016 Report Share Posted November 25, 2016 I can confirm there is a slowdown, especially in the fifth step, comparing to the older versions. On my system that is not an issue cause it is pretty fast anyway (3-4 mins on SSD)... scan_161028-194524_old version.txt scan_161125-180255_new version.txt Link to comment Share on other sites More sharing options...
stapp Posted November 25, 2016 Author Report Share Posted November 25, 2016 As there is no feedback so far, I will attach debug logs of a very long malware scan. a2service_20161125142702(1092).zip Link to comment Share on other sites More sharing options...
Orlando Pivi Posted November 26, 2016 Report Share Posted November 26, 2016 Hi Guys, Thank you for your report. It seems I can confirm the issue. Could you please provide us scan engine debug logs? These will help us on finding better the problem. You can create them by creating a DWORD value "EngineDebugOutput" in HKEY_LOCAL_MACHINE\SOFTWARE\Emsisoft\ and setting it 1. Then restart your computer to save settings, logs are saved in |your EAM/EIS folder| (NOT the normal debug folder) as "ScanEngineDebug.log". After the restart, try to reproduce the problem. NOTE: once you reproduced the problem do NOT restart your computer or service as logs will be replaced with new ones. It is enough you send us ScanEngineDebug.log after reproducing the problem. Thank you, Orlando Link to comment Share on other sites More sharing options...
stapp Posted November 26, 2016 Author Report Share Posted November 26, 2016 Is this right? Because there are no logs in EAM folder. I did a reboot after setting registry. I did the 32 bit dword value not the 64bit one. Link to comment Share on other sites More sharing options...
Orlando Pivi Posted November 27, 2016 Report Share Posted November 27, 2016 Hi Stapp, Please be sure to insert that value here: HKEY_LOCAL_MACHINE\SOFTWARE\Emsisoft\ in "Emsisoft" key (please make a key called "Emsisoft" as there is not). You are created it in "Emsi Software Gmbh" Let me know if there is anything! Thank you! Orlando Link to comment Share on other sites More sharing options...
stapp Posted November 27, 2016 Author Report Share Posted November 27, 2016 Ahh, you did not say at first that I would have to create a key as well Will do soon. Link to comment Share on other sites More sharing options...
stapp Posted November 27, 2016 Author Report Share Posted November 27, 2016 scan engine debug log for win 7 attached Also see here http://support.emsisoft.com/topic/25530-ausnahmen-werden-ignoriert/#entry163182 ScanEngineDebug.log Link to comment Share on other sites More sharing options...
stapp Posted November 28, 2016 Author Report Share Posted November 28, 2016 I see you have locked my feedback reports in the EEK beta area. What is the point of having that section if you don't allow posting of info into it? Sometimes products behave differently, so because I went to the trouble of getting ScanEngineDebug logs for you then perhaps you would be good enough to accept them Here is the ScanEnginDebug log for EEK. It looks different to the EAM one but still has the same problem. ScanEngineDebug (2).log Link to comment Share on other sites More sharing options...
Orlando Pivi Posted November 28, 2016 Report Share Posted November 28, 2016 Hi Stapp, Thank you for logs, I added them to our tracker! What is the point of having that section if you don't allow posting of info into it? As I mentioned in the other thread, engine used by Emsisoft product is the same, so the problem is reflected in both products. I closed there to not split this issue (as it is one) in two different threads to follow. Once the problem will be fixed in Anti-Malware will be fixed automatically in the Emergency Kit too. Orlando Link to comment Share on other sites More sharing options...
stapp Posted December 9, 2016 Author Report Share Posted December 9, 2016 Slow EAM malware scan issue is now fixed for me on Win 7 and scan times have returned to normal. Thanks devs Link to comment Share on other sites More sharing options...
Fabian Wosar Posted December 9, 2016 Report Share Posted December 9, 2016 Yes. We released an update earlier today that should fix the issue. Link to comment Share on other sites More sharing options...
JeremyNicoll Posted December 9, 2016 Report Share Posted December 9, 2016 (edited) I'm following this topic, so just got emailed to say there were two updates to it. Not only did the emails NOT contain the new texts, neither of the links that they contained instead worked. In each case I ended up on a website page that said, eg for this link: http://support.emsisoft.com/topic/25809-malware-scan-using-6956/?do=findComment&comment=164045 an error message: Sorry, there is a problem We could not locate the item you are trying to view. Error code: 2S136/C (and I'm sure that this isn't the best place to report a forum problem, but I don't know where I should have done that) Edited December 9, 2016 by JeremyNicoll added parenthetical last comment Link to comment Share on other sites More sharing options...
Orlando Pivi Posted December 23, 2016 Report Share Posted December 23, 2016 Hi Jeremy, Thanks for your report, we will check it. Orlando Link to comment Share on other sites More sharing options...
Recommended Posts