114 replies to this topic

[Whatacrock]

Errors have been corrected and the script amended and been uploaded to my dropbox.

As usual please report errors and will correct if needed.

[DesertJerry]

#1 XP Pro x64 w/SP2

Downloaded latest batch > AutoPatcher

Windows XP x64 - Critical Updates
KB924667 - black - no check mark (I thought this had been fixed earlier - the either/or situation)
KB2481109 - black - check mark - the 64 was missing, again.

Everything else listed in blue - same as my earlier.

I still would recommend:

windows_xp_x64.apm

be changed from:

[OperatingSystem]
WindowsVersion=ANY
SystemLanguage=ANY

to:

[OperatingSystem]
WindowsVersion=XP_X64
SystemLanguage=ANY

This change results in the XP Pro x64 listing not being shown unless the user is running XP Pro x64.

[ViroMan]

windows_xp_x64.apm, I can agree with that.

KB924667 doesn't even show up in a search when looking in the modules folder.
This command in the script is probably why: PreAction=del "autopatcher:\modules\Windows XP x64\Critical\KB924667-v2-x64-ENU.apm"
The file is in the zip then gets deleted by the script. The script only mentions the apm by delete commands not detection.
As far as I can tell this kb is only mentioned in one MS bulletin so it should still be a valid security update.

KB2481109 shows blue and fine to me.

[Whatacrock]

Windows_XP_x64.apm has been changed as suggested.

KB924667 script error corrected and is indeed a valid update, so reinstated in the script.

Typo error fixed on KB2481109

Files uploaded on my dropbox

Fire away and let me have it people!!

[DesertJerry]

Updates could be a bit slower for a while - Olympic watching is on my schedule

[DesertJerry]

DesertJerry, on 28 July 2012 - 09:19 PM, said:

Updates could be a bit slower for a while - Olympic watching is on my schedule

Olympic break - updated batch > AutoPatcher > #1 XP Pro x64 - all OK.

[Whatacrock]

OK its been a while between posts ,this is to inform of an update to the Windows XP x64 script to August 2012.
Anyone wishing to test, download the archive and extract the batch file to your apup folder.
This will use apup V1.



As usual please report any errors

Edited by Whatacrock, 15 August 2012 - 07:48 AM.

[DesertJerry]

Downloaded the August 7z file and ran the batch file. Had gone to Microsoft Updates yesterday. Booted to XP Pro x64 and ran AutoPatcher - all XP Pro x64 item same as previously reported - no unexpected black listed items. So, I would say things are doing just fine.

[ViroMan]

well if things are working just fine and there are no more errors... I will start signing the files... err.. tomorrow.

[ViroMan]

Put on the main list.... fixed a few file size errors... also there is a missing apm for KB924667. KB2655992 had an extra X64 in its parent ID

Edit: So I fixed the errors... someone give it a look over before I sign. Since I seem to be making quite a few mistakes as of late.

Edited by ViroMan, 16 August 2012 - 11:39 PM.

[Whatacrock]

Damn....how did those errors escape me.

Downloaded a fresh apup and went through to checkthe apms and found en error in KB924667-v2 apm:

reads as
[Removal]
"Module:windows:\$NtUninstallKB924667_WM11x64$\spuninst\spuninst.exe" /q /u /z

needs to be changed to
[Removal]
"Module:windows:\$NtUninstallKBKB924667-v2$\spuninst\spuninst.exe" /q /u /z

and here is the file detection section

[DetectionFile]
FilePath=windows:\SysWOW64
FileName=mfc42u.dll
FileVersion=6.06.8064.0
FileMD5=E1EAB83C1D1E1E18862C9364313D05BE

Have no idea why this apm was missing as my main apup and the backups that were used for checking all have it listed...thems the breaks I suppose.
The rest seems fine so will switch to Windows XP x64 shortly to test once again.

Have tested the release and the only one showing it needs to installed is KB924667-v2
My apm for this update in the spoiler

Spoiler

[General]
Title=Security Update for Windows XP x64 Edition (KB924667-v2)
Description=Vulnerability in Microsoft MFC Could Allow Remote Code Execution
Author=Microsoft
ModuleAuthor=Whatacrock
WebPage=http://technet.microsoft.com/en-us/security/Bulletin/MS07-012
ReleaseDate=20070611

[Behavior]
ParentID=WINDOWS_XP_X64_CRITICAL_PARENT
UniqueID=KB924667-v2-x64-ENU
Critical=False
Recommended=True
AutoExpand=
Depends=
TimeToInstall=30
TimeToRemove=30
RequiresReboot=True
ModuleFolder=Critical_files

[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB924667-v2
KeyName=Type
KeyValue=Update

[DetectionFile]
FilePath=windows:\SysWOW64
FileName=mfc42u.dll
FileVersion=6.06.8064.0
FileMD5=E1EAB83C1D1E1E18862C9364313D05BE

[OperatingSystem]
WindowsVersion=XP_SP2_X64,2K3_SP2_X64
SystemLanguage=ANY

[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:\WindowsServer2003.WindowsXP-KB924667-v2-x64-ENU.exe" /quiet /norestart

[Removal]
"Module:windows:\$NtUninstallKBKB924667-v2$\spuninst\spuninst.exe" /q /u /z

Edited by Whatacrock, 17 August 2012 - 02:56 AM.

[DesertJerry]

Checked KB924667-V2.apm here - nothing had to be chnaged. Go figure.

[ViroMan]

my bad on the removal string... I took an existing apm and edited it. derp.

edit:
Oh hey... just noticed one more thing.... Your detection string is
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB924667-v2

and the one Microsoft says to watch is
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB924667-v2

Which one actually exists?

Edited by ViroMan, 17 August 2012 - 09:30 PM.

[Whatacrock]

I have double check the detection in the registry and the one I get is
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB924667-v2

[ViroMan]

Latest script has been uploaded to server. Will sign in a min. Signed

Edited by ViroMan, 25 August 2012 - 06:31 AM.