Frontpage
Forums
Tutorials
Members
Calendar
Subscription
Donate
Links
Contact 
Help
Hello,
it is required (or not) an exact sequence (ex. date or other) order to install all updates ?
Thank you, bye
Claudio
Page 1 of 1
Update install order
#1
- Group: Members
- Posts: 1
- Joined: 25-December 11
- OS:Windows 7 x86
-
Country:
Posted 03 January 2012 - 02:17 PM
Back to top
#2
- after Windows 7 GA still Vista lover :)
-
- Group: Patrons
- Posts: 4,976
- Joined: 28-August 05
- OS:Vista Ultimate x86
-
Country:
-
Posted 03 January 2012 - 03:28 PM
under Vista/7 the order is unimportant.
#3
- Group: Members
- Posts: 4
- Joined: 06-June 12
- OS:Windows 7 x64
-
Country:
Posted 07 June 2012 - 07:13 PM
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...
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...
This post has been edited by mclone: 07 June 2012 - 10:28 PM
Share this topic:
Page 1 of 1