6 replies to this topic

[MacNala]

I have tried updating the "english/win_xp/autopatcher_xp_sp3_enu_20090624.script" which I understood had been updated to include KB938127.
APUP log shows

APUP Has Started

Operating System: English (1033) Windows XP Professional Service Pack 3
Current Locale: English - United Kingdom / Non-Unicode Default: English - United Kingdom
Starting APUP From: C:\Downloads\AutoPatcher
Date & Time: 26-Jun-2009 16:42 UTC Offset: 0

***Downloading/Processing Releases.list***

List file HTTP location: [url="http://www.autopatcher.com/releases.list"]http://www.autopatcher.com/releases.list[/url]

***Releases.list Processed: Waiting for User Input***

The Following Releases have been Picked:
english/win_xp/autopatcher_xp_sp3_enu_20090624.script

***Running Any Pre-Cleanup Routines***

Executing shell command: del "C:\Downloads\AutoPatcher\modules\Critical\KB954459_xp_sp3_x86_enu.apm"

Executing shell command: move /y 
"C:\Downloads\AutoPatcher\modules\Critical\MSXML6SP1_x86_files" 
"C:\Downloads\AutoPatcher\modules\Components\__msxml\MSXML6SP1_enu.apm_files"

Executing shell command: del "C:\Downloads\AutoPatcher\modules\Critical\KB955069_xp_x86_enu.apm"

Executing shell command: move /y 
"C:\Downloads\AutoPatcher\modules\Critical\MSXML3_ptb.apm_files" 
"C:\Downloads\AutoPatcher\modules\Components\__msxml\MSXML3_enu.apm_files"

Executing shell command: move /y 
"C:\Downloads\AutoPatcher\modules\Critical\KB954459_xp_sp3_x86_enu.apm_files" 
"C:\Downloads\AutoPatcher\modules\Components\__msxml\MSXML6SP1_x86_files"

Executing shell command: move /y 
"C:\Downloads\AutoPatcher\modules\Critical\KB955069_xp_x86_enu.apm_files" 
"C:\Downloads\AutoPatcher\modules\Components\__msxml\MSXML3_ptb.apm_files"

Executing shell command: move /y 
"C:\Downloads\AutoPatcher\modules\Components\__msxml\MSXML4SP3_enu.apm_files" 
"C:\Downloads\AutoPatcher\modules\Components\__msxml\msxml4_sp3_files"

Executing shell command: rmdir /S /Q "C:\Downloads\AutoPatcher\modules\Components\__msxml\MSXML4SP3_enu.apm_files"
Executing shell command: del "C:\Downloads\AutoPatcher\modules\Critical\KB890830_files\windows-kb890830-v2.10.exe"
Executing shell command: del "C:\Downloads\AutoPatcher\modules\Critical\KB960715_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "C:\Downloads\AutoPatcher\modules\Critical\KB960715_xp_x86_enu.apm_files"
Executing shell command: del "C:\Downloads\AutoPatcher\modules\Critical\KB958690_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "C:\Downloads\AutoPatcher\modules\Critical\KB958690_xp_x86_enu.apm_files"
Executing shell command: del "C:\Downloads\AutoPatcher\modules\Critical\KB963027_IE7_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "C:\Downloads\AutoPatcher\modules\Critical\KB963027_IE7_xp_x86_enu.apm_files"
Executing shell command: del "C:\Downloads\AutoPatcher\modules\Critical\KB963027_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "C:\Downloads\AutoPatcher\modules\Critical\KB963027_xp_x86_enu.apm_files"
Executing shell command: del "C:\Downloads\AutoPatcher\modules\NonCritical\KB969497_ie8_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "C:\Downloads\AutoPatcher\modules\NonCritical\KB969497_ie8_xp_x86_enu.apm_files"
Executing shell command: del "C:\Downloads\AutoPatcher\modules\Critical\RootCerts_0902.apm"
Executing shell command: del "C:\Downloads\AutoPatcher\modules\Critical\KB958215_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "C:\Downloads\AutoPatcher\modules\Critical\KB958215_xp_x86_enu.apm_files"
Executing shell command: del "C:\Downloads\AutoPatcher\modules\NonCritical\KB950478_xp_wmp11_x86.apm"
Executing shell command: rmdir /S /Q "C:\Downloads\AutoPatcher\modules\NonCritical\KB950478_xp_wmp11_x86.apm_files"
Executing shell command: del "C:\Downloads\AutoPatcher\modules\NonCritical\KB968220_ie8_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "C:\Downloads\AutoPatcher\modules\NonCritical\KB968220_ie8_xp_x86_enu.apm_files"
Executing shell command: del "C:\Downloads\AutoPatcher\modules\Critical\KB890830_files\windows-kb890830-v2.9.exe"
Executing shell command: del "C:\Downloads\AutoPatcher\modules\Critical\KB951698_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "C:\Downloads\AutoPatcher\modules\Critical\KB951698_xp_x86_enu.apm_files"
Executing shell command: del "C:\Downloads\AutoPatcher\modules\Critical\KB956841_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "C:\Downloads\AutoPatcher\modules\Critical\KB956841_xp_x86_enu.apm_files"
Executing shell command: del "C:\Downloads\AutoPatcher\modules\Critical\KB960714_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "C:\Downloads\AutoPatcher\modules\Critical\KB960714_xp_x86_enu.apm_files"
Executing shell command: del "C:\Downloads\AutoPatcher\modules\Critical\KB961260_ie7_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "C:\Downloads\AutoPatcher\modules\Critical\KB961260_xp_x86_enu.apm_files"
Executing shell command: del "C:\Downloads\AutoPatcher\modules\Critical\KB890830_files\windows-kb890830-v2.8.exe"

***Starting Detection Routine Phase***

***Downloading Releases***

Files to be Downloaded: 0

***Processing Cleanup Routines***

But it doesn't seem to be there.

[_def_x_]

Those are simply "PreActions" from the script...

Here is the download info from the script:

Item=IE7-WindowsXP-KB938127-v2-x86-ENU.exe
DetectFile=autopatcher:\modules\Critical\KB938127_IE7_xp_x86_enu.apm_files\IE7-WindowsXP-KB938127-v2-x86-ENU.exe

Have you checked "\modules\Critical\KB938127_IE7_xp_x86_enu.apm_files\" for the update, it's in my release? Your
log shows "Files to be Downloaded: 0" - you should already have it.

BTW, I had to move down a few lines from your log (I didn't remove any) so the codebox didn't scroll so far to the right. Also,
thanks for actually using "codebox", most ignore it and post a log file that scrolls way down the thread page.

[Cristiano]

for sure is in there. i've just removed those files and did an download test. the log is bellow:

APUP Has Started

Operating System: Brazil (1046) Windows XP Professional Service Pack 3
Current Locale: Portuguese - Brazil / Non-Unicode Default: Portuguese - Brazil
Starting APUP From: D:\autopatcher\xp enu
Date & Time: 26-jun-2009 13:32 UTC Offset: -3

***Downloading/Processing Releases.list***

List file HTTP location: [url="http://www.autopatcher.com/releases.list"]http://www.autopatcher.com/releases.list[/url]

***Releases.list Processed: Waiting for User Input***

The Following Releases have been Picked:
english/win_xp/autopatcher_xp_sp3_enu_20090624.script

***Running Any Pre-Cleanup Routines***

Executing shell command: del "D:\autopatcher\xp enu\modules\Critical\KB954459_xp_sp3_x86_enu.apm"
Executing shell command: move /y 
"D:\autopatcher\xp enu\modules\Critical\MSXML6SP1_x86_files" 
"D:\autopatcher\xp enu\modules\Components\__msxml\MSXML6SP1_enu.apm_files"
Executing shell command: del "D:\autopatcher\xp enu\modules\Critical\KB955069_xp_x86_enu.apm"
Executing shell command: move /y 
"D:\autopatcher\xp enu\modules\Critical\MSXML3_ptb.apm_files" 
"D:\autopatcher\xp enu\modules\Components\__msxml\MSXML3_enu.apm_files"
Executing shell command: move /y 
"D:\autopatcher\xp enu\modules\Critical\KB954459_xp_sp3_x86_enu.apm_files" 
"D:\autopatcher\xp enu\modules\Components\__msxml\MSXML6SP1_x86_files"
Executing shell command: move /y 
"D:\autopatcher\xp enu\modules\Critical\KB955069_xp_x86_enu.apm_files" 
"D:\autopatcher\xp enu\modules\Components\__msxml\MSXML3_ptb.apm_files"
Executing shell command: move /y 
"D:\autopatcher\xp enu\modules\Components\__msxml\MSXML4SP3_enu.apm_files" 
"D:\autopatcher\xp enu\modules\Components\__msxml\msxml4_sp3_files"
Executing shell command: rmdir /S /Q "D:\autopatcher\xp enu\modules\Components\__msxml\MSXML4SP3_enu.apm_files"
Executing shell command: del "D:\autopatcher\xp enu\modules\Critical\KB890830_files\windows-kb890830-v2.10.exe"
Executing shell command: del "D:\autopatcher\xp enu\modules\Critical\KB960715_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "D:\autopatcher\xp enu\modules\Critical\KB960715_xp_x86_enu.apm_files"
Executing shell command: del "D:\autopatcher\xp enu\modules\Critical\KB958690_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "D:\autopatcher\xp enu\modules\Critical\KB958690_xp_x86_enu.apm_files"
Executing shell command: del "D:\autopatcher\xp enu\modules\Critical\KB963027_IE7_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "D:\autopatcher\xp enu\modules\Critical\KB963027_IE7_xp_x86_enu.apm_files"
Executing shell command: del "D:\autopatcher\xp enu\modules\Critical\KB963027_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "D:\autopatcher\xp enu\modules\Critical\KB963027_xp_x86_enu.apm_files"
Executing shell command: del "D:\autopatcher\xp enu\modules\NonCritical\KB969497_ie8_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "D:\autopatcher\xp enu\modules\NonCritical\KB969497_ie8_xp_x86_enu.apm_files"
Executing shell command: del "D:\autopatcher\xp enu\modules\Critical\RootCerts_0902.apm"
Executing shell command: del "D:\autopatcher\xp enu\modules\Critical\KB958215_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "D:\autopatcher\xp enu\modules\Critical\KB958215_xp_x86_enu.apm_files"
Executing shell command: del "D:\autopatcher\xp enu\modules\NonCritical\KB950478_xp_wmp11_x86.apm"
Executing shell command: rmdir /S /Q "D:\autopatcher\xp enu\modules\NonCritical\KB950478_xp_wmp11_x86.apm_files"
Executing shell command: del "D:\autopatcher\xp enu\modules\NonCritical\KB968220_ie8_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "D:\autopatcher\xp enu\modules\NonCritical\KB968220_ie8_xp_x86_enu.apm_files"
Executing shell command: del "D:\autopatcher\xp enu\modules\Critical\KB890830_files\windows-kb890830-v2.9.exe"
Executing shell command: del "D:\autopatcher\xp enu\modules\Critical\KB951698_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "D:\autopatcher\xp enu\modules\Critical\KB951698_xp_x86_enu.apm_files"
Executing shell command: del "D:\autopatcher\xp enu\modules\Critical\KB956841_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "D:\autopatcher\xp enu\modules\Critical\KB956841_xp_x86_enu.apm_files"
Executing shell command: del "D:\autopatcher\xp enu\modules\Critical\KB960714_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "D:\autopatcher\xp enu\modules\Critical\KB960714_xp_x86_enu.apm_files"
Executing shell command: del "D:\autopatcher\xp enu\modules\Critical\KB961260_ie7_xp_x86_enu.apm"
Executing shell command: rmdir /S /Q "D:\autopatcher\xp enu\modules\Critical\KB961260_xp_x86_enu.apm_files"
Executing shell command: del "D:\autopatcher\xp enu\modules\Critical\KB890830_files\windows-kb890830-v2.8.exe"

***Starting Detection Routine Phase***

Missing file D:\autopatcher\xp enu\modules\Critical\KB938127_IE7_xp_x86_enu.apm
  Item AutoPatcher XP SP3 Critical APMs is missing. Adding its download to the queue.
  --Adding [url="http://www.autopatcher.com/releases/english/win_xp/windows_xp_sp3_enu_critical_20090624.7z--"]http://www.autopatcher.com/releases/englis...l_20090624.7z--[/url]

Missing file D:\autopatcher\xp enu\modules\Critical\KB938127_IE7_xp_x86_enu.apm_files\IE7-WindowsXP-KB938127-v2-x86-ENU.exe
  Item IE7-WindowsXP-KB938127-v2-x86-ENU.exe is missing. Adding its download to the queue.
  --Adding [url="http://download.microsoft.com/download/3/d/9/3d90cc6e-2158-4e2d-af30-ae3602d8b1e0/IE7-WindowsXP-KB938127-v2-x86-ENU.exe--"]http://download.microsoft.com/download/3/d...2-x86-ENU.exe--[/url]

***Downloading Releases***

Files to be Downloaded: 2

***Processing Cleanup Routines***

Extracting D:\autopatcher\xp enu\temp_bin\windows_xp_sp3_enu_critical.7z into D:\autopatcher\xp enu\modules\Critical

as is stated in the log, the files wasn't in there and it was downloaded, as expected, in here:


[]s

[MacNala]

Yes it is there and does not need to be downloaded - my bad.
Retrying Autopatcher with the same answer file that was used does not install KB938127.
I have just retried again after reading your response.
I have also tried to use the Autopatcher.exe /log command but no log file was generated.
It might help to understand why the patch is not installing when all the other IE7 patches do install.
How do you use the /log?

[_def_x_]

OK, let's try and understand the answer file first.

The answer file is designed to be used once on the same machine, or when you want to install the same set of updates on
multiple machines you create an answer file. Once the answer file has been selected and the updates have been installed
you no longer need to use the answer file - hopefully the updates now appear blue indicating they have been installed.

I like to use my answer file - "no.selections" so when I run AutoPatcher nothing is checked, this allows me to select the
updates I want to install. This is nice for me when setting up a new OS install, I have my methods and I don't like having
to keep checking and unchecking after I reboot so I load nothing ie; my "no.selections" answer file. I could also create
separate answer files for Critical, NonCritical, well, you get it, any set of updates I want to load, then install each set of
answer file updates, reboot, select another set of answer file updates an so on. The idea is to only need the set once,
after installation they should be blue aka installed.

About KB938127:
How do you know it is not installing, is it still black after supposedly installing it and after reboot? If you have it as part
of an answer file set, I believe even after install if you reload that same answer file it will again be checked. So, if you
are expecting KB938127 to be unchecked just because it was installed, the answer file is not that sophisticated, it will
simply have the same set of updates selected. That is why I said, for the "same" machine an answer file is only used
once.

If you know it's not installing using AutoPatcher and you can't find a KB938127.log file, have you tried to install the update
manually - by double-clicking the update? If that doesn't work, I would try Microsoft Update.

You can create a log file by adding /log to either "autopatcher.exe" or "apup.exe" and using "Run" from "Start" and navigate
to your AutoPatcher/APUP folder (for apup.exe you can also Dbl-Click the "Hit.This" file in the Autopatcher/APUP folder).

Go to "Start" - "Run" - browse and find autopatcher.exe highlight and click open - in the "Run" window add /log to the end
of autopatcher.exe -> autopatcher.exe /log - when ready click OK.

You should be able to find your update logs and the AutoPatcher log in the "\Windows" directory.

[MacNala]

Hi,

Many thanks for the explanation of the answer file and your method of using it.
I have adopted a similar method. I do not use an answer file but initially select the critical components and the optional ones I want for the updating process. I then repeat the run again without an answer file to find out what patches are needed to update the additonal components. This seems to work fine. I have a problem with the MSXML SP3 installation but I wil start another thread for that.
Thanks again for your help and forbearance with some of my stupid questions.

[_def_x_]

Good to hear you are making some ground, and stupid questions - no not at all, I hope others read the posts which is why
I tend to be long winded

About Stupidity...

Well, I'm not sure if it qualifies as stupid, but I admit I have done it (on more than one occasion) which is another reason
I now load a "no.selections" answer file just about every time. If you notice where your mouse is located after firing up
AutoPatcher, it is on the "Next" tab. Well, I thought I moved the mouse far enough onto "Exit" to close AutoPatcher and
instead was on "Next" just enough to click it - Which proceeds to install whatever is checked in AutoPatcher which was
not my plan. I run autopatcher.exe /no license which bypasses the license agreements and loads the release right
away.

I was hoping the developer of AutoPatcher and APUP might write some code that would add a "warning" or "confirmation"
of any selections made before the next step occurs but it likely wont ever see the light of day. With APUP and service pack
level scripts warnings are critical. The XP SP3 x86 script initially removed a couple hundred megs of updates, and now we
see the new Vista SP2 scripts doing some major house cleaning. It should be intuitive to people that a new service pack
level (you've update to SP2 and now run a SP2 level script) will remove lots of updates found in the new service pack but
a Reminder would still be nice.