Search the Community

Showing results for tags 'fixed'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Malware Research Center
    • Help, my PC is infected!
    • Ransomware First Aid
    • Malware and Computer Security
    • Malware submissions
  • Company & Products
    • Customer Support
    • Public Betas
    • Feedback, Comments and Suggestions
    • False positives
    • Emsisoft News
  • Other Languages
    • German Support - Deutscher Support
    • French Support - Assistance Française
    • Russian Support - Русская поддержка
    • Dutch Support - Nederlandse Support
    • Italian Support - Supporto Italiano
    • Polish Support - Polskie wsparcie

Found 60 results

  1. Updated EAM from 7213 to 7219 on Win 7 64bit. Turned laptop off. After a few moments turned it back on again (to confirm delay in boot fixed now) Then got to old user profile issue again. Had to log out and log in again as me. Attached are both sets of debug logs from the 2 boots this morning, plus the 4 event viewer errors 1508, 1502, 1515, 1511. Note the user profile service in this session said it had successfully started (1531) immediately before the errors. (Frank this user has a ticket with you for similar issue?) a2guard_20170226055045(3236).zip
  2. Hello. I have been doing some malware testing lately and I have come across four samples that completely crash real-time protection. After a reboot the notification icon is red, and after a few minutes I get a pop up as shown in the attachment. One of the samples from 03/16 is still zero-day as the signatures and heuristics don't pick it up along with the Behavior Blocker misses it. I have tested in both Oracle VirtualBox and VMWare with Windows 7, 8.1, and 10 and it occurs with all of them. I have forwarded 3 of the samples to customer service over a week ago, but I see this hasn't been addressed yet and was advised to start a thread in this particular sub-forum to get the most quick and direct feedback from a developer. Thanks.
  3. I use the old .bat files to keep debug logging on so I have logs for any reports I make. Took me a little while to figure out why I had no debug logs anymore. EAM automatically turns off debug logging after 7 days.
  4. Just wondering why description for ZAM.exe is missing in BB list (beta 6716)
  5. My EAM was updating to the latest stable released today. I received a notification popup (GUI was closed) but when I pressed Restart button nothing happened. EAM did not restart...even after few minutes. I had to manually restart PC in order to finish the update.
  6. Two Desktops and 1 VM updated automatically. So far so good
  7. In Windows Event Viewer under 'System' logs at each boot it shows 2 errors Event ID 7009 ''Description: A timeout was reached (30000 milliseconds) while waiting for the Emsisoft Protection Service service to connect.'' Event ID 7000 ''Description: The Emsisoft Protection Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.'' The effect of these 2 errors is that at boot there is a time of about 20-30 seconds where there is only a black screen with a cursor. I also reported the same for build 7207 and provided debug logs etc. Find more debug logs attached for this attached a2service_20170225060458(3056).zip
  8. After starting the computer Emsisoft was starting a scheduled scan. But when arriving on 82% the scan stopped and didn't progress. I'm unable to stop the scan even when closing the interface. After reopening the interface the scheduled scan apears to be stuck ad 82%. Unable to start new scan. I use build with the new BB engine, Beta enabled See logs and picture
  9. Just updated my EEK on Win 10 64 bit only to be told it is the wrong bitness and cannot be run. EEK froze when trying to finish installing the update. Did a couple of dumps from taskmanger. Both EEK 32 and EEK 64 were listed. However here are debug logs first. You probably won't need the dump files as obviously an error in the bitness update is the problem. a2emergencykit_20170126161633(4476).zip
  10. EAM ..Win 7...6844 I have seen this twice in the last week ....Event ID 1530 warning It happens at shutdown warning.txt
  11. EAM just autoupdated to EAM 6956 on Windows 7. After doing the requested app restart file guard is off I will turn it on manually. Noticed a brief glimpse of a countdown by numbers on slide ...should I have? Logs attached. a2service_20161124182439(2612).zip
  12. Perhaps instead of ''do not necessarily resolve in the same paths'' put.................. ''do not necessarily resolve to the same paths'' also ........... ''because the software protects on system level'' should be ...... .''because the software protects at system level''
  13. Win 7 smooth autoupdate to 7035 Did a reboot afterwards to see if update was still was Notice the first scan in a windows session takes twice the time as it does later in the same session. This is on a hard drive not SSD
  14. 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.
  15. Regarding this issue here I also noticed that if you are doing an EAM malware scan with the GUI on screen, and an update slide appears, the slide does not disappear until the scan is finished. Is this expected behaviour?
  16. EIS Windows 10 Home Version 1607 OS Build 14393.447 Shadow Defender EIS update freezes in Shadow Defender Shadow Mode. a2guard CPU will remain at approximately 15 %. This issue was caught "on-the-fly" so I collected an a2guard memory dump using Windows task manager. a2guard task manager memory dump attached. a2guard.7z
  17. On Win 7 went from 6508 to 6954. Update went really well, did it twice to get to new build of 12. I like the GUI. Even harder for people to find build number now!! Same problem as with new build of EAM... malware scan is going so slow through C\Windows \Installer it is barely moving at all
  18. EAM...Win 7.....6828 (Fresh stable install from website ) Installed and it did the manual updates thing during the install. I enabled beta updates and left all update settings at default... every hour. Just wondered why it then did an auto update 30 minutes later, or is that expected ?
  19. Hi Orlando I have one more Bug for you see my picture into the black circle With best Regards Mops21
  20. Hi I set my EIS update setting like image 1. EIS must update only at 4:00 but as you see in image 2 logs show something else and EIS update outside the time I choose. I think this issue exists on V11 too. thank you.
  21. EIS Windows 10 Home Version 1607 OS Build 14393.477 Reboot system > double-click EIS tray icon > GUI will open offset (partially off screen at bottom and right side) to the lower right corner of display It does not happen every single time, but instead most of the time Same happened in
  22. Hi Can you check the Crash Dump Files please With best Regards Mops21
  23. Hi Is this normal when a Component of Emsisoft Anti-Malware 12 updated and the Prog will restart the Application it will not reload it Ist das normal sobald eine Komponente geupdated wird das das Programm dann nicht neugestartet wird und checkt auch mal das Verhalten das beim Neustarten das beim Updatevorgang die Balken mit den weißen und schwarzen Balken nicht weiterläuft da er stehen bleibt With best Regards Mops21
  24. Using Win 10 found a small protection status glitch. From taskbar right-click option I shut down protection. Then in Task Manager I killed Emsi Protection Service ( I run with self protection disabled) Then after a minute or so I started EAM again using desktop icon. GUI reports file guard is off, taskbar right-click status says it is on. I had to click on it in GUI to get it to turn green, opening and shutting GUI wouldn't enable it.
  • Who's Online   0 Members, 0 Anonymous, 46 Guests (See full list)

    There are no registered users currently online