KB902322 Windows update trouble

Discussion in 'NOD32 version 2 Forum' started by Goldengamegod, Jul 11, 2005.

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

    Gizmo Registered Member

    Joined:
    Apr 23, 2003
    Posts:
    34
    Thank you for this post.
    I had trouble controlling automatic update service before.
     
  2. Tassie_Devils

    Tassie_Devils Global Moderator

    Joined:
    May 8, 2002
    Posts:
    2,514
    Location:
    State Queensland, Australia
    Yep, thanks for the advice. ;)

    Sure it will help many wonder what's happening.

    Cheers, TAS
     
  3. rjbsec

    rjbsec Registered Member

    Joined:
    May 15, 2005
    Posts:
    132
    Interesting - not just Norton's SymNRT.exe to look out for!
    I'm currently trialling NOD32 (14 days to go) and it's showing as version 2.19 or something similar - is it possible to update the trial version?
     
  4. Gizmo

    Gizmo Registered Member

    Joined:
    Apr 23, 2003
    Posts:
    34
    Eset, please why didn't you inform us about such problems(fixes) ?
    Changelog on you website is somehow old.
    Some of us may save some time solving things.
     
  5. NOD32 user

    NOD32 user Registered Member

    Joined:
    Jan 23, 2005
    Posts:
    1,766
    Location:
    Australia
    Basically if your NOD32 is up to date - 'version 2.50.23' or later according to the M$ page, you will not be affected by this issue. :)
     
    Last edited: Jul 13, 2005
  6. piktor

    piktor Registered Member

    Joined:
    Feb 4, 2005
    Posts:
    45
    Location:
    Germany
    Does this concern to 2.12.3 too?

    Then all users using languages, that are so far not updatet to 2.50.25 by Eset, having a big problem!

    -piktor-
     
  7. zashita

    zashita Registered Member

    Joined:
    May 17, 2005
    Posts:
    309
    I tried here with 2.12.3 french, and no problem ... till now :)
     
  8. rjbsec

    rjbsec Registered Member

    Joined:
    May 15, 2005
    Posts:
    132
    Anyone?
     
  9. SSK

    SSK Registered Member

    Joined:
    Nov 28, 2004
    Posts:
    976
    Location:
    Amsterdam
    Looking at the download page of www.eset.com, the trial version is shown as version 2.5. So I guess you could uninstall your trial version and install the new trial version?
     
  10. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Trial version 2.50.19 is exactly the same as 2.50.25 as it does not contain Configuration editor that was the only thing updated.
     
  11. CyberMew

    CyberMew Registered Member

    Joined:
    Apr 17, 2005
    Posts:
    128
    Thanks a lot for the information. No wonder I always get that error before 2.50.23 and not now(using latest now with no problems). I thought it was because I was using microsoft windows update beta version 6.
     
  12. VikingStorm

    VikingStorm Registered Member

    Joined:
    Jun 7, 2003
    Posts:
    387
    Windows Update 6 is also no longer in beta... (though I think it would auto-update to the final any how).
     
  13. anotherjack

    anotherjack Registered Member

    Joined:
    Jun 13, 2003
    Posts:
    224
    Location:
    Louisiana
    Does anyone know if this will also affect the WSUS update process? We're still at 2.12.2 as a corporate standard, but will be updating to 2.50.25 in the coming months.

    Jack
     
  14. Gizmo

    Gizmo Registered Member

    Joined:
    Apr 23, 2003
    Posts:
    34
    I experienced problems with WSUS on network using NOD32 v 2.50.16.
    Computers with this NOD version were not updating.
    Updating NOD to 2.50.25 solved the problem.
     
  15. mip

    mip Guest

    please applies KB894391.
     
  16. Holden4th

    Holden4th Registered Member

    Joined:
    Mar 27, 2005
    Posts:
    69
    How do I know which version of NOD32 I have?
     
  17. dog

    dog Guest

    Control Centre -> NOD32 System Tools -> Information ... then in the right panel scroll down to "Information about installed components"
     

    Attached Files:

  18. b+e

    b+e Registered Member

    Joined:
    Feb 22, 2005
    Posts:
    12
    There might be problems with MicrosoftUpdate V6 an the "old" versions of NOD32. You should avoid using/installing V6 and MSBA 2.0 until the newest version of NOD32 is available in your language.
     
  19. Samiko

    Samiko Registered Member

    Joined:
    Jul 20, 2005
    Posts:
    9
    Strange, since updateing to 2.50.25 i can not get it to work as it should, the Windowsupdate i mean.

    I have all the latest updates and when trying to update windows it just keeps loading and loading but nothing happens. I have had it running now for over 10 minutes and nothing happens.

    I've checked to see if Nod32 appeared in the Add or Remove programs and it did.

    I've been experiencing three problems since updating to the latest version, this one in this post and two others at this post https://www.wilderssecurity.com/showthread.php?t=89770

    Im very happy with Nod32 in general but these three issues gives me big problems.
     
  20. alglove

    alglove Registered Member

    Joined:
    Jan 17, 2005
    Posts:
    904
    Location:
    Houston, Texas, USA
    Do you have the same problem if you uninstall NOD32? I am wondering if it a problem with NOD32 or a problem with Windows Update itself.
     
  21. Samiko

    Samiko Registered Member

    Joined:
    Jul 20, 2005
    Posts:
    9
    I've uninstalled it now and it works perfectly (both my windows update and msn messenger 7.0 works fine when nod32 uninstalled).
     
  22. ronjor

    ronjor Global Moderator

    Joined:
    Jul 21, 2003
    Posts:
    57,728
    Location:
    Texas
  23. Samiko

    Samiko Registered Member

    Joined:
    Jul 20, 2005
    Posts:
    9
    Isn't that only for Windows XP 64 OS? Im not using the 64-bit Windows.
    If not i'll download it and try that one instead.
     
  24. ronjor

    ronjor Global Moderator

    Joined:
    Jul 21, 2003
    Posts:
    57,728
    Location:
    Texas
    Sorry. I was looking at the wrong info -- "an AMD 64 3500+".
     
Thread Status:
Not open for further replies.