Jump to content

FredW

Members
  • Posts

    9
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by FredW

  1. My previous posting was about my experiences on Friday and Saturday afternoon.

    I had now NOD32 9.0.408 installed and everything seemed working.

    However Saturday evening some updates for NOD32 failed, busy server or something.

    Also my email program did not receive and could not send anymore.

    So I wondered about problems at my ISP.

    But my browsers (2) worked without problems.

    So I decided to sleep on it.

     

    This morning (Sunday) updates for NOD32 failed again (server something).

    Emails could not be received (server something)

    But my other antivirus (not real-time, on request only) updated without problems.

    My browsers also worked without problems, I could get at any website I wanted.

     

    I checked my images and found an image of six (6) weeks ago.

    That image is before installing the trial EIS 10.0.359 (NLD).

    I decided to restore the image of six weeks ago (restore takes less than 10 minutes)

    The programs I had installed during those six weeks, I had to install again (I keep track of what I install).

    As I use mostly portable programs, this task was do-able.

    (portable programs on a separate partition are not effected by restoring an image)

     

    After restart everything worked as should be.

    NOD32 updates automagically again, mails could be received and sent, browsers worked fine.

    I am now back at NOD32 9.0.386 and I have blocked application update (to 9.0.408).

    I decided to never again be a guinea pig by way of a trial license.

  2. I was a long-time user of Eset NOD32 (ENU) (license valid till 15-09-2017).

    But I got a trial license (6 months) from my ISP (NLD) for Eset Internet Suite.

    So I installed Eset Internet Security 10.0.359 (NLD) to look for advantages (if any) over NOD32.

    The trial was a success, I found out that for me EIS has no advantages over NOD32.

    I had a separate firewall and could check what was happening, while the firewall of EIS was totally mysterious, no information for me whatsoever to be found.

     

    YESTERDAY

    When I read about 9.0.408, I decided it was time for me to go back to NOD32, version 9.0.386 with an in-product update to 9.0.408.

    So I tried to uninstall EIS 10.0.359, but Eset refused me to do so.

    I had to provide a *.msi file from the installation of EIS 10.0.359.

    I had deleted the *.msi file from Windows, because it is a useless file, taking only space without having any function at all.

    So Eset decided for me, that I was NOT allowed to uninstall a Eset product.

     

    Once I had downloaded an Eset tool called EsetUninstaller.

    So I tried to look in the Knowledge base for a newer version, if any.

    However Eset told me I did not need EsetUninstaller because WindowsDefender was not better that Eset antivirus and I should not remove Eset.

    hxxp://support.eset.com/

    Does Eset think I am a toddler who cannot think for himself?

     

     

    --- today ---

    (when I repeated this today to check if what I am writing is correct, all of a sudden I get German answers to a question in Eset International, go figure ...)

    https://www.eset.com/int/

    I give up on this point, I wanted to reconstruct what I did yesterday, but the Eset website is not cooperating and AGAIN tries to prescribe what I have to do.

    --- end today ---

     

     

    Whatever, yesterday I succeeded somehow (no longer possible to reconstruct) in finding a newer version of the Eset Uninstaller.

    The Eset Uninstaller has to be used in safe mode and run as administrator.

    I did so twice and twice all traces of Eset were removed.

     

    After restart I tried to install NOD32 9.0.386 (ENU).

    All seemed well till I restarted my Windows desktop after installation.

    When I clicked on the Eset logo (right bottom in the taskbar) my computer froze, even the time stopped.

    OK, computer frozen, then restore from the image I made before starting the exercise.

    Same results all over again.

     

    However, the second time when the computer froze, I went away to make some tea and when I came back the computer was no longer frozen and I could continue (I thought).

    I wanted to activate and copied and pasted my Nod32 License key to the input field of the Activation screen.

    Enter, wait, wait, wait very long, … Activation failed, could not reach the activation server.

    I tried several times, no success, no protection.

    Yes, I had NO problems reaching other websites!

    In the end, after having spent some hours in vain, I restored again and continued with EIS 10.0.359 (NLD), so I did not have to waste the evening.

     

     

    TODAY

    Lets try again this afternoon, starting with creating an image.

    To solve the missing *.msi, I tried to install EIS 10.0.359 over 10.0.359.

    Unfortunately, again the *.msi file was missing.

     

    Repeat procedure of yesterday.

    Used EsetUninstaller to remove all traces of Eset.

    Installed Nod32 9.0.386, restart, computer froze, wait, wait, wait, ….

    Copy and paste License key, activate, … could not reach activation server …

    All websites available.

     

    And while I took some time in writing this story the not-activated Eset Nod32 9.0.386 did a computer scan without asking my permission, without announcing the scan, all of a sudden a scan was completed.

     

    As a final straw (wild guess) I restored an image of four (4) weeks ago, I have no idea why.

    And see … in C:\Windows\Installer there was a *msi file that * could * be the requested *.msi file to be able to uninstall EIS 10.0.359

    Of course the name was gibberish (I think five (5) alphanumeric characters), but nevertheless I copied this file to a safe location and renamed to the requested name.

     

    Restore to the image of today.

    Try uninstall EIS 10.0.359 using the – by accident – discovered *.msi file.

    Uninstall accepted.

    Install Nod32 9.0.386 and try to activate, activate worked immediately, no problems.

     

     

    LATER

    On my Linux laptop I could find the location of the Eset Uninstaller that the Eset Support on my Windows desktop refused to show.

    hxxp://support.eset.com/kb2289/#Win_7

     

    IF, if I had not – totally by accident – found the requested *.msi file in an old image, I would have been stuck in Eset refusing to activate 9.0.386 as long as EIS 10.0.359 was installed in my PC.

    What would have happened when the 6 month trial period had expired I do not know.

    Probably long before that I would have decided to reinstall Win7HP64SP1 completely to get rid of everything from ESET.

     

    Now I can continue with NOD32 9.0.408 and see how that behaves.

    I do not want to go to version 10 yet, I will wait for a more mature version.

     

     

    I will also consider the policy of Eset to put a *.msi install file of any product from Eset in several places on my C:\partition.

    It is amazing to put the same file on multiple places.

    It is amazing the have such a large file stored without any purpose.

    It is amazing that Eset requires me (without any warning or any explanation) to keep a useless file, taking only useless space.

    Of course I will take all this into consideration when my subscription (now over 10 years) for Eset products expires.

     

    I have added the latest log of Eset Uninstaller.

  3. Today all day Last successful update showed 2016-07-22  20:36:26, date/time from late yesterday.

    This is odd because I did not switch of my computer before this date/time, so it was not updated after a cold start.

     

    Today version updates 13848, 13849, 13850 without changes to Last successful update.

     

     

    V9.0.381 had a different issue with last update notifications and the problem in 9.0.386 is a consequence of fixing the bug from 9.0.381. We'll see what can be done about it but fixing both issues together will not be an easy task and it's likely that only v10 will have them fixed both.

     

     

    Imo these are statements made by marketing not by technicians!

     

    Long time ago I was a (Cobol) programmer and a good one.

    Fixing a bug is *never* an excuse for a new bug, proper testing should have prevented this!

    And please do not say that fixing two (2) bugs is not an easy task, that looks so silly.

     

    If fixing some (minor) bugs is a problem, then what is the quality of the programmers at Eset???

    (hire some autistic nerds, they are very good in solving problems.)

    If Eset does not want to spend efforts in correcting these bugs in version 9 than do say so.

     

    This is my last message in this thread.

    If marketing gives (lame) answers on behalf of programming I am done.

    It only makes me wonder how I can look at the quality of the products of Eset.

  4. An update ...

     

    The problem definitely still exists, but with the following addendum:

     

    1) If you completely shut down your computer, and then

    2) Reboot your computer from a cold state, and if

    3) Before logging on, ESET runs a background update, then

    4) the "update was last run" information on the home tab and update tab do show correct information.

     

    I can confirm this.

    I switch off my computer every night and switch on every morning.

     

    Yesterday Last successful update did nor change.

    Today the first update after switching on was recorded.

    Last successful update 2016-07-22  8:46:26 (version 13842)

     

     

    Later in the morning I switched off and in the afternoon I switched on.

    No updates were recorded anymore since first start this morning.

    Updates 13843, 13844, 13845 and 13846 passed without changes

    to Last Successful update.

    (all dates/times my time.)

     

    I will ignore Last Successful update (I can also look in Log files / Events).

    I will wait (have to wait) for version 10.

  5. This morning Last Successful update shows 2016-07-20  21:46:44.

    That is for database version 13834, so the time was updated yesterday.

     

    However Virus signature database version shows 13837 (20160721)

    And Log files / Events shows latest update (13837) was 2016-07-21  11:51:28

    (all dates/times are my time)

     

    So I still have a problem, only occasionally (?) update of the Last successful update?

     

     

     

    Hello Siljaline, yes we meet regularly in a newsgroup.

    Latest version announced by Eset in this forum is 375,

    I discovered the release of 381 and 386 via other channels.

    One may wonder why Eset does not say so?

  6. I can confirm the issue.

     

    Yesterday I upgraded from version 9.0.381.0 to 9.0.386.0  (Win7HP64SP1)

    Last successful update (Update) is shown as 2016-07-19 20:32:41  (my time)

    However that is for database version 13828.

     

    After that there were updates for database version 13830,13831 and 13832.

    (as I could see in Log files / Events with different date/time stamp)

    But the date/time stamp of the last successful update has not changed anymore.

     

    Also in Tools / Scheduler I can see that updates were done at a later date/time.

    (latest regular automatic update 2016-07-20  14:46:27 (my time) )

    This is a little bit confusing.

  7. Thank you, Marcos, for your answer.

     

    I use Win7HP64SP1.

    As a firewall I have PrivateFirewall installed.

    hxxp://www.privacyware.com/PF_support.html

     

    NOD32 and PrivateFirewall do not cooperate (very well), I have to switch off HIPS in NOD32 to enable the firewall to work, if I don't switch off HIPS my computer freezes.

    In version 8 switching off HIPS gave no problems, but in version 9 I get the permanent red screen.

    I refer to this topic:

    https://forum.eset.com/topic/6258-disabling-hips-alert-in-v9/

    and NOD32 is also not cooperating with another firewall (Agnitum FW).

     

    You state that HIPS is very important for NOD32, I accept that, but that means that the choice of a firewall is limited to … (I have no idea to which firewalls).

    Your statement that I can use any firewall I want does not compute, at least my firewall and another firewall will no longer work because NOD32 requires exclusive rights to HIPS.

     

    When I switched off HIPS in version 9 some other features were also (automagically?) switched off, but I could switch them (most of them?) back on.

     

    In version 8 / Email client protection / Email client integration, I can integrate three (3) email clients.

    I had chosen to select none, as they are not relevant to me, that gave no problems.

    When in version 9 I select none (same reason), I get a permanent error message, so I have to cheat and select one (anyone?) to avoid the permanent red screen.

    https://forum.eset.com/topic/6265-e-mail-protection-non-functional/

    Why do I have to cheat to avoid a permanent (in my opinion not justified) error message?

    (more like giving hearing aids to people who have no hearing problems, if I may say so)

     

    As I no longer have version 9 installed (see subject) I cannot reproduce the 3,4,5,? consecutive certificate messages I get in Opera 12.17 when I click on any of:

    https://www.avast.com/virus-update-history

    https://www.avira.com/en/support-vdf-history

    hxxp://www.virusradar.com/ (an Eset site with incomplete security certificates?)

    The following link could not be found in Opera 12.17 with NOD32 version 9 (Could not connect to remote server), but is again available in version 8:

    https://www.security.nl/ (Dutch security site)

    SSL scanning seems to do amazing things.

    ;-)

     

    I am patiently waiting for the next version 9.

  8. Three times I tried to upgrade from Eset NOD32 8.0.312 to 9.0.318.

    Three times after the first restart when I clicked in the icon in the taskbar for NOD32 my computer froze, even the time stopped.

     

    Some time after my last restore back to 8.0.312, I remembered that I had similar problems when upgrading from version 7 to version 8.

    Eset NOD32 and my firewall (PrivateFirewall) did not work together very well and in the end I had to turn of HIPS in NOD32 and everything worked fine.

     

    So I spent many hours examining various scenarios with NOD32 with and without HIPS and with several firewalls (uninstall, install, see what works (or not), restore, etc.)

    I ran trial with NOD32 versions 8.0.312, 8.0.319, 9.0.318

    I ran trial with firewalls from Comodo, ZoneAlarm, TinyWall and PrivateFirewall.

     

    I am now back to NOD32 version 8.0.312 and PrivateFirewall.

    I am not going to update to any higher version, unless:

    – Eset allows switching off HIPS without punishing the user by producing a permanent not-removable error message (home screen all red)

    – Eset allows NOT selecting a not-used, not-present and not-wanted email program (Microsoft only) for email protection without punishing the user with a not-removable and not-justified permanent error message.

    – Eset allows the use of a firewall of MY choice (PrivateFirewall) without forcing me to use a non-HIPS firewall.

    – Eset solves the strange (and very repetitive) messages appearing in my second browser (Opera 12.17) about not complete/incorrect security certificates for some security websites (Avast, Avira, Eset); I noticed these messages appearing for some days (it can happen that security certificates are not in order), but they disappeared, quite unexpectedly, when I went back from NOD32 9.x.xxx to NOD32 8.x.xxx

     

    Furthermore I used to download the offline-installer from:

    https://www.eset.com/us/download//home/detail/family/2?installer=offline

    But for some weeks that link had not been working for me anymore, a mystery why.

    After having NOD32 three (3) times downloaded and installed via the Eset Live installer,

    I discovered – almost by accident – that sites in North America are apparently no longer allowed for customers outside North America.

    I have to download the offline installer now from an International link:

    https://www.eset.com/int/download//home/detail/family/2?installer=offline

    One may speculate why Eset does so, I can think of no reason, I do not want to know, I find it plain silly.

     

    The outlook of NOD32 9.x.xxx is modernized (whatever that may be), but the functionality has suffered because of this, it is more complicated to do an advanced setup.

     

    Finally I expected that downgrading to 8.0.319 would solve my problems with 9.0.318, but I had a hunch and went further back to 8.0.312 (after the umpteenth restore) and now also my KeePass 2 is fully working again.

     

    I used to be a happy user of NOD32, I have been using it for many years, last year I have renewed my subscription (3 pack) for another three years..

    But now I am disappointed with developments at Eset with NOD32 9.0.318.

    I will stay some time with Eset and Nod32 and see how things develop.

    Meanwhile exploring NOD32 for Linux.

×
×
  • Create New...