Jump to content


XP/2003 x64 release was suspended now resumed


114 replies to this topic

#61 _def_x_

    audi 5k

  • Veterans
  • PipPipPipPipPipPip
  • 1,460 posts
  • Gender:Male

Posted 09 July 2012 - 11:33 AM

 Whatacrock, on 08 July 2012 - 12:23 PM, said:

The critical update still persists so requesting help with this one KB958469 requires as a prerequisite which is KB956744.

Not sure how to write apm for this.

ViroMan has the right idea, and if using a 'dependency' doesn't work you can try a 'prerequisite' - if I remember correctly.

KB956744 is needed first, and I believe it installs, ... file(s) v6.0.6000.21061

\\SysWOW64
...\wlhmstscx.dll
\\System32
...\lhmstscx.dll

and, ... KB958469, ... file(s) v5.2.3790.4524

\\SysWOW64
...\wmstscax.dll
\\System32
...\mstscax.dll


So, this may work with the apm requiring the 'prerequisite', ...

[SystemComponents]
InternetExplorer=ANY
WindowsMediaPlayer=ANY
DotNetFramework=ANY
WindowsInstaller=>3.1
MSNMessenger=ANY
ComponentFile=windows:\SysWOW64\wlhmstscx.dll
ComponentVersion=>6.0.6000.21061

Just a thought, confirm files, etc, will need a test - but should work as an alternative. This is how a 'prereq' is used when a file expects to have another file in place first. :) You can experiment with '=>' and some updates require a newer 'Windows Installer', probably not XP x64, but I figure 7 wants Windows Installer 4x - just FYI.

#62 _def_x_

    audi 5k

  • Veterans
  • PipPipPipPipPipPip
  • 1,460 posts
  • Gender:Male

Posted 09 July 2012 - 04:02 PM

I forgot to mention, it may be self evident, using 'dependency' will allow the update with the dependency to remain visible, using the 'prerequisite' will keep it hidden until the prerequisite is in place - in this case, KB958469 will remain hidden until KB956744 is successfully installed. There's good reason to use both scenarios, just need to determine when you want one over the other.

#63 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPipPipPip
  • 1,159 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted 09 July 2012 - 09:07 PM

Ohh we figgured out last night that KB958469 and KB956744 is the same update for different versions of the RDP client. One does not need the other.

ohh ya we caught those errors with the registry detection... thats where I said there were issues.

Edited by ViroMan, 09 July 2012 - 09:13 PM.


#64 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPipPipPip
  • 1,159 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted 11 July 2012 - 08:43 PM

no one wants to test again? aww...

#65 eohrnberger

    Newbie

  • Members
  • Pip
  • 3 posts

Posted 11 July 2012 - 10:15 PM

Hi! I have to admit that I'm new to AutoPatcher, but I can see where it is a valuable tool for bringing an XP machine to the latest and greatest patch level.

Been trying to get past thedreded "One or more files has failed verification. Please re-run AutoPatcher Updater. If this problem presists, please report to the forums at AutoPatcher.com" error.

First, I want to make sure that I'm doig it right.
  • When I get this error, I clck the 'OK' on the error message dialog
  • Then I click 'Finish' on the main window
  • Re-run Apup2.exe
  • Click 'Get List', and when that's finished
  • Click 'Download'.
Apup2.exe does the MD5 check against the already downloaded files, and comes back with the error essage.

Since the error dialog doesn't specify which file(s) failed the MD5 check, I've included an attachment of the screen grab of the files / patches that I've selected.

Granted, shouldn't be any 64 bit software in there, but I searched the board, and this is the only place where I found the error message text.

Attached Files



#66 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPipPipPip
  • 1,159 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted 11 July 2012 - 10:18 PM

for apup2 just look for the log file called Apup2_LOG.rtf in the directory you put apup2 in. That will give us the results of the error.

#67 eohrnberger

    Newbie

  • Members
  • Pip
  • 3 posts

Posted 12 July 2012 - 12:40 AM

OK. Cool. Didn't know that. Here's the lines in the log file which appear to be the issue. I plan on deleting these files and trying to re-download, see if that clears it.

Download Error: C:\apup\apup_exe.7z
File size does NOT match. Expecting 1224704, but found 1222470!!!

Download Error: C:\apup\officesp2007.rti
File size does NOT match. Expecting 2447, but found 676!!!

#68 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPipPipPip
  • 1,159 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted 12 July 2012 - 03:49 AM

huh... weird... apup errors?

the office error is fixable on the server side... it might have been moved. I will check.

Edit:
The office error should be fixed... looking into apup error. Apup error was just a typo in the expected file size... its corrected. You should have no more errors.

Edited by ViroMan, 12 July 2012 - 03:59 AM.


#69 DesertJerry

    AutoPatcher Elite

  • Members
  • PipPipPipPipPip
  • 982 posts
  • Gender:Male
  • Location:Victorville, California

Posted 14 July 2012 - 03:51 AM

XP Pro x64 w/SP2

Installed updates on patch Tuesday

Started APUP2 and downloaded WhatACrocks script 04Jul

Started AutoPatcher > Windows XP X64 - Critical Updates:
KB924667 black - not checked
Other items shown in black were checked and installation selected.

Started AutoPatcher;
KB982381 still black - checked APM for detection locations, found neither.
KB2481109 still black - checked APM for detection locations - difference was found:

[DetectionFile]
FilePath=windows:\SysWOW
FileName=mstscax.dll
FileVersion=6.0.6001.18564
changed to

[DetectionFile]
FilePath=windows:\SysWOW64
FileName=mstscax.dll
FileVersion=6.0.6001.22815

Restart AutoPatcher KB2481109 now blue.

Edited by DesertJerry, 14 July 2012 - 03:52 AM.


#70 Whatacrock

    Lord Of The Scripts: Return Of The Manager

  • Release Managers
  • PipPipPipPipPip
  • 725 posts
  • Gender:Male
  • Location:Somewhere near Hell !!!

Posted 15 July 2012 - 09:40 AM

DesertJerry... have looked into KB2481109 quiet deeply and have no idea why there is a discrepency with file version.
Manually downloaded a seperate copy from MS dumped to temp folder and extracted the files within the self executable..
Checked the version numbers on all .dll files and all state version 6.0.6001.18564.

Will leave as is for the moment till ViroMan gets back online after his moving but many thanks for your reporting.

Any chance of posting a log file so can check what other errors you system detected.

B

#71 eohrnberger

    Newbie

  • Members
  • Pip
  • 3 posts

Posted 15 July 2012 - 12:19 PM

All clear now. Successful download. Thanks!

#72 _def_x_

    audi 5k

  • Veterans
  • PipPipPipPipPipPip
  • 1,460 posts
  • Gender:Male

Posted 15 July 2012 - 03:47 PM

 Whatacrock, on 15 July 2012 - 09:40 AM, said:

DesertJerry... have looked into KB2481109 quiet deeply and have no idea why there is a discrepency with file version. Manually downloaded a seperate copy from MS dumped to temp folder and extracted the files within the self executable..
Checked the version numbers on all .dll files and all state version 6.0.6001.18564.

There's 2 branches,

... SP2GDR branch: ( 6.0.6001.18564 )
... \SysWOW64
mstscax.dll - SP2GDR - \wlhmstscx.dll
mstsc.exe - SP2GDR - \wlhmstsc.exe

... SP2QFE branch: ( 6.0.6001.22815 )
... \SysWOW64
mstscax.dll - SP2QFE - \wlhmstscx.dll
mstsc.exe - SP2QFE - \wlhmstsc.exe

#73 Whatacrock

    Lord Of The Scripts: Return Of The Manager

  • Release Managers
  • PipPipPipPipPip
  • 725 posts
  • Gender:Male
  • Location:Somewhere near Hell !!!

Posted 16 July 2012 - 01:50 AM

Thanks for that _def_x_ .. Posted Image
I did have that typed but on the wrong computer ...working on a laptop as well on my workdesk and got confused what machine was typing on.Posted Image Posted Image

#74 Whatacrock

    Lord Of The Scripts: Return Of The Manager

  • Release Managers
  • PipPipPipPipPip
  • 725 posts
  • Gender:Male
  • Location:Somewhere near Hell !!!

Posted 16 July 2012 - 06:51 AM

@_def_x_ my apologies... found the document on the laptop I was also working and found the info contained with in...You and DesertJerry are correct.. a simple fix to the apm...have done..not added into archived apms..will do tonight or tomorrow morning.

#75 _def_x_

    audi 5k

  • Veterans
  • PipPipPipPipPipPip
  • 1,460 posts
  • Gender:Male

Posted 16 July 2012 - 07:07 AM

 Whatacrock, on 16 July 2012 - 06:51 AM, said:

@_def_x_ my apologies...

No need for that, yours is a labor freely given, you do what you can do, sometimes something slips by, hopefully someone else catches it, that's all.

#76 Whatacrock

    Lord Of The Scripts: Return Of The Manager

  • Release Managers
  • PipPipPipPipPip
  • 725 posts
  • Gender:Male
  • Location:Somewhere near Hell !!!

Posted 18 July 2012 - 05:14 AM

Have been doing updates to my script to bring it to July updates.This update also fixes several apms which I have amended.

However one update has not been added as still working on the detections for so will be added once completed.,The update is KB2728973.Will post later today on this as am currently on different OS.

For those wanting to test this latest release point your apup here http://dl.dropbox.co.../releases2.list

This test script runs directly from my drop box not from autopatcher.com so people aren't confused.

Feedback is welcome also please report errors encountered.

Edited by Whatacrock, 18 July 2012 - 05:25 AM.


#77 Whatacrock

    Lord Of The Scripts: Return Of The Manager

  • Release Managers
  • PipPipPipPipPip
  • 725 posts
  • Gender:Male
  • Location:Somewhere near Hell !!!

Posted 18 July 2012 - 09:00 AM

The script has been updated and new apms added..

Please report any errors and your commnets

#78 Whatacrock

    Lord Of The Scripts: Return Of The Manager

  • Release Managers
  • PipPipPipPipPip
  • 725 posts
  • Gender:Male
  • Location:Somewhere near Hell !!!

Posted 19 July 2012 - 12:23 AM

For those wanting to run this test script , unzip this archive into you apup folder and run batch file to download.




#79 DesertJerry

    AutoPatcher Elite

  • Members
  • PipPipPipPipPip
  • 982 posts
  • Gender:Male
  • Location:Victorville, California

Posted 19 July 2012 - 10:09 PM

XP Pro x64 w/SP2

Downloaded Whatacrock_XPx64_July.7z and ran the batch file.

Started AutoPatcher > Windows XP x64 > Windows XP x64 - Critical Updates

KB924667 is black - no check

KB982381 is black - check mark: Cumulative Security Update for Internet Explorer for Windows XP x64 Edition - question here, all versions of Internet Explorer? I have IE 8 installed - description should mention version or all - whichever is applicable.

KB2481109 is black - check mark - see postings #69, 70, 72 - thought this was fixed

KB2699988 is black - check mark: problem is the check mark is shown in the IE7 version, I have IE8 installed and that one is shown blue.

Windows XP x64 - Non-Critical Updates

KB954430 is black - no check mark: Question here: Last patch Tuesday - did it not update MSXML 4.0 and 6.0 ? Also, my Add or Remove Programs shows MSXML 4.0 SP2 (KB954430), MSXML 4.0 SP3 (KB2721691), and MSXML 6 SP2 (KB2721693) as being installed.

Did not opt to install items mentioned pending WhatACrocks review

#80 Whatacrock

    Lord Of The Scripts: Return Of The Manager

  • Release Managers
  • PipPipPipPipPip
  • 725 posts
  • Gender:Male
  • Location:Somewhere near Hell !!!

Posted 19 July 2012 - 10:22 PM

Thanks for the report DesertJerry it looks as if my detections are wrong. Will investigate these further later this morning and will upload fixes when I have completed them.
Don't install any till I get fixed
Thanks





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users