Problems Downloading Updates

Discussion in 'NOD32 version 1 Forum' started by Anyone, Nov 1, 2002.

Thread Status:
Not open for further replies.
  1. Anyone
    Offline

    Anyone Guest

    G'Day All,

    I have a client that purchased NOD32 and installed with no probs.
    Now when she tries to update a message appears saying that TRANSFER FILE IS DAMAGED.

    I have since uninstalled NOD32 then reinstalled but the prob is still there.

    Is there a registry setting that I have to delete to fixo_Oo_Oo_O?

    Awaiting your answers and thanking you in advance.

    Regards

    Paul
  2. f_disk
    Offline

    f_disk Guest

    Paul,
    I'm not 100% sure, but it sounds like a corrupted download.
    When you uninstalled, after rebooting did you go into the programs directory and delete ESET? Maybe run a regcleaner too.............I'd do it in this order:

    Uninstall NOD32
    Reboot
    Del ESET from "c:\program files"
    Empty trash can
    Run regcleaner and delete all traces of ESET
    Reboot
    Reinstall NOD32
    Reboot
    Run update
  3. Paul Wilders
    Offline

    Paul Wilders Administrator

    In case f_disk's solution doesn't solve your problem )kudoos, f_disk!): drop us an email: support@wilders.org .

    regards.

    paul
  4. Anyone
    Offline

    Anyone Guest

    Will do this as soon as I get back from hols. If I still get the prob I'll get back to the forums.

    Paul
  5. Straight Shooter
    Offline

    Straight Shooter Guest

    Hello.

    Try the above suggestions first, but also, after you find the ESET
    folder in Program Files and delete it, you may also want to do a search for NOD32 in Windows, and being careful, then delete those. If you feel comfortable with the registry, do a search for Nod32 and ESET, be PARTICULARLY careful with anything you find ESET, because you may wind up deleting something that says "RESET". Delete those entries and see..If in doubt, don't delete!

    I use Registry First Aid.. It's very good and seems to find a lot of stuff others don't...
Thread Status:
Not open for further replies.