stapp

Global Moderator
  • Content Count

    3163
  • Joined

  • Last visited

  • Days Won

    54

Everything posted by stapp

  1. It is recommended to upload a copy of the ransom note along with an encrypted file to ID Ransomware so that you can verify which ransomware you are dealing with to this site here: https://id-ransomware.malwarehunterteam.com/ You can paste a link to the results into a reply so that one of our experts can review them.
  2. EAM doesn't work on XP or Vista now. System requirements are :- For Windows 7/8.1/10, 32 & 64 bit
  3. Follow the steps here https://support.emsisoft.com/topic/31280-gerosan-file-encrypted-please-help/?tab=comments#comment-193731
  4. It is recommended to upload a copy of the ransom note along with an encrypted file to ID Ransomware so that you can verify which ransomware you are dealing with to this site here: https://id-ransomware.malwarehunterteam.com/ You can paste a link to the results into a reply so that one of our experts can review them.
  5. Follow the instructions here https://support.emsisoft.com/topic/31280-gerosan-file-encrypted-please-help/?tab=comments#comment-193731
  6. ..and my next update just now replaces the file with another
  7. It comes the same time as EAM gets an update?
  8. I recommend uploading a copy of the ransom note along with an encrypted file to ID Ransomware so that you can verify which ransomware you are dealing with: https://id-ransomware.malwarehunterteam.com/ You can paste a link to the results into a reply so that they can be reviewed
  9. I recommend uploading a copy of the ransom note along with an encrypted file to ID Ransomware so that you can verify which ransomware you are dealing with: https://id-ransomware.malwarehunterteam.com/ You can paste a link to the results into a reply so that they can be reviewed
  10. Just pointing out to the experts that you have the same thread running here https://www.bleepingcomputer.com/forums/t/698808/new-ransomware-ive-never-heard/?hl=%2Bburan#entry4801969
  11. I recommend uploading a copy of the ransom note along with an encrypted file to ID Ransomware so that you can verify which ransomware you are dealing with: https://id-ransomware.malwarehunterteam.com/ You can paste a link to the results into a reply so that they can be reviewed
  12. I recommend uploading a copy of the ransom note along with an encrypted file to ID Ransomware so that you can verify which ransomware you are dealing with: https://id-ransomware.malwarehunterteam.com/ You can paste a link to the results into a reply so that they can be reviewed.
  13. Emsisoft Protection Platform cannot stop you going into safe mode. You should be able to access safe mode from the Automatic Repair Screen. Advanced Options > Troubleshoot > Advanced Options > Startup Settings > Restart and select either 4 or 5.
  14. Devs are aware Batman https://support.emsisoft.com/topic/31178-beta-9469/?tab=comments#comment-193231
  15. Upload a copy of the ransom note along with an encrypted file to ID Ransomware to verify which ransomware you are dealing with to this site here: https://id-ransomware.malwarehunterteam.com/ You can paste a link to the results into a reply so that one of our experts can review them.
  16. In all the years I have been sending debug logs I have always captured the event before zipping and sending the logs. I don't need anymore instructions on how to do it. I am finished with this thread now.
  17. I do not understand why you are telling me this. I have been right-clicking and selecting..send to compressed zip.. on in use debug files for years now. There is no need to copy them to another folder. The action of sending them to compressed zip from the context menu copies them.
  18. Upload a copy of the ransom note along with an encrypted file to ID Ransomware to verify which ransomware you are dealing with to this site here: https://id-ransomware.malwarehunterteam.com/ You can paste a link to the results into a reply so that one of our experts can review them.
  19. ? I got rid of all logs including debug logs to see if it still happened when debug logging was restarted... it did. All debug logs I deleted from ProgramData.
  20. I wanted to start with a clean slate so I got rid of everything (by the way the reset counters also gets rid of the 'malware objects detected'' number on the main gui)
  21. Jeremy I have send debug logs to the devs the same way for years.. and they are complete up to the time that I do it. As regards the context menu corruption , when I highlight the 3 logs and right-click the context menu appears and immediately disappears. I purged all logs via the gui (Settings.. Advanced.. Factory defaults.. Revert.. clear all logs and reset counters.) I also turned off debug logginging and deleted all logs inside ProgramData Emsi folder. After turning debug logging back on the same issue occurs with the in use debug logs. The a2service logs contain an access denied error which may have some relevance. It is a form of corruption of EAM debug logging just on this machine, so I doubt it will have a high priority.
  22. I guess my logs about it weren't of any interest either
  23. As there has been no comment from devs on how this context menu corruption of EAM debug logs may have occurred, I guess I'll just forget it for now.
  24. On another 1903 Pro machine which I have just updated to beta 9469, I am able to right-click on any of the in use debug logs and select send to zip. In other words the context menu works for in use debug log files on that machine. I can only assume that the context menu of the EAM debug logs has become corrupt in some way on the other machine. I have purged all logs from the GUI and also by turned debug logging off and on but it makes no difference. That is the only area of that machine where the context menu is affected. I may just have to do a reinstall of EAM without any further ideas.