173 replies to this topic

[Whatacrock]

Thanks DesertJerry for the report, was starting to wonder if anyone downloaded the latest.
If anyone else has download and reports no problems, then will get ViroMan to sign the release and move it to main...

Will need click-click to comment on the DotNET Framwork as that his baby...

[click-click]

http://www.autopatch...dpost__p__19140

[DesertJerry]

Started #1 and #2 systems; both to XP Pro x64 w/SP2 and then AutoPatcher
Windows XP x64 & 2003 x64 > Critical Updates
#1 system no problems - all blue
#2 system security update *** (KB2799329) black with check mark
Windows XP x64 & 2003 x64 > Non Critical Updates
#1 system no problems - all blue
#2 system Update WMP11 (KB935552) and Update *** (KB2779562) black
Opted to install all three #2 items indcated above - finished and restarted #2's AutoPatcher - same items still listed in black - have no idea why system #1 shows these items blue and system #2 black
Microsoft Windows - Updated Components > .Net Framework 3.5 and family
#1 system only one item listed in black: .Net framework 3.0SP2 (KB958483)(previously mentioned)
#2 system no problems - all blue
Microsoft Windows - Updated Components > .Net Framework 4.0
#1 system no problems - all blue
#2 system major problems - not listed by AutoPatcher and I am unable to install it using the downloaded programs - keep getting error message: Blocking Issues: The setup cannot run in compatibility mode. For more information, see the Readme file. (Readme is/was useless - unable to find solution using online searches or Microosft forums.)

Not many testers, as mentioned in other places, so don't know if my results from two systems provide enough info to finalize - your choice.

Edited by DesertJerry, 19 February 2013 - 08:50 PM.

[Whatacrock]

Your results do count DesertJerry and I vote for the release to be signed and moved to the main list...

Edited by Whatacrock, 23 February 2013 - 03:38 AM.

[Whatacrock]

Windows XP x64 ENU is now on main

[ViroMan]

New XP x64 script up on test list. Since I don't have anyone to check it against for pre-release errors there may be something off.

[ViroMan]

WAC provided a new XP x64 script... its up on Test list. Not Signed.

[DesertJerry]

I'm going to have to play dumb here - you know I have XP Pro x64 on two systems - please explain "its up on the Test list" ? How is anyone supposed to know where this is - no indication when I run APUP - the closest I see is **Test Script** (DONT USE) 7 Feb 2013

[_def_x_]

 DesertJerry, on 12 April 2013 - 07:39 PM, said:

I'm going to have to play dumb here - you know I have XP Pro x64 on two systems - please explain "its up on the Test list" ? How is anyone supposed to know where this is - no indication when I run APUP - the closest I see is **Test Script** (DONT USE) 7 Feb 2013

XP SP2 x64 English, dated April 09, 2013, is right there on the same list. This comment is very strange, you act like you're just hearing about releases2 list for the first time, ie: the beta list, the test list, the other list.

[Whatacrock]

When stated that it is on the test list it is always releases2.list ... to iron out any problems before signing.

If you check the list of available releases you will notice that there are several with an April 9 date... these are the latest scripts !!!

thanks _def_x_ .. you beat me to it

[DesertJerry]

I saw all the items dated 09 April - as today is 12 April and the comments about the new script were made yesterday or today I expected to see the same date in APUP. I had mentioned in other postings about comments being made about updates but the dates in APUP were days or weeks behind the date of the comments. Yes, I'm aware of releases2 - I've used it for months. I would just prefer the dates of the comments and the listing in APUP coincided.

Edited by DesertJerry, 13 April 2013 - 02:20 AM.

[Whatacrock]

This issue has been thrown around a number of times. Depending on the release maintainer the date is usually for the Patch Tuesday of that particular month (which it is in my case).

It may or can a release maintainer several days to complete their work, so using the date of Patch Tuesday is a logical place to start.

Also in my case I have to pass over the updated material for them to upload onto the server as am still awaiting access to ftp server. Since it is either dkdk_it or ViroMan I send the material to it can a couple of days for them to upload.
Comments are posted once the new updated script releases are uploaded. A small suggestion may be in order then, posting to include the date for the latest script.

[DesertJerry]

Ran APUP and downloaded 09 April updates - both systems.
Booted into XP Pro x64 - both systems > AutoPatcher
#1 - Windows XP x64 & 2003 x64 - Critical Updates - one black item = (KB2813345); had AutoPatcher install > finished - stayed black, why - unknown.
Non- critical and Component Updates all ok.
Everything else = ok.
#2 - same item stayed black as above - other stuff ok

Opened the appropriate APM > checked:

[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB2813345
KeyName=Type
KeyValue=Update
[DetectionFile]
FilePath=windows:\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
FileName=KB2813345.cat
FileVersion=ANY

neither location had item indicated.

Edited by DesertJerry, 13 April 2013 - 03:38 AM.

[Whatacrock]

DesertJerry -- am currently looking in to the situation, this update is for RDC 6.0 and it may be that your version of this component is less than 6.1.

As a matter of interest could you please look in SysWOW64 directory for the following file: mstscax.dll

Please report the FileVersion and if possible the MD5 hash. Interested to check the differences. Will post the findings of the one in this system when time permits.

Edited by Whatacrock, 15 April 2013 - 07:07 AM.

[DesertJerry]

#1 system XP Pro x64 SysWOW64 > mstscax.dll = version 6.0.6001.22815 MD5 = 985392E2DECD9EF3DAAFF01AA2F946A3

[Whatacrock]

There is something strange here as your version of mstscax.dll = version 6.0.6001.22815 is later than the one the update installed, mine being 6.0.6001.18926.

The previous version of the dll before the update was 6.0.6001.18564, MD5=6F5E4ABF34A0F7B5751EFE53282B8F8D, I beg there is an explanation somewhere.

As a matter of interest, can you check your autopatcher Windows XP x64,Non Critical to see if you have Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP x64 Edition (KB925876) installed, if not then may be the reason for the update not installing.

Please report your findings.

Edited by Whatacrock, 15 April 2013 - 07:22 AM.

[click-click]

6.0.6001.18564 is from the GDR branch whereas 6.0.6001.22815 is from the QFE branch. Windows Update normally will only install the GDR branch of a fix. The QFE branch was most likely installed via another method.

GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.

Instead of having AP install KB2813345, I would try and execute the fix directly to see if there are any messages. AP tends to hide messages at times that may be of importance.

Edited by click-click, 15 April 2013 - 09:00 AM.

[DesertJerry]

Whatacrock, on 15 April 2013 - 05:36 AM, said:

As a matter of interest, can you check your autopatcher Windows XP x64,Non Critical to see if you have Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP x64 Edition (KB925876) installed, if not then may be the reason for the update not installing.
Please report your findings.

Item in question shows as blue so it must be installed.

[Whatacrock]

DesertJerry -- as per click-click's posting, try installing the update and report accurately the error if any generated, this may lead to correcting the problem.

My update was installed via Windows/Microsoft Update, from this created the apm for autopatcher.

[Whatacrock]

Have made a few small changes to the release...on releases2 dated April 16 2013.