stapp

Global Moderator
  • Content Count

    3176
  • Joined

  • Last visited

  • Days Won

    54

Everything posted by stapp

  1. 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.
  2. 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.
  3. 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.
  4. ? 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.
  5. 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)
  6. 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.
  7. I guess my logs about it weren't of any interest either
  8. 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.
  9. 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.
  10. On a different 1903 machine via autoupdater I saw this. I didn't see it on my other machine (that one has dark mode for slides.)
  11. Win 10 pro 1903 via autoupdater and a restart. No issues so far.
  12. I have always been able to send debug logs via right-click send to zip even on the day of the logs. As for deleting old ones I can do that any time without turning anything off.
  13. I have discovered that if I want to highlight and send on one the debug logs (for example a2service.log) I can only do it the following day. The logs for yesterday I can now highlight and send to zip. However the ones for today I cannot. Is EAM preventing this while they are in use?
  14. Win 10 1903.... EAM 9412 First thing I do each morning after boot is look at Forensics. This morning the 27th was not at the top of the list and I couldn't get them there. I had no problem with the log showing correctly yesterday. Thought I would send you the debug logs but I couldn't highlight each one (service, guard, start) and send to zip. The context menu just disappeared. I was able to highlight and send the logs folder itself though. There looks to be some 'access denied' lines in the service log. After quite a few clicks the 27th is now at the top as it should be. Logs.zip
  15. Just for info, released build of Win 10 1903 upgraded with EAM installed and running without any issues at all.
  16. 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.
  17. 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.
  18. 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.
  19. 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 then paste a link to the results into a reply so that one of our experts can review them.
  20. Did you try double clicking on Start Emergency Kit Scanner exe ?
  21. 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.
  22. It is recommended to upload a copy of the ransom note along with an encrypted file to ID Ransomware so that we can verify which ransomware you are dealing with to this site here: https://id-ransomware.malwarehunterteam.com/ You can then paste a link to the results into a reply in your thread here.
  23. Hello Matiu, Are you using Windows 10 64 bit? Have you tried restarting your machine? Was Emsisoft running okay and working before this problem happened? If you open Emsisoft and click on ''About'' at the bottom right-hand side of the screen what version number does it say you are running?
  24. 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 then paste a link to the results into a reply in your thread here.