Jump to content

Update install order


Recommended Posts


  • 5 months later...

Hi, I'm interested in maintaining my own ULZ file for a specific XP machine, and I am also concerned about the order of their addition since there are several patches which do not appear on Windows Update until others have been installed. I have thought up two main ways to handle this:

1. Keep WUD's existing folder output structure, but edit the ULZ to prepend each local filename with an incrementing number (so that they can easily be re-ordered in another utility, in this case nLite).

2. Manually track the updates that appear/are installed in each session, and create a ULZ list for each iteration, so set 1, set 2, etc., and then integrating updates from one iteration at a time.

Will these ideas work? Is there a better solution?

edit: After some further reading, I can probably answer my own question. it would appear that the order (for XP) MAY be important depending on the update, since obviously one can't install a service pack for .NET without first installing .NET. It appears nLite will integrate by the order the updates are shown, and that the column headers can be clicked to sort by that field. That's great because most of the hotfixes have an entry in the Date field, which should resolve most issues. Using the default WUD XP-SP3 list however, there are several updates which are not dated. I'mm have to see if those are the ones it's giving me errors on...

Edited by mclone
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...