20 replies to this topic

[reach293]

I just created this batch script since I have most of the XP SP2 updates downloaded and heres my batch script on how it looks like.
Can you please tell me on what part needs to be corrected in order for this to work?

When I run it, all it says is Installing Windows Updates.....And does nothing. Even under Windows Admin account.

Please help.

And by the way, can anyone please post a template on how to create a batch file for all the post XP SP2 patches and updates?
This batch does not contain the whole updates, only part of it since it is just an example for showing you all here.
Thx.

@echo off
echo Installing Windows XP Updates
cmd >updatelog.txt
WindowsXP-KB873339-x86-ENU.exe /passive /norestart /n
WindowsXP-KB925720-x86-ENU.exe /passive /norestart /n
WindowsXP-KB925902-x86-ENU.exe /passive /norestart /n
shutdown -r -t 30 -f

[reach293]

All I want to use this batch file for, is that I want to run it so I dont have to click each and every one of these patches after reinstalling Windows.

reach293, on Sep 28 2008, 07:25 AM, said:

I just created this batch script since I have most of the XP SP2 updates downloaded and heres my batch script on how it looks like.
Can you please tell me on what part needs to be corrected in order for this to work?

When I run it, all it says is Installing Windows Updates.....And does nothing. Even under Windows Admin account.

Please help.

And by the way, can anyone please post a template on how to create a batch file for all the post XP SP2 patches and updates?
This batch does not contain the whole updates, only part of it since it is just an example for showing you all here.
Thx.

@echo off
echo Installing Windows XP Updates
cmd >updatelog.txt
WindowsXP-KB873339-x86-ENU.exe /passive /norestart /n
WindowsXP-KB925720-x86-ENU.exe /passive /norestart /n
WindowsXP-KB925902-x86-ENU.exe /passive /norestart /n
shutdown -r -t 30 -f

Edited by reach293, 28 September 2008 - 06:37 AM.

[Cristiano]

try:
WindowsXP-KB873339-x86-ENU.exe /q /o /z
WindowsXP-KB925720-x86-ENU.exe /quiet /norestart /overwriteoem
WindowsXP-KB925902-x86-ENU.exe /quiet /norestart /overwriteoem

not all updates share the exact same silent install string, you know...

[]s

[reach293]

Cristiano, on Sep 28 2008, 01:22 PM, said:

try:
WindowsXP-KB873339-x86-ENU.exe /q /o /z
WindowsXP-KB925720-x86-ENU.exe /quiet /norestart /overwriteoem
WindowsXP-KB925902-x86-ENU.exe /quiet /norestart /overwriteoem

not all updates share the exact same silent install string, you know...

[]s

Nope...still the same thing happening

[Cristiano]

have you tried install any of those with just the install command line to make sure that isn't some sort of failure into your script? the install strings that i give to you was the ones that once we used for those modules. also, if the test machine already has the sp3, it may not work

[]s

[reach293]

Cristiano, on Sep 28 2008, 04:53 PM, said:

have you tried install any of those with just the install command line to make sure that isn't some sort of failure into your script? the install strings that i give to you was the ones that once we used for those modules. also, if the test machine already has the sp3, it may not work

[]s

Ok, I installed those already including all the updates previuosly from Autopatcher under SP2...And this machine only runs SP2.

Can you or someone please post a decent Template in order for me to use this batch?

[Cristiano]

well, the autopatcher one. if you choose any module, you just will have to change the proper things and it will work. i'm about to finish our new documentation about it, so, it will be online shortly. but first we need fix some things, like language issues

about and .bat file to that, i've tried that approach with win98. it may works, but there's an big issue that your script doesn't have: all updates need to be installed in proper order or some of them may not work

[]s

[reach293]

Cristiano, on Sep 28 2008, 06:26 PM, said:

well, the autopatcher one. if you choose any module, you just will have to change the proper things and it will work. i'm about to finish our new documentation about it, so, it will be online shortly. but first we need fix some things, like language issues

about and .bat file to that, i've tried that approach with win98. it may works, but there's an big issue that your script doesn't have: all updates need to be installed in proper order or some of them may not work

[]s

Ok, my IT guys at work use Autopatcher and its quite differently ran on our XP SP2 workstations. This is how they do it.

1 They send us an email with the Autopatcher.exe in it.
2 Then we would run it.
3. When ran, a command prompt will pop-up just like this below.
Not exactly, this is just a rough example.

D:\Docs and Settings > MS-037.exe

And it just automatically go through the upsates EXE files and then a window pops up that tell us the PC will reboot in 2 minutes.

I want to do the same.

Now, I have the XP SP2 with the SP2 updates in Modules folder all burned onto a CD-R. Can you please explain on how to add the updates from the Modules folder and then add it onto Notepad to create a batch file similar to what the IT guys at my work do?

Also, I have a collection on the "MS08-XXX.exe" files on a separate folder and CD which was not from the Autopatcher directory...
And would I add those EXE files to the batch script also?

Edited by reach293, 28 September 2008 - 06:15 PM.

[Cristiano]

> onto Notepad to create a batch file similar to what the IT guys at my work do?
all autopatcher modules (the .apm files) can be opened with notepad. basically, you only need do something like this:

[AutoPatcher 5.6 Module]

[General]
[AutoPatcher 5.6 Module]

[General]
Title=Security Update for Windows XP (KB938464)
Description=A security issue has been identified that could allow an attacker to remotely compromise a Windows-based system that uses GDI+ and gain control over it.
ModuleAuthor=James A.
WebPage=http://www.microsoft.com/technet/security/bulletin/MS08-052.mspx
ReleaseDate=20080908

[Behavior]
ParentID=WINDOWS_CRITICAL_PARENT
UniqueID=KB938464_XP_ENU_X86
Critical=True
AutoExpand=False
Depends=
TimeToInstall=45
TimeToRemove=45
RequiresReboot=True

[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB938464
KeyName=Type
KeyValue=Update

[DetectionFile]
FilePath=system:\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
FileName=KB938464.CAT
FileVersion=ANY
FileMD5=C6BA20FD2E7C500E155E7EDEE95E27F1

[OperatingSystem]
WindowsVersion=XP_SP2_X86,XP_SP3_X86
SystemLanguage=1033,2057

[SystemComponents]
InternetExplorer=ANY
WindowsMediaPlayer=ANY
DotNetFramework=ANY
WindowsInstaller=ANY
MSNMessenger=ANY

[OfficeComponents]
Word=ANY
Excel=ANY
PowerPoint=ANY
Outlook=ANY
Publisher=ANY
Visio=ANY
Project=ANY
OneNote=ANY
FrontPage=ANY
InfoPath=ANY
Access=ANY

[Installation]
"Module:\WindowsXP-KB938464-x86-ENU.exe" /quiet /norestart

[Removal]
"Module:\WindowsXP-KB938464-x86-ENU.exe" /quiet /norestart /uninstall

[Slipstream]
"Module:\WindowsXP-KB938464-x86-ENU.exe" /quiet /norestart /integrate:"share:"

this module file is KB938464_xp_x86_enu.apm, so, the update himself must be in a folder like this one: KB938464_xp_x86_enu.apm_folder

take a look that the folder and the kb has the same name, just the _folder at the end. UniqueID= must be really unique. there's the detection part, that you can take from a machine already running that update or extract the files from the update and take the md5 for the .cat file. also, there's the registry detection, that you also can take from a machine already running that update.

you may build as many modules that you wish. just don't forget that each update has an release date and that ReleaseDate= is the date that the kb was really released. if you set it wrong, you may find that one kb may need that an previews update must be installed first

[]s

[reach293]

Cristiano, on Sep 28 2008, 09:12 PM, said:

> onto Notepad to create a batch file similar to what the IT guys at my work do?
all autopatcher modules (the .apm files) can be opened with notepad. basically, you only need do something like this:

[AutoPatcher 5.6 Module]

[General]
[AutoPatcher 5.6 Module]

[General]
Title=Security Update for Windows XP (KB938464)
Description=A security issue has been identified that could allow an attacker to remotely compromise a Windows-based system that uses GDI+ and gain control over it.
ModuleAuthor=James A.
WebPage=http://www.microsoft.com/technet/security/bulletin/MS08-052.mspx
ReleaseDate=20080908

[Behavior]
ParentID=WINDOWS_CRITICAL_PARENT
UniqueID=KB938464_XP_ENU_X86
Critical=True
AutoExpand=False
Depends=
TimeToInstall=45
TimeToRemove=45
RequiresReboot=True

[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB938464
KeyName=Type
KeyValue=Update

[DetectionFile]
FilePath=system:\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
FileName=KB938464.CAT
FileVersion=ANY
FileMD5=C6BA20FD2E7C500E155E7EDEE95E27F1

[OperatingSystem]
WindowsVersion=XP_SP2_X86,XP_SP3_X86
SystemLanguage=1033,2057

[SystemComponents]
InternetExplorer=ANY
WindowsMediaPlayer=ANY
DotNetFramework=ANY
WindowsInstaller=ANY
MSNMessenger=ANY

[OfficeComponents]
Word=ANY
Excel=ANY
PowerPoint=ANY
Outlook=ANY
Publisher=ANY
Visio=ANY
Project=ANY
OneNote=ANY
FrontPage=ANY
InfoPath=ANY
Access=ANY

[Installation]
"Module:\WindowsXP-KB938464-x86-ENU.exe" /quiet /norestart

[Removal]
"Module:\WindowsXP-KB938464-x86-ENU.exe" /quiet /norestart /uninstall

[Slipstream]
"Module:\WindowsXP-KB938464-x86-ENU.exe" /quiet /norestart /integrate:"share:"

this module file is KB938464_xp_x86_enu.apm, so, the update himself must be in a folder like this one: KB938464_xp_x86_enu.apm_folder

take a look that the folder and the kb has the same name, just the _folder at the end. UniqueID= must be really unique. there's the detection part, that you can take from a machine already running that update or extract the files from the update and take the md5 for the .cat file. also, there's the registry detection, that you also can take from a machine already running that update.

you may build as many modules that you wish. just don't forget that each update has an release date and that ReleaseDate= is the date that the kb was really released. if you set it wrong, you may find that one kb may need that an previews update must be installed first

[]s

Ok, since I have the Modules folder and the rest of the Autopatcher XP SP2 components on a CD, can I just run the Autopacther.exe which wioild reinstall those updates?

[Cristiano]

> without reinstall those updates?
yes, because of that part of "detection". if properly done, you can have all updates in your home-made version of autopatcher that it will show the already installed updates in blue and the not installed in black. of course, you may run autopatcher with an option to never select already installed updates

[]s

[reach293]

Cristiano, on Sep 28 2008, 10:38 PM, said:

> without reinstall those updates?
yes, because of that part of "detection". if properly done, you can have all updates in your home-made version of autopatcher that it will show the already installed updates in blue and the not installed in black. of course, you may run autopatcher with an option to never select already installed updates

[]s

Yes....Thats what I meant...

Suppose I get a PC, or reinstall XP SP2, can I used the Autopatcher again to reinstall those updates?

I know APUP will not work because Autopatcher does not support XP SP2 anymore.

[reach293]

The APUP will NOT work since AP will NOT support further downloads of SP2 updates...

So my question is.

Can I run only the Autopatcher.exe only to install the upsates on a new PC?

[Cristiano]

> Autopatcher.exe only to install the upsates on a new PC
yes. apup is just a kind of downloader, so, his script doesn't have anymore any kind of sp2 updates. but you can do it by yourself, because autopatcher.exe doesn't care about it. but it can be very tricky, since a lot of updates us to superseed another ones

[]s

[reach293]

Cristiano, on Sep 29 2008, 11:27 AM, said:

> Autopatcher.exe only to install the upsates on a new PC
yes. apup is just a kind of downloader, so, his script doesn't have anymore any kind of sp2 updates. but you can do it by yourself, because autopatcher.exe doesn't care about it. but it can be very tricky, since a lot of updates us to superseed another ones

[]s

So just to confirm, can I run only the Autopatcher.exe only to install the updates if I reinstall Windows XP SP2?

Because anyway, I have all the updates contained in that MODULES folder.
So, when I click on Autopatcher.exe after reinstalling XP SP2, will it reinstall those updates again?

Edited by reach293, 29 September 2008 - 12:31 PM.

[Cristiano]

> can I run only the Autopatcher.exe only to install the updates if I reinstall Windows XP SP2?
yes, if you have the module folder from a previews version that still had the sp2 updates

> will it reinstall those updates again?
autopatcher.exe will select to install only the modules that aren't installed yet. so, if any module is already installed, it will skip the selection to the already installed module

[]s

[reach293]

Cristiano, on Sep 29 2008, 01:53 PM, said:

> can I run only the Autopatcher.exe only to install the updates if I reinstall Windows XP SP2?
yes, if you have the module folder from a previews version that still had the sp2 updates

> will it reinstall those updates again?
autopatcher.exe will select to install only the modules that aren't installed yet. so, if any module is already installed, it will skip the selection to the already installed module

[]s

Ok, for example:

When I do a reinstall of XP SP2 and run Autopatcher.exe, will Autopatcher let me choose or select every update for SP2?
Or, will it only show the installed updates from the previous install of XP?

This is very confusing...Please explain in detail.

[Cristiano]

> will Autopatcher let me choose or select every update for SP2?
yes. autopatcher doesn't care about module instalations. the only one thing that doesn't support sp2 anymore is the apup script, because there's too many updates for sp2 and a lot of them are already replaced. since sp3 is already even in automatic updates, there's no need to us keep those into our scripts, since sp2 updates will not fit anymore to a lot of people.

> Or, will it only show the installed updates from the previous install of XP?
it can show both. in the main autopatcher screen, you can see the module tree. in that tree, you can see modules in blue and other ones in black. you don't need select any of the modules that are in blue, because they are already installed. if your machine has been wiped out, removing any trace of an previews OS and you are installing an clean version of Windows, you probably will have none update already installed, so, you probably will see the entire module tree in black. but if you just are repairing an windows install, you probably will have the first scenario, where some modules are in blue and others in black, to allow you select just the ones that are missing.

please, keep in mind 2 things:
- autopatcher.exe can be installed in many machines that you wish and the module tree will be builded to the specific situation of the machine that is running autopatcher in that time;
- reinstall may mean that the machine had an previews OS that was damaged and you wipe it out, so, basically, you are installing it again, but reinstall also can mean that you are installing the OS all over again, without remove nothing that was in there.

[]s

[reach293]

Cristiano, on Sep 29 2008, 02:45 PM, said:

> will Autopatcher let me choose or select every update for SP2?
yes. autopatcher doesn't care about module instalations. the only one thing that doesn't support sp2 anymore is the apup script, because there's too many updates for sp2 and a lot of them are already replaced. since sp3 is already even in automatic updates, there's no need to us keep those into our scripts, since sp2 updates will not fit anymore to a lot of people.

> Or, will it only show the installed updates from the previous install of XP?
it can show both. in the main autopatcher screen, you can see the module tree. in that tree, you can see modules in blue and other ones in black. you don't need select any of the modules that are in blue, because they are already installed. if your machine has been wiped out, removing any trace of an previews OS and you are installing an clean version of Windows, you probably will have none update already installed, so, you probably will see the entire module tree in black. but if you just are repairing an windows install, you probably will have the first scenario, where some modules are in blue and others in black, to allow you select just the ones that are missing.

please, keep in mind 2 things:
- autopatcher.exe can be installed in many machines that you wish and the module tree will be builded to the specific situation of the machine that is running autopatcher in that time;
- reinstall may mean that the machine had an previews OS that was damaged and you wipe it out, so, basically, you are installing it again, but reinstall also can mean that you are installing the OS all over again, without remove nothing that was in there.

[]s

Now I understand....

So in other words...theres no need of a batch file then...if I can just install all the updates again using Autopatcher.exe if I were to "CLEAN" install the OS...Or, on a new PC with reinstalling XP..

But....of course...when new updates are released from Microsoft for SP2, then of course, Autopatcher will not install it because the APUP file does not support SP2 anymore..
So when the new ones come out...Then those have to be installed MANUALLY...And therefore, the modules folder ONLY contains the updates that I had installed before...

Correct me if Im wrong.

[Cristiano]

> when new updates are released from Microsoft for SP2, then of course, Autopatcher will not install it because the APUP file does not support SP2 anymore
autopatcher will not install just because those modules probably will not be there. but if you create those modules by yourself, they may be in there and autopatcher will not say nothing about "you need sp3". but it will show also "unofficial"

> Then those have to be installed MANUALLY
or you need download the sp3 version and let it in another folder or mix booth, forgetting that a lot of updates was superseeded and install all at once. it will do your version become unofficial

> the modules folder ONLY contains the updates that I had installed before
no. it contains all the modules that you have downloaded. you may not have selected all them to install someday and by doing this will not erase any module. so, all the already downloaded modules will be there, allowing you install those modules again or not

[]s