NOD32 file is damaged

Discussion in 'NOD32 version 2 Forum' started by gregf, Nov 17, 2007.

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

    gregf Registered Member

    Joined:
    Nov 17, 2007
    Posts:
    4
    Hello to all:
    The weekly scheduled scan brought forth this message; Nod 32-error-The Nod 32.00 file is damaged. o_O The program is unable to perform a scan, with
    the error message being revealed even on independent scans. This message
    has not reared itself before. The program has been operating flawlessly(v2.7).
    Is there an unknown condition on the laptop that has crippled Nod32?
    The laptop is functioning normally, no issues. Perhaps an uninstall/reinstall is
    the answer?
    All advice is appreciated. Thank you.
     
  2. gregf

    gregf Registered Member

    Joined:
    Nov 17, 2007
    Posts:
    4
    Performed a reboot and in progress of a thorough scan. :D
    Functioning well. My apology for a premature post.
    Thank you.
     
  3. ASpace

    ASpace Guest

    Hello!

    Welcome to Wilders!

    Open the folder where ESET NOD32 is installed - by default it is %ProgramFiles%/ESET

    Manually delete all the files called :
    • nod32.000
    • nod32.002
    • nod32.003
    • nod32.004
    • nod32.005
    • nod32.006


    Then , open the folder %ProgramFiles%/ESET/updfiles
    and delete all files from inside this folder (only the files inside , not the folder itself)


    Open NOD32 Control Center -> Update and press Update now to perform immediate update .


    Hope this helps :thumb:



    P.S. Why don't you try Eset Antivirus v3 which has improved system of upd files protection
     
Thread Status:
Not open for further replies.