install manually downloaded Windows Updates
lengolad
28 Nov 2010
I have a very limited internet connection. I maintain numerous XP machines. For the past four or five years I have manually downloaded Windows Updates from the Windows Technical website and installed them manually on all my machines. It's a lot of work, especially when I reinstall XP on a machine... I've just learned about AutoPatcher and I'm excited! Is AutoPatcher able to apply the updates that I have already downloaded and keep in a folder (these are executable files from Microsoft, not AutoPatcher)? Can I somehow just point it to that folder and let it go to work? I don't want to have to download them all again (at significant cost... ). Thanks for any advice.
_def_x_
28 Nov 2010
Hi lengolad ...
If you are looking for a portable, reusable approach to updating multiple Windows XP SP3 machines AutoPatcher may be for you - I believe the three languages available are English, Italian, Portuguese (Brazil).
Chances are the updates might already be in an AutoPatcher release. The short answer is yes with a but 
- AutoPatcher communicates with the update (executable) via the .apm file, every update has one associated with it. The .apm file (module) contains information that drive the installation and recognition (post installation) of the update - call these 'dependencies'.
So, if you have an additional update not in a release it would need an .apm file and need to be located in the '\modules' folder, you would also need to add the info to the .apm file yourself. You could create a custom release that would function just fine but it will be Unofficial and state this on the main window in red letters - Unofficial/Unsupported Release - see unofficial.jpg.
Short answer is no but you may be able to build the release by consulting the script and paying close attention to the names and full paths to the updates. I would also have a look at an .apm file - both the script and apm file can be opened with notepad, they are text files really.
If I was you I would take a look at the latest XP SP3 English script - search the list for your updates by KB#, find a link to a .7z file that contains the .apm files and open them to get an idea of what is needed to make a release work - here is the .7z file that contains all the XP SP3 Critical APM files. You may be able to add the folder to the release and move your update to the folder but you will need to make sure the update is the same name, hash, and size otherwise the script will delete the update - you can fudge the name (renaming a file) but not the hash or size. I have built up a release this way, it is tedious but can be done. When you think you are close you will run APUP to see how you did. You may want to copy your updates to the folder so you will always have a backup.
This should get you started, btw, I attached an Official release pic with the Critical category expanded - notice all the detail available - you have 'categories' (Critical, Recommended, etc), an update 'title' along with a description, and the update detection - black (uninstalled), blue (installed), and so on.
Bottom line, it is really easy to build up a release this way, adding files you already have and letting APUP gather what you are missing - the tough part will be if you have updates not in the XP SP3 release.
Also, have a look at This Post!, this will help with downloading a release - you will need to get AutoPatcher and APUP setup first. In the link I have you select a release (XP SP3 English) as well, uncheck it if you want and download only the first two scripts, add XP SP3 when you are ready to go by running APUP again and selecting the release you want - make sure you are doing this on the same folder and location - change paths and you will need to start again from scratch.
Finally, you wont have a '\modules' folder until you select a release - the first two scripts will give you the files/folders that both APUP and AutoPatcher need but without a release (XP, Vista, .NET Framework) to load you get a dead window - give it a try it wont hurt
Quote
I maintain numerous XP machines
Quote
Is AutoPatcher able to apply the updates that I have already downloaded and keep in a folder (these are executable files from Microsoft, not AutoPatcher)
- AutoPatcher communicates with the update (executable) via the .apm file, every update has one associated with it. The .apm file (module) contains information that drive the installation and recognition (post installation) of the update - call these 'dependencies'. So, if you have an additional update not in a release it would need an .apm file and need to be located in the '\modules' folder, you would also need to add the info to the .apm file yourself. You could create a custom release that would function just fine but it will be Unofficial and state this on the main window in red letters - Unofficial/Unsupported Release - see unofficial.jpg.
Quote
Can I somehow just point it to that folder and let it go to work? I don't want to have to download them all again
If I was you I would take a look at the latest XP SP3 English script - search the list for your updates by KB#, find a link to a .7z file that contains the .apm files and open them to get an idea of what is needed to make a release work - here is the .7z file that contains all the XP SP3 Critical APM files. You may be able to add the folder to the release and move your update to the folder but you will need to make sure the update is the same name, hash, and size otherwise the script will delete the update - you can fudge the name (renaming a file) but not the hash or size. I have built up a release this way, it is tedious but can be done. When you think you are close you will run APUP to see how you did. You may want to copy your updates to the folder so you will always have a backup.
This should get you started, btw, I attached an Official release pic with the Critical category expanded - notice all the detail available - you have 'categories' (Critical, Recommended, etc), an update 'title' along with a description, and the update detection - black (uninstalled), blue (installed), and so on.
Bottom line, it is really easy to build up a release this way, adding files you already have and letting APUP gather what you are missing - the tough part will be if you have updates not in the XP SP3 release.
Also, have a look at This Post!, this will help with downloading a release - you will need to get AutoPatcher and APUP setup first. In the link I have you select a release (XP SP3 English) as well, uncheck it if you want and download only the first two scripts, add XP SP3 when you are ready to go by running APUP again and selecting the release you want - make sure you are doing this on the same folder and location - change paths and you will need to start again from scratch.
Finally, you wont have a '\modules' folder until you select a release - the first two scripts will give you the files/folders that both APUP and AutoPatcher need but without a release (XP, Vista, .NET Framework) to load you get a dead window - give it a try it wont hurt
_def_x_
28 Nov 2010
I thought it might help if I gave a short example of how the script works as it scans the release (\modules folder) detecting what is present, and moving on to download any missing files - this is very much simplified but does explain the process in brief.
You start APUP (apup.exe), it loads the releases.list file, you make your selection, click Next... a \temp_bin folder gets created in the root directory and the script along with other files get put in there temporarily - and the script begins... see Spoiler to follow along...
#Changelog/PreActions
The script scans the folder to locate and perform the command, in this case remove update KB2362765 altogether from the \NonCritical subdirectory - the .apm file and folder (this includes the update in the folder). Notice the .apm file is not in the same folder with the update - this is important - the .apm files go in the category subdirectory not in the folder with the update (look at the folder name, looks similiar to the .apm file with the added '_files' at the end).
all PreActions are performed and the script moves on...
#Module Downloads: Critical
All critical .apm files are verified. The script scans the \Critical subdirectory for .apm KB2345886, if it verifies (line 2) the script moves on. If there is an issue the script will have downloaded the critical .7z file and placed it in \temp_bin (line 3 & 4), if the size and hash pass (line 5 & 6) the failed or missing .apm file will get extracted to the \Critical subdirectory (line 7).
and the script moves on...
#Downloads: Critical updates
The same process of file verification takes place, using the name, size, and hash - if an issue arises, the script will attempt to download the file from the link (line 3). Sometimes we make mistakes and the script needs fixin' - just FYI!
This is where the script can help you build a release or reduce the number of updates needed.
Lets say you have update WindowsXP-KB2345886-x86-ENU.exe already, you verified the name, size, and hash using the script details, and you would like to add it to the release so the script can move on and download only missing files you don't have - all the info you need is in the script.
Looking at this section you can see the update goes in the \Critical subdirectory, in the folder named \WindowsXP-KB2345886-x86-ENU.apm_files - if you have the correct file, create a New Folder in \Critical, copy and paste the correct folder name (renaming 'New Folder') - this way you get it exact - then copy (don't move) the update to the correct folder.
Always run APUP (apup.exe) a second time to confirm all is well, if you have everything APUP will simply scan the folder and report 0 files to download (see apup.log), and give you the 'Finish' tab. I suggest copying your saved files to AutoPatcher so if something goes wrong you still have your originals - what you do with them after AutoPatcher shows an Official release is up to you.
Note: This is pretty straight forward but if you do this wrong you will create a case of perpetual Unofficial status - just pay attention and all should be fine.
Spoiler
What in the world is going on in the Spoiler...You start APUP (apup.exe), it loads the releases.list file, you make your selection, click Next... a \temp_bin folder gets created in the root directory and the script along with other files get put in there temporarily - and the script begins... see Spoiler to follow along...
#Changelog/PreActions
The script scans the folder to locate and perform the command, in this case remove update KB2362765 altogether from the \NonCritical subdirectory - the .apm file and folder (this includes the update in the folder). Notice the .apm file is not in the same folder with the update - this is important - the .apm files go in the category subdirectory not in the folder with the update (look at the folder name, looks similiar to the .apm file with the added '_files' at the end).
all PreActions are performed and the script moves on...
#Module Downloads: Critical
All critical .apm files are verified. The script scans the \Critical subdirectory for .apm KB2345886, if it verifies (line 2) the script moves on. If there is an issue the script will have downloaded the critical .7z file and placed it in \temp_bin (line 3 & 4), if the size and hash pass (line 5 & 6) the failed or missing .apm file will get extracted to the \Critical subdirectory (line 7).
and the script moves on...
#Downloads: Critical updates
The same process of file verification takes place, using the name, size, and hash - if an issue arises, the script will attempt to download the file from the link (line 3). Sometimes we make mistakes and the script needs fixin' - just FYI!
This is where the script can help you build a release or reduce the number of updates needed.
Lets say you have update WindowsXP-KB2345886-x86-ENU.exe already, you verified the name, size, and hash using the script details, and you would like to add it to the release so the script can move on and download only missing files you don't have - all the info you need is in the script.
Looking at this section you can see the update goes in the \Critical subdirectory, in the folder named \WindowsXP-KB2345886-x86-ENU.apm_files - if you have the correct file, create a New Folder in \Critical, copy and paste the correct folder name (renaming 'New Folder') - this way you get it exact - then copy (don't move) the update to the correct folder.
Always run APUP (apup.exe) a second time to confirm all is well, if you have everything APUP will simply scan the folder and report 0 files to download (see apup.log), and give you the 'Finish' tab. I suggest copying your saved files to AutoPatcher so if something goes wrong you still have your originals - what you do with them after AutoPatcher shows an Official release is up to you.
Note: This is pretty straight forward but if you do this wrong you will create a case of perpetual Unofficial status - just pay attention and all should be fine.
lengolad
28 Nov 2010
Wow, thanks for the detailed response gUiTaR_mIkE! It's a bit more involved than I had hoped... I was looking for a 'find updates here' check-box kind of thing. :-/ Oh well, I may just have to bite the bullet and go with the 'stock' options. Thanks again for your time,
Paul
Paul
_def_x_
28 Nov 2010
Quote
It's a bit more involved than I had hoped... I was looking for a 'find updates here' check-box kind of thing
If you can spare the download time and bandwidth (less than 300 MB) just download the apupxxx.zip file, extract the contents, and download XP SP3 - Its just that easy. Read Here! to get started
Again, I apologize, I should have assumed you were only asking and pointed you directly to the getting started post
