mik

Emsisoft Employee
  • Content count

    36
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mik

  • Rank
    Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

2071 profile views
  1. The issue has been fixed. The fix will appear in one of next updates.
  2. Working with them. Thanks/
  3. Thanks for your feedback. Could you please send me also Logs\logs.db3 file in private?
  4. CLOSED Forensic logs 7797

    Know problem. It is already fixed. The fix will be available a bit later.
  5. I hope you'll return it back when we'll publish new beta. You always help us with testing The logging shouldn't affect EEK's folder removing. It seems a2emergencykit.exe or another executable was not closed before try to remove the folder.
  6. Fixed. Unfortunately, your copy of EEK is now workable only on 32bit system. If you have no 32bit system then there is only way - download EEK installer from our site.
  7. CLOSED Autoupdate to 6954

    That is know issue of EEK V11. It is fixed in V12. Thank you for feedback.
  8. И Вам всего наилучшего
  9. Приятно слышать что у Вас всё заработало. С безопасностью проблемы не будет если у вас в ЕАМ включена самозащита (Настройки-Общие-Включить самозащиту).
  10. Добрый Вы правильно искали - файлы *.el должны быть в папке ЕАМ (если их там нет значит либо они были отправлены либо не успели создаться). Документацию по ОА Вы можете найти здесь. В Вашем случае нужно открыть "Options->Exclusions" и добавить там папку ЕАМ и затем перезагрузить комрьютер.
  11. День добрый. Отправляли ли Вы эти краш репорты нам? Ксожалению я их не вижу. Попробуйте добавить ЕАМ в исключения в ОА и перегрузить компьютер. Если не поможет тогда пришлите один из репортов мне в пм? (*.el в папке ЕАМ )
  12. DLL failure during nightly update

    Thanks for logs. The reason of the problem is not clear yet. Anyways, you are correct there is no need to test it on both systems. It will be enough to focus on one of them (on your choice).
  13. Emsisoft will not run

    Try current beta 4700 - the problem should gone.
  14. That is know problem. It appears when you have unchecked all week days. If you change 'Friday=0' to 'Friday=1'. The scheduled scans will become working. The problem is already fixed. The fix will be available in the next beta.