GT500

Emsisoft Employee
  • Content Count

    12842
  • Joined

  • Days Won

    387

Everything posted by GT500

  1. Please try the instructions at this link, and let me know if they help.
  2. This is interesting, as the log shows EAM trying to use a rather odd port to connect to a local proxy. You don't use a VPN, do you?
  3. Just an FYI, I have been helping another user who has been having issues with OA showing incorrect information for files in C:\Windows\System32, and I posted some screenshots showing why. Online Armor's GUI is redirected to C:\Windows\SysWOW64 when it attempts to read C:\Windows\System32, and it cannot actually see the contents of C:\Windows\System32.
  4. Adding EAM to the exclusions in Online Armor should be all that you need to do. If you still experience issues after readding the exclusion, then please let me know.
  5. I've let our Sales Manager know about your request, and he will take a look at it as soon as he can.
  6. Yes, I got it. Unfortunately it's not the entire log. May I ask if you changed the format when saving the session data in Fiddler?
  7. If you right-click on the file, then go to Send to, and select Compressed (zipped) file Windows will ZIP the file and you can attach it.
  8. jade4, did you have a chance to run ComboFix?
  9. OK, the tutorial is not out of date (and should be completely valid). The person who was testing was running EAM on a server edition of Windows. If they want to participate in the referral program, then they should run EAM on a normal installation of Windows XP, Windows Vista, Windows 7, or Windows 8 with the latest Service Packs.
  10. The contents of both folders are somewhat different on all 64-bit editions of Windows. System32 will always contain more files than SysWOW64. Basically, what you are experiencing is an unfortunate side-effect of how 32-bit applications work on 64-bit editions of Windows. Hopefully, in the future, we will be able to offer versions of Online Armor that are compiled as 64-bit executables instead of 32-bit executables.
  11. The tutorial may be out of date. I'll verify if that is the case, and let you know. As for the guy who is having issues, he can contact me (or open a ticket in our Helpdesk) and we can help him set up a proper referral link.
  12. EAM Please download and install Fiddler 2 from this link (this is the version that requires the Microsoft .NET Framework 2.0), and then follow the instructions below: After installing Fiddler, please open it from the Start Menu. Launch Emsisoft Anti-Malware. Go to Configuration in the menu on the left. Select the Update Settings tab. Click on the Connection settings link in the lower-right corner. Check the box that says Use proxy server. Enter localhost in the Proxy server field, and then enter 8888 in the port field. Click 'OK'. Go back to the Menu on the left, and select Security Status. Click on the Update Now button to start the update (Fiddler must be running when you do this). After the update fails, go back to Fiddler, and to File, then Save, and select All Sessions (please save it on your desktop). Please send the Fiddler log to me in a Private Message (do not post it here).
  13. One of our moderators removed the log from your post and sent it to me in a private message. A quick look at the log shows that it can connect to the update server, but it receives a 504 error when attempting to download the first file, so I will send this information to our server admins and see if they need anything else. Since we are using a CDN (Content Delivery Network) now, we may need to know what IP address the EEK was being redirected to when connecting to the update servers. Scratch all of that for the moment. The proxy information in the log is a bit odd. Do you use a local proxy of some sort, or did you just use a non-standard port number for Fiddler?
  14. Unfortunately when one of our moderators saw your log attached to your post, they removed it and tried to send it to me in a private message, however the log didn't get attached to the message. If you still have the log, then please click on my screen name over to the left of where you're reading this, and send me a message. You can attach the log to the massage.
  15. When you right-click in the Programs list and select 'Add', and then navigate to C:\Windows\System32 Online Armor will show you the contents of C:\Windows\SysWOW64. See the screenshots below from my test environment (Windows 7 x64):
  16. Actually, I said that the documentation implies it, and not that quotes are required. Yes, I was incorrect. I would suggest following the documentation. Using spaces isn't documented, and we cannot guarantee that it will always work as you expect.
  17. Assuming you mean deleting and adding a rule in Online Armor, then no, it shouldn't cause any problems. Have you checked to see if it is showing you only the files/programs in C:\Windows\SysWOW64\drivers, and just saying they are in C:\Windows\System32\drivers?
  18. ¥akuza112, you're a tester, so if you need a license key then let me know.
  19. Looking at this documentation, the examples all have quotes around the paths, and it is specifically mentioned that "Multiple paths have to be delimited by commas". If a comma is being used as a delimiter then it is implied that paths with commas will have issues, and if the examples all show quotes around the paths then that implies that quotes should be used for all paths. Admittedly it isn't plainly stated that you should use quotes for paths, and so I did forward your request on to our management.
  20. When an item in the whitelist is checked, it is ignored by the scanner. I do not recall seeing that in any of the changelogs, so it should not have changed since the previous version. If you don't want a drive scanned, then do a Custom Scan and select which drives to scan. As for excluding a folder, anything in that folder would be excluded.
  21. I would believe that this is the way the command-prompt works, and is not due to a2cmd itself. There are a lot of paths that do not require quotes. Knowing which do and which do not is a matter of knowing the Windows command-prompt. That being said, I can pass on your request for these changes to the documentation, however please note that I cannot make any guarantees that they will be implemented.
  22. Try the copy that's in SysWOW64. I think that's what OA is seeing as being in System32, as that's how WoW64 works.