pkolasa

Tester
  • Content Count

    10
  • Joined

  • Last visited

  • Days Won

    1

pkolasa last won the day on March 24 2014

pkolasa had the most liked content!

Community Reputation

1 Neutral

About pkolasa

  • Rank
    Member
  • Birthday 05/06/1991

Contact Methods

  • Website URL
    https://www.facebook.com/pkolasa91

Profile Information

  • Gender
    Male
  • Location
    Poland
  1. Absolutely no issues on all my machines (Windows 7 and 10). Auto-update went smoothly and swiftly.
  2. Hello, shortly after updating to the newest beta, I noticed that while update is in progress, Forensic logs falsely alert user to an update failed from not know reasons (Wystąpił nieznany błąd aktualizacji = An unknown error occured). As you can see in the box below (copied the entire log content) and on the screenshot attached, there is an information about files not being updated, moreover, the date is definitely wrong. This is nothing very important, and this error disappeared right away update was finished, but someone might be alerted to it as an error. Ogólne informacje: Wersja 2017.11.0.8219 Start aktualizacji: 26.11.2017 12:19:31 Koniec aktualizacji: 01.01.1970 Czas trwania: 12:19:31 Wystąpił nieznany błąd aktualizacji Szczegółowe informacje: 62 Modułów, 23826551 Bajtów a2hosts.dat (3741 Bajtów) - Nie zaktualizowano a2trust.dat (464 Bajtów) - Nie zaktualizowano Signatures\20171126.sig (2066 Bajtów) - Nie zaktualizowano Signatures\BD\dalvik.ivd (341 Bajtów) - Nie zaktualizowano Signatures\BD\e_spyw.i00 (1605 Bajtów) - Nie zaktualizowano Signatures\BD\e_spyw.i15 (194527 Bajtów) - Nie zaktualizowano Signatures\BD\e_spyw.i16 (220104 Bajtów) - Nie zaktualizowano Signatures\BD\e_spyw.i17 (323 Bajtów) - Nie zaktualizowano Signatures\BD\e_spyw.i18 (345017 Bajtów) - Nie zaktualizowano Signatures\BD\e_spyw.i19 (333021 Bajtów) - Nie zaktualizowano Signatures\BD\e_spyw.i20 (4068 Bajtów) - Nie zaktualizowano Signatures\BD\e_spyw.i21 (414471 Bajtów) - Nie zaktualizowano Signatures\BD\e_spyw.i22 (386263 Bajtów) - Nie zaktualizowano Signatures\BD\e_spyw.i23 (4248 Bajtów) - Nie zaktualizowano Signatures\BD\e_spyw.i24 (3236 Bajtów) - Nie zaktualizowano Signatures\BD\e_spyw.i25 (378528 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.000 (348504 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.379 (693 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.385 (310 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.391 (116416 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.393 (138395 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.394 (264 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.396 (78177 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.403 (163515 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.404 (173824 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.405 (147370 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.407 (2309 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.408 (113037 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.409 (2706 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.410 (247725 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.411 (171290 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.412 (207364 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.413 (216947 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.414 (190591 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.415 (225605 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.416 (34724 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.417 (258129 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.i05 (767284 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.i06 (34763 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.i07 (848710 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.i08 (827222 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.i22 (92423 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.i25 (754197 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.i26 (766946 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.i27 (453822 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.i29 (853650 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.i32 (295449 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.i38 (744114 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.i50 (597311 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.i55 (706835 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.i56 (694485 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.i57 (719537 Bajtów) - Nie zaktualizowano Signatures\BD\emalware.i61 (735254 Bajtów) - Nie zaktualizowano Some explanations because of Polish language used in the log: Start aktualizacji = Start of update Koniec aktualizacji = End of update Czas trwania = Duration Nie zaktualizowano = not updated And the issue can be seen also on the following screenshot:
  3. Smooth update once again on my W10 Insider 17046. No major issues, except the one about which I'll open a new ticket in a moment.
  4. Update as smooth as always, but strange thing I noticed was that protection off time was quite longer than previously, where after the restart Emsisoft interface reported protection as enabled almost instantly.
  5. I am on W10 Insider build 17004, but in the latest EAM I have exactly the same behaviour. I get information, that EAM is installed, but that I have to open it to get status information. Seems MS broke something in getting information from Emsi AV.
  6. I get the same observation as stapp before. Opened GUI, quickly clicked through tabs in Options and Protection sections and yes, Forensics shows every non-default setting (see attachment, top part). Moreover, I noticed strange thing - after scan completes (in this case a scheduled USB scan), I get information about scan with empty name being canceled (also in the attachment, highlighted. And yes, I went to menu and canceled this scan, just wondering about the name.).
  7. In my case update went fine, but (I think this is a bug) I got two independent program restart notifications. One in a form of toast notification with yellow bar and blue Restart text and second in form of a normal popup with Yes and No to choose. I clicked on Restart in toast, toast disappeared, but program still waited for reply in normal window. It also showed me the main Emsisoft console, which, after agreeing to restart, just hanged (see attachment, sorry for Polish, but the Windows popup says that a process is not responding and asking me if I want to kill it). After killing and manually running Emsisoft Guard again, I got the update completed popup.
  8. I'll cling to that topic, other than create mine. On mine similarly, no issues. Other that self-hiding tray icon (which should be set to be on top in Windows), but that's not anything important.