How to prevent update from forcing a reboot?

Discussion in 'NOD32 version 2 Forum' started by gpk, Jun 26, 2006.

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

    gpk Registered Member

    Joined:
    Jun 26, 2006
    Posts:
    3
    A friend of mine bought and installed NOD32 on my recommendation (tho I don't have it myself ;) ) and has just one problem. Usually the AV defs get updated quite happily, but a couple of times (presumably program updates?) the updater has forced a reboot of the PC, interrupting his work and causing data loss (because MS Word didn't shut down properly and Word's autosave feature doesn't handle tracked changes correctly).

    Is there any way of stopping NOD32 from rebooting the PC, at least without the user giving "permission"?

    Thx

    gpk
     
  2. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    Hi gpk, welcome to Wilders.

    Have your friend take a run through this thread, in particular post number 63 deals with offer of restarts after a component upgrade.

    Cheers :D
     
  3. ASpace

    ASpace Guest


    Yes , there is a way . Please ,see the screenshots which I am attaching .

    Then , let's see why does NOD32 update its components - I mean that if you friend has the latest version of the installer then there will be no need of component upgrade . I bet he/she is using a NOD32 CD which obviously has old version of NOD32. So , two options :

    1) See the screenshots and correct

    2) Reinstall the program in few minutes with the latest installer
     

    Attached Files:

  4. YeOldeStonecat

    YeOldeStonecat Registered Member

    Joined:
    Apr 25, 2005
    Posts:
    2,345
    Location:
    Along the Shorelines somewhere in New England
    Open up Control Center
    Click up "Update" to expand the update hive
    Over on the right side of CC once update is selected..click on the "Setup" button
    Click on the "Change" button in the "Type of Update" section

    Study the radio button choices there...you probably have that 3rd section set to "reboot in necessary"...can flip it to "offer computer restart.."
     
  5. YeOldeStonecat

    YeOldeStonecat Registered Member

    Joined:
    Apr 25, 2005
    Posts:
    2,345
    Location:
    Along the Shorelines somewhere in New England
    Whoops..triple post at same time...I lost the race going into the kitchen to refill my coffee mid-post. :p
     
  6. ASpace

    ASpace Guest

    part 2
     

    Attached Files:

  7. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    The wolves are hungry tonight... ;) :D
     
  8. YeOldeStonecat

    YeOldeStonecat Registered Member

    Joined:
    Apr 25, 2005
    Posts:
    2,345
    Location:
    Along the Shorelines somewhere in New England
    Breakfast for me! US EST! :D
     
  9. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    A reinstall is not necessary in this case unless your friend is finding NOD32 continually installing component upgrades and rebooting. Simply adjust your friends’ settings and he will be asked from here on in.

    Cheers :D
     
  10. gpk

    gpk Registered Member

    Joined:
    Jun 26, 2006
    Posts:
    3
    Wow thanks all, that was quick! I consider my question well and truly answered (and another post appeared while I was penning this reply!) :D

    This is probably the best product support I've ever received :cool:

    gpk
     
  11. gpk

    gpk Registered Member

    Joined:
    Jun 26, 2006
    Posts:
    3
    Hmm all a bit strange. The settings were as per default I think (Notify before upgrade, Offer restart if nec.) so quite why the reboot had occurred I don't know. I wonder if actually Word had crashed the computer or if the NOD settings weren't working properly. Anyway I changed it to Never reboot, so presumably that will prevent NOD from doing so and mean that NOD will just have to wait for reboot in those situations where one is required to implement the update.

    gpk
     
Thread Status:
Not open for further replies.