Unable to upgrade AV Home 3.x to 4.x

Discussion in 'ESET NOD32 Antivirus' started by chrizio, Dec 4, 2009.

Thread Status:
Not open for further replies.
  1. chrizio

    chrizio Guest

    My upgrade attempts on windows xp pro didn't succeed.
    All ESET kb articles regarding installation, reinstallation, uninstallation
    and clean-up procedures consulted and followed.

    Well, the installation process runs without any issue.
    But during the next OS reboot the problems start to exist.
    Windows boot screen (windows logo on black background) the system
    gets hanged up. Progress bar keeps to animate but hdd doesn't work.
    In this state the machine can stay for ages. Hard reset necessary.
    After that windows boot offers "last good". If this proposal
    not chosen the problem repeats.

    I noticed, that after having applied the ESET uninstaller/clean-up utility
    some NOD32 or ESET related entries are still present in registry.
    Primarily keys HKEY_LOCAL_MACHINE\SYSTEM\ControlSet0xx.

    Any idea about possible reason?
     
  2. WayneP

    WayneP Support Specialist

    Joined:
    Apr 9, 2009
    Posts:
    339
    Hello,

    The most common reason behind the symptoms you see are due to previous antivirus. Sometimes the conflict can show up when installing the latest version even though the previous versions had no problems at all. If you had any previous antivirus programs installed, I would recommend running the uninstall utility for that program. A list of common antivirus removal tools can be found in the Knowledgebase article below.

    http://kb.eset.com/esetkb/index?page=content&id=SOLN146
     
  3. chrizio

    chrizio Guest

    Once, a long time ago on this machine ran Ewido Anti-Maleware by Grisoft
    than (after ewido end-of life) AVG Antispyware.
    However I wonder, that times they ran pretty well in parallel with eset nod32.

    In registry some ewido and avg as remainders are still present.
    Do you think, these could cause my probs?

    I think I will be able to get some Cleaner for AVG-Software.
    But that with ewido could be slightly harder.
    Fortunately I have still the installer for old ewido software.
    Perhaps installing it and then uninstalling will clean up the system.
    Of course all while NOD32 temporarily removed from system.

    A long time ago some other anti maleware software was present on this system, like
    spybot
    malewarebytes anti-maleware
    eventually super anti-spyware
    Currently no more installed. Do you think their's remainders could cause this issue as well?
     
  4. WayneP

    WayneP Support Specialist

    Joined:
    Apr 9, 2009
    Posts:
    339
    You should check to make sure any drivers that may have been leftover by previous AV are removed. Device Manager hides these by default, but if you click on View and then Show hidden devices then a new section will appear called Non-Plug and Play Drivers.
     
  5. siljaline

    siljaline Former Poster

    Joined:
    Jun 29, 2003
    Posts:
    6,619
    If you have been manually editing your Registry this presents a huge problem and likely has nothing to do with ESET's product. Consider a fresh install.
     
  6. trjam

    trjam Registered Member

    Joined:
    Aug 18, 2006
    Posts:
    9,057
    Location:
    North Carolina
    I can manully clean my registry with never any issues. Go to regedit and hit control and F at the same time.Type in the name of old software you have used and hit enter. It will take you to old registry keys, you may be surprised. Just delete and hit control and F again till you finish. You may get to your Legacy files and just ignore as they wont delete. Then reinstall Eset again. Dont forget to clean out Eset also before installing again.
     
  7. trjam

    trjam Registered Member

    Joined:
    Aug 18, 2006
    Posts:
    9,057
    Location:
    North Carolina
    meant to say hold control then press F. I use to get the perverbial warning from Eset that F-Secure or Norton was detected. By doing this it cleared it up. For Norton you also have to go back and type Symantec.

    With F-Secure legacy files a folder pops up below the legacy file like 000 with entries of F-Secure on the right. If you right click on the 000 and delete it will say it cant but click ok and they will delete. I have messed up things before but never from manually cleaning my own registry. I prefer this method over using any registry cleaner I have seen. You may find your PC is more responsive to.
     
  8. siljaline

    siljaline Former Poster

    Joined:
    Jun 29, 2003
    Posts:
    6,619
    I would manually uninstall this way, but we all have our methods, though, this is preferred. :cool:
     
Thread Status:
Not open for further replies.