locked
Update Cycle takes too long RRS feed

  • Question

  • I am testing windows disk protection from windows steadystate and am running into the issue where it does not complete the update cycle in a timely manner.  Even without any updates pending it will take 9 - 10 hours to complete.  I do have a custom update script listed, however it is a placeholder and has no code within.  Is this causing my problem?

    Wednesday, August 1, 2007 4:55 PM

Answers

  •  

    Hi ToddHamlin,

     

    Depending on the updates being installed, the update process can sometimes take a long time. During the update process, the system downloads all the updates from the server, then SteadyState will modify the status of Windows Disk Protection (WDP) to save all the changes to the hard drive. Therefore, it will take a longer time than normal update.

     

    Regarding the update script, if you have the Custom Updates option enabled, you need to write the script by yourself (or copy from another place). SteadyState will abort any script that takes longer than 30 minutes.  If there is a problem when applying the script, you'll see an event in the event log (eventvwr.msc).

     

    Best Regards,

    Friday, August 3, 2007 6:02 AM