Search the Community

Showing results for tags 'fixed'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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 71 results

  1. when u click "always block this" , there is no responding test with latest beta 7318 ,window 7 x64
  2. 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?) https://support.emsisoft.com/topic/26833-bootvorgang-korrumpiert/#comment-167652 a2guard_20170226055045(3236).zip ev4.zip
  3. EIS 2017.7.0.7797 Office365 (all versions) The Office365 installer launches Powershell. Powershell code triggers Emsi's anti-exploit protection.
  4. EAM on Win 7 64 bit after manual update from 7797 I did a block all rule for mspaint to test fix. This is warning I get when I tried to run it.
  5. Emsisoft Anti-Malware and Emsisoft Internet Security 2017.6.0.7640 In new "Email Notifications" window, "Ok" button should be "OK".
  6. Frank, please PM me and I will provide you a download link for the *.bat and password. Video is .mp4 format. Delete Shadow Copies.mp4
  7. Using the latest EAM 2017.3.0.7318 beta on Win 7 HomePremium SP1 x64. Some good files in behavior blocker tab are still marked as Unknown. In stable version those are also shown first when I open GUI but are removed after few seconds. Online check confirms them as Trusted in AMN. Are there some AMN problems?
  8. On 6963 and 6971 there is a small graphics error and I have been trying to find what triggers it and an the moment I cannot. Perhaps it is a Windows session thing I don't know. I do a malware scan, look at reports, etc then back to main GUI then open logs and I see this in the screenshot.
  9. EAM on Windows 7 64bit. Turned on laptop and was logged in with a temp profile. Logged out and back into my own profile. EAM started autoupdate and never finished it. Some things such as taskmanager etc were slow to respond. In the end I rebooted (went straight to my own profile as normal this time) EAM has not attempted to update again and still says last update was yesterday when I hover over taskbar icon. I may attempt manual update later, however I think something is broken Find attached debug logs, screenshot of GUI and update log. update log.txt a2service_20170201065719(1116).zip
  10. EAM 2017.4.1.7484 beta on Windows 7 SP1 x64 HomePremium always installs a2dix64.sys component....as many times as I try to update it.
  11. 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.
  12. 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.
  13. Just wondering why description for ZAM.exe is missing in BB list (beta 6716)
  14. 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. Logs.zip
  15. Two Desktops and 1 VM updated automatically. So far so good
  16. 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. https://support.emsisoft.com/topic/26936-event-viewer-errors-in-win-7-build-7207/ Find more debug logs attached for this attached a2service_20170225060458(3056).zip
  17. 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 12.0.0.6828 with the new BB engine, Beta enabled See logs and picture Logs.zip
  18. Big bugs in the update package size of I've installed version EMSISOFT IS 12.0.1.6859. I got within three days I checked the update package size. The first day about 24 MB. The second day is about 42 MB. The third day is about 49.5 MB. Why does this update package size is too much. I updated version of the high volume of daily 11 EMSISOFT the problem I had, and I support the report, but the company did not fix it. There is also the problem now in version 12. Please make this big problem. (Total size of the database BitDefender Antivirus is published on a weekly basis is about 170 MB), but EMSISOFT receives 50 megabytes per day.? Respectfully
  19. 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
  20. EAM ..Win 7...6844 I have seen this twice in the last week ....Event ID 1530 warning It happens at shutdown warning.txt
  21. 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
  22. 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''
  23. Win 7 smooth autoupdate to 7035 Did a reboot afterwards to see if update was still there....it 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
  24. 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.