Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by carmik

  1. @Marcos good news and bad news: ran certfix yesterday via GPO on around 150 PCs. At the time went smoothly, all clients have started updating virus bases and messages about phishing not operational have disappeared from all. Status on ESMC console was either all-ok or yellow (due to ESMC agent being an older version for example, nothing serious). Today, I've received at least 3 calls from users whose systems I personally checked that were ok. In all 3 cases: * the phishing problem came up * along with a new one, pop/http scanners do not work So far it's 3 systems, not sure if this is a regression of some sort. WIll install 6.5.2132.5 as per: https://support.eset.com/en/alert7396-legacy-products-startup-issue
  2. Hoping that I've not deleted them yet, will do so in the evening. Ok to PM you a link to my MEGA share? Expected so, then perhaps try the following:
  3. Does the ESET uninstaller delete the c:\programdata\eset directory as well? If I were to enter safe mode, I'd do so to eradicate the actual cause of the problem, ie the files residing under c:\programdata\eset\eset security\IPM Perhaps the issue appears even on clean installations: upon execution of a license-expiring ESET app, c:\programdata\eset\eset security\IPM gets populated and causes the issue. In this case safe mode cleaning with the uninstaller won't help (since upon new installation the entire C:\programdata\eset directory will be re-created along with problematic IPM entries). Suggestion: with nod32 already installed and the issue existing, enter safe mode, only to delete those files residing under IPM. Is the issue resolved in that scenario?
  4. What I meant is that in order to get to advanced setup, you must be able to open the eset application window; if you have this issue, you simply can't!
  5. @itmanNot sure if that would work. In my case, I could not "hold" the eset window long enough to even open the settings... @Marcossetting this to "Solved", considering a solution has been found.
  6. That solved the problem in all 3 systems I had issues with.
  7. I've opened a ticket already, do you want me to pm you the ref number? For the record I re-posted some of the information you've asked because I was looking for them in Program Files, instead of ProgramFiles. Is it a problem if I do the safe-mode move on my daughter's system? I'd like to avoid shutting down my main rig... <offtopic>There is a problem with your ticket submission system, it does not accept mailboxes of the form mailname+alias@gmail.com. It treats the plus sign as an invalid character. This is incorrect handling as per the SMTP specification. Due to the bug right now, my browsing is very slow for some reason. Google "plus sign in mail", there's a Rutgers CS link that contains both informal explanations as well as the BNF of RFC822 (IIRC) which clearly shows + is a valid character, and widely used in Google to create pseudo-emails.</offtopic>
  8. There is an ECP directory, but it is empty. Can not tell, sorry There are 3 directories, 2, 3, and 5.
  9. @Marcos I think perhaps you should try to reproduce this in your lab, with a license close to expiration...
  10. Just checked my son's and my daughter's laptops, which have the same windows and the same nod32 and license: the same issue is exhibited!
  11. Yes, this is exactly what I've been encountering. @Marcos, since @NicoW stated that he corrected things by pushing back the date, could this be related to the issue encountered on Endpoint Security 6.5, some kind of regression? @NicoW can you also open a ticket and provide logs, as discussed above please, to accelerate a solution?
  12. I'm happy to say that the issue seems to be resolved on the PCs I've made a test run on. Furthermore, on Windows Server 2003 AD, it suffices to create a new gpo with a startup script the fix file itself, provided that the file is placed in files section of the gpo. It ran via group policy without issues on 3 systems, so I'm now deploying globally. Will let you know how that goes.
  13. @Marcosafter running this tool manually on a XP box (6.5.2132.1): 1) Endpoint Antivirus seemed fixed, but the fix window remained open for some reason. Is that expected behaviour? 2) Before applying the fix, I had the system removed from my ESMC console (VA, latest version). I expected that the system would reappear in lost and found, after applying the fix. It doesn't and I'm a bit clueless on what happened here. The system does respect the "use specific proxy to download ESET updates" policy, as I can watch from running netstat -a -p tcp. But it is invisible on the ESMC console (tried searching for it with system name and ip address). Has anyone else encountered something like that?
  14. There seems to be a problem, the exe does not exit. Not sure if it is safe for running it in a gpo, but will try it on a couple of systems...
  15. Will do. In the meantime, can you please address these questions?
  16. Is it batchable? I could put the exe on a network-accessible share and run it with a cmd script on the server, however can this exe run quietly? If so, what are the options?
  17. I lack the skills to do so mate. Plus, I'm not sure Windows server 2003 has powershell? Any help will be appreciated.
  18. Thank you for the fix, it's a good first step. However, I've got to replace 6.5.2118.4 on more than 1000 systems, so I (and I guess a lot of people here) would appreciate if you either provided a GPO-pushable MSI version of this file, or instructions for alternatively installing it via gpo (doable also on Windows Server 2003). The size of this task is huge, it is an impossible feat to accomplish manually unfortunately.
  19. I presume you are talking using the procedure as per hxxp://support.eset.com/kb3466/ Correct? Is there any issue running the English language log collector on my Greek-based installation? That is, would that be ok? Furthermore, I presume the collected log files will be used to open a ticket with you in https://www.eset.com/int/support/contact/ is that correct? As I've described this is a Windows 10 installation, build 1909. Has been as such for two months (it was 1809 or 1903 before, don't recall). EDIT: In that other thread, you asked for a video. Do you need one here as well?
  20. I've got a 5 system license that is going to expire in about 10 days. One of this licenses is installed as NOD32, on my Windows 10 Home (build 1909) rig. Had no issue, until this warning appeared. The problems appearing are the following: * (cosmetic) Every 10-30" the eset icon changes from a green E to a green E with an orange "!" warning (I think it is an exclamation mark). It stays as such for a couple of seconds, then goes back to normal "E" * (critical) trying to open the eset app, it opens but almost immediately (i) the eset icon is turned into "E" with an exclamation mark and (ii) the eset app window is closed The behaviour is similar to the one described in ... that is: The difference between my case and that other one is that in my case NOD32 does not complain about anything at all. It just does this thing with app window and the icon. I've tried repairing the installation first. It failed, so I made an uninstall and re-install. I did not use the eset cleaner but the settings are brand new. (Gawd what an awful quote mechanism!)
  21. What is the current ESET recommendation for Windows XP? 6.5 or 6.6? But before answering, please weight your response very carefully: if and only if 6.6 is as stable as 6.5 on XP, I could consider upgrading to the former, as a viable option.
  • Create New...