HazBeen

Member
  • Content Count

    44
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by HazBeen

  1. Popup notification from EAM saying it is unable to contact its update server, here in USA too. Using staff member GT500's cmd_update.bat to perform an update, signatures begin to download, then are interrupted...
  2. I've never used Powershell, so I'll happily remove it after learning Powershell creates a vulnerability. Thanks, Fabian !
  3. Today, I also have been experiencing these update connection failures, however -- just now -- EAM successfully updated !
  4. Just noticed this similar complaint over on the EIS Support discussion board. Good luck!
  5. I have not experienced any problem with EAM updating over the past couple of days, and the Emsisoft download link in your post is accessible for me using Chrome to begin the download. When I experience any accessibility problem, I use DownForEveryoneOrJustMe to determine if the desired site is working, or if the problem might be my own setup. Perhaps your firewall or some other security component on your computer is blocking your connection to Emsisoft's download servers? Good luck!
  6. Arthur: Yes, the issue is fully resolved. I fell back to Delayed updates, and then cycled through Stable updates and Beta updates -- with OS restarts in between each step -- and the issue has been totally eliminated across the board. Thank you for your followup and for everyone's efforts that fully resolved this issue. It is customer service like this that validates my past decision to upgrade from Vista to Windows 7 in order to remain an EAM user. Good luck!
  7. I offer sincere appreciation for the Development Staff's prompt action. Beta Update 2016-02-27 has totally eliminated this problem with EAM Beta version 11.5.0.6191. Good luck!
  8. Emsisoft's malware database lists numerous variants of that file as being infected. EAM uses Bitdefender's malware signatures, and Bitdefender's malware database lists that file as indicative of the win32.worm.mabezat family. You should probably seek guidance through Emsisoft's "Help, my PC is infected" Forum, to ensure that this potentially serious infection is removed from your PC. Good luck! ** Updated - Sorry, I was unaware that you received a clean-PC pronouncement elsewhere. **
  9. Arthur: I appreciate your guidance on submitting Debug Logs, which I have e-mailed through the Support UI. Just in case this information is useful... The nearly 1.6 million entry a2user.dat file size is 73.8 Mb. The 12,500 entry a2user.dat file size is 1.2 Mb. The 12,250 entry a2user.dat file size is 1.1 Mb. Good luck!
  10. It is true that this problem is not related to the several Stable Update Hotfixes, but that the problem began after this Beta Update. In an effort to determine the threshold of entries in the a2user.dat file that triggered the error message, I incrementally reduced the number of entries in the a2user.dat file. I found that with EAM beta version 11.5.0.6182, and 12,500 entries in the a2user.dat file, the following Error Message occurred without the User Interface opening when I right-clicked on the EAM Tray Icon and selected "Host rules". When the a2user.dat file is reduced to 12,250 entries, no error message occurs and the User Interface opens with the Hostname List immediately populated. Good luck!
  11. For nine months, EAM's Surf Protection has been successfully running custom a2user.dat files containing up to 2.5 million undesirable URL entries, and I am currently running an a2user.dat file containing 1.6 million entries. I have always been impressed that these large numbers of entries in the a2user.dat file have not slowed the Surf Protection feature or negatively impacted EAM. The February 23rd beta update, to EAM version 11.5.0.6182, is causing a repeating error message when attempting to access the Surf Protection page of the GUI by right-clicking on the EAM Tray Icon and selecting "Host rules". If I right-click on the Tray Icon and I select "Security Overviews", the GUI will open. If I then select "Surf Protection" from the Overview GUI page, the Surf Protection page will be presented, but the Hostname List will not populate for about 45 seconds. And sometimes, the Hostname List will not populate and an error message will occur. Replacing the custom a2user.dat file, with an empty (zero entries) a2user.dat file, totally eliminated the error messages and, whether using the Tray Icon or the "Security Overviews" access points, the Surf Protection page's Hostsname List populates immediately with EAM's built-in list. Changing from Beta Updates to the Stable Update channel, returned me to using EAM version 11.5.0.6131, which now runs my original 1.6 million entry a2user.dat file without any error messages and it immediately populates the Hostname List when the Surf Protection page is revealed. I'll stay with the Stable Update channel until a correction is offered through Beta Updates. I can provide you the a2start.el Eureka Log, if that would be helpful. Good luck!
  12. I placed the batch file inside my Program Files/Emsisoft Anti-Malware folder and created a Desktop shortcut, which I execute using Right-Click/Run as administrator. The update feed is determined by the Beta-Stable-Delayed selection in the Update Settings of the GUI, and not by the Commandline Scanner parameters, as described in the attached image. While its release was inadvertent in this case, I offer thanks to Fabian & Arthur for their Commandline Update batch file, which is an enjoyably efficient updating tool. Good luck!
  13. Yilee: Regarding your desire to obtain Signature-only updates that require no reboot, this post by Fabian Wosar from 2010 offers two methods to achieve your wish. I just tried the EEK method that Fabian describes, and it worked for me after restarting EAM only, with no System reboot. Perhaps that method can satisfy your needs. Regarding your demand for a decent answer to what's going on with this (Win 7 x64 EAM Tray Icon) issue, Emsisoft Employee Arthur Wilkinson (a.k.a. GT500) has already offered that in Post #6, above... "our QA team has been able to reproduce this, and is working with our developers to determine the cause of the issue" and "Hopefully it won't take much longer to debug this and provide a viable workaround." Good luck!
  14. After several updates using the Beta channel, EAM and its Tray icon continue to operate normally for me. I am running an Administrator account with Win 7 Pro x32. Good luck!
  15. I returned to Beta Update setting, updated & rebooted, and EAM tray icon is now visible on startup, and protection is fully active. Problem solved for me using Beta Update channel. Thank you !!!
  16. I noticed Fabian's post in the HMPA thread mentioning that the hotfix was pushed out to Beta Update users. I reverted to Stable updates in Settings, ran an update & rebooted, and the EAM startup tray icon problem was eliminated. Will remain on Stable Update setting until the HMPA hotfix tray icon issue is solved. Good luck!
  17. HMPA hotfix also broke startup of beta update EAM version 11.0.0.6131 for me, running Win 7 Pro x32. I am not a HMPA user. With "Enable real time protection at startup" checked in Settings, after PC Startup, "a2AntiMalware" service is running along with "a2Guard.exe" process, but "a2Start.exe" process does not run. Manually starting EAM from Start Menu creates a second instance of "a2Guard.exe" process to run, and "a2Start.exe" to run and EAM tray icon appears. After period of time, "a2Start.exe" process disappears from Task Manager and EAM tray icon remains. I have tried unchecking/rebooting & rechecking/rebooting "Enable real time protection at startup" in Settings, but this provided no improvement. Will be manually starting EAM after all reboots to assure full protection, until an update correcting this problem is pushed out. I see in the EIS Support Forum that this problem is also affecting EIS users following the HMPA hotfix. Good luck!
  18. The "My own" rules for Surf Protection are stored in the "a2user.dat" file, within the "Program Files/Emsisoft Anti-Malware" folder. This is a text-format file that can be viewed and edited using MS Notepad or MS Word while EAM is running. Saving an edited "a2user.dat" file requires shutting down protection by right-clicking EAM's icon in the notification area of the Taskbar and selecting "Shut down protection", as well as the stopping of the "a2AntiMalware" service using Windows Task Manager. Regardless of the origin of the "My own" rule that is presenting the problem, it is possible to remove any-or-all of the "My own" rules, and to save the edited file using the above method. Also, make sure the saved file name remains "a2user.dat" and is not changed into "a2user.dat.txt" by MS Notepad or MS Word in the "Program Files/Emsisoft Anti-Malware" folder. Then, the "a2AntiMalware" service can be re-started and EAM re-started. Once EAM is fully running, the EAM icon in the notification area of the Taskbar can be right-clicked and "Host rules" selected. Surf Protection rules that have been deleted should no longer show up in the rules list and, hopefully, their problem-effects should also be gone. Merry Christmas!
  19. A successful EAM update just occurred for me. Thank you for your corrective efforts!
  20. I am also experiencing the same no-update condition with my EAM v11.0.0.5984 running Windows 7 Pro. There is no problem with my Internet connection. All my other programs are regularly updating. No successful EAM update in the past 4 hours, with another previous 41/2 hour gap in successful Updates. Prior to today, no update problems. Switching from Beta to Stable update channel makes no difference. Is there an availability issue occuring with the Emsisoft Update Server ? Good luck!
  21. Based upon the "My own" entries showing in your Surf Protection rules, you must be importing a custom Hosts file. What Hosts file source(s) are you using to compile your "My own" rules? Based upon the time stamps, is it possible the blank rule is a corrupted entry that was imported from your Hosts file? Good luck!
  22. iWarren: It's true that there are competing philosophies -- opinions -- about Hosts file usage. However, that question is moot to this discussion, because using HostsMan and the above-mentioned block list providers is only the means-to-the-end of creating the "a2user.dat" file which Surf Protection uses to affect connection blockages by any application on the computer. Once again, after the custom Hosts file is compiled by HostsMan, that existing custom Hosts file is deactivated and has no effect upon the computer and its connections. Surf Protection performs all the blocking actions with the added benefit of screen notifications and the logging of blocking activity, which is especially useful in recognizing and correcting False Positives in the "a2user.dat" file list. Surf Protection's notifications & logging enabled me to recognize connection behavior by a mainstream Password Manager that compromised my confidence in the Password Manager, which I decided to delete. My Firewall judged the Password Manager as legitimate, so those connections would have otherwise been allowed and I would have had no awareness of what was happening in the background. I hope this clarifies my perspective on your concerns, but feel free to make no customization to Surf Protection, if that is what you prefer. Good luck!
  23. In my experience, there is a substantial overlap of sites listed among the block list sources I describe above, which makes HostsMan necessary to eliminate duplicates from the finally-compiled custom Hosts file. I've not recognized any duplication of the blocked sites listed in Surf Protection's built-in block list after installing my manually converted custom Hosts file as "a2user.dat". Either Surf Protection is eliminating duplicate listings, or, Emsisoft's block list data source is entirely unique and, perhaps, more fully zero-day malware centered. It is understandable why Emsisoft does not incorporate the above-mentioned block lists in Surf Protection, because of the prevalence of False Positives. Customization of Surf Protection with a custom Hosts file enables users to tailor blocking actions to users' personal preferences and it removes Emsisoft from the duty of correcting somebody else's False Positives. Good luck!
  24. Before this thread is locked, let me express my appreciation of the user customization option that Emsisoft Surf Protection provides. I also appreciate that Emsisoft doesn't try to be all-things to all-people, even while I use multiple security products. I grew tired of Norton Internet Security consuming half my CPU with a multitude of features I didn't need, which led me to try nearly every Internet security product. I am a very satisfied Emsisoft customer, patiently waiting for non-beta Version 11 to be released. Good luck!
  25. I appreciate M0unds clarifying comments and I have replied to iWarren's question & concerns in the other discussion thread. Good luck!