169 replies to this topic

[DesertJerry]

ViroMan, on 01 January 2013 - 09:50 PM, said:

well... you didn't have to edit the ini... but ok. lol If your using the new 1.4.2 version of apup(which it sounds like you are) then just open options and put a 2 in the url. lol.

While it's true I may be running APUP 1.4.2 there is no way for me to tell; when APUP is started the line at the top says: AutoPatcher Updater - no version information included here - in fact I could find no version information for APUP anywhere - minor error on someone's part.

[ViroMan]

You are right, none of the versions of apup ever said what version were running except in the log. I will make them say the proper version.

[Whatacrock]

New updated script for Jan 2013 now on releases2 for testing..

Please turn off your sweeper before downloading as the scripts have not been signed yet !!!

As usual people please report any errors and will correct before it is moved to main list..

Edited by Whatacrock, 16 January 2013 - 01:12 AM.

[Whatacrock]

Anyone testing this or have tested it but no found any issues with it........

Edited by Whatacrock, 19 January 2013 - 11:56 AM.

[DesertJerry]

Whatacrock, on 18 January 2013 - 11:20 PM, said:

Anyone testing this or have tested it but no found any issues with it........

Will try to boot into XP Pro x64 later today - Later:

Booted to XP Pro x64

Windows XP x64 & 2003 x64 > *** - Critical Updates >
Check mark > Security Update *** (KB2721693)
Check Mark > Update *** (KB2798897)

Next > Finished > restarted AutoPatcher > both stayed black with check mark

Checking APMs.

(KB2721693) > UniqueID=KB2721693-enu-amd64

Registry Editor 64bit - did not find the following:

[DetectionRegistry]
RegistryPath=MsiExec.exe /I{2511745F-5778-45C5-A6BF-C5F0969F02C0}
KeyName=DisplayName
KeyValue=MSXML 6 Service Pack 2 (KB2721693)

Checked:

[DetectionFile]
FilePath=windows:\SysWOW64
FileName=msxml6.dll
FileVersion=6.20.2012.0
Found msxml6.dll with version: 6.20 2016.0 dated 08Nov12. (Higher version number - correct?)

(KB2798897) - UniqueID=KB2798897-x64-ENU.apm

Registry Editor 64 bit Checked:

[DetectionRegistry]
RegistryPath=HKLM\SOFTWARE\Wow6432Node\Microsoft\Active Setup\Installed Components\{C3C986D6-06B1-43BF-90DD-BE30756C00DE}
KeyName=Version
KeyValue=3,0,2195,0

Found:
KeyValue=1,0,2195.0 (Don't know if this is correct)

Edited by DesertJerry, 19 January 2013 - 10:13 PM.

[Whatacrock]

Thanks DesertJerry for the report --- KB2721693 <<<-- manually delete apm and exe as the batch file missed the deletion..

Double checked the rvkroots update (KB2798897-x64-ENU) and key value is what I have for the update

Edited by Whatacrock, 19 January 2013 - 11:18 PM.

[DesertJerry]

Deleted as mentioned; other, I'm not sure - how often is this updated?

[Whatacrock]

Previous update for rvkroots was back in September 2012 (KB2728973)

A suggestion if I may... Use Windows Update for your XP Pro x64 and see if the update is listed for you..
Allow WU to update system then check with AP afterwards

Edited by Whatacrock, 20 January 2013 - 06:14 AM.

[DesertJerry]

XP Pro x64

Microsoft Update listed (KB2798897) as High-Priority Update - installed same successfully.

AutoPatcher > Windows XP x64 & 2003 x64 - Critical Updates > Update for XP and Server 2003 (KB2728973) black with check mark > Next > Finished.

Restarted AutoPatcher > Windows XP x64 & 2003 x64 - Critical Updates > Update for XP and Server 2003 (KB2798897) black with check mark. WTF!! This is the same item I just installed from
Microsoft.

But, Update for XP and Server 2003 (KB2728973) now blue. Back to Microsoft.

Microsoft Update, again, lists same item as above.

Something is wrong somewhere.

[Whatacrock]

@DesertJerry -- can you read the apm for KB2798897 and using regedit locate the registry entry stated in the apm..
In the right panel check the Version and report what it is.

You previously posted your KeyValue=1,0,2195.0 and interested to see if it changed .... if so can redit the apm to correct..

Edited by Whatacrock, 22 January 2013 - 12:16 AM.

[Whatacrock]

Something that was pointed out to my today by ViroMan.....the update KB2798897 is common to all OS's except for Win 8 so will move this to Common Files....still interested in version number for the detection..

Will update both XP scripts to remove the update and move to Common....

[DesertJerry]

Booted to XP Pro x64 > Started AutoPatcher

check mark and black for KB2728973

Opened APM for KB2798897 > KeyValue=3,0,2195,0 read registry: KeyValue=3,0,2195,0 - so they match and item is blue in AutoPatcher

Next > Finished > Re-started AutoPatcher:

Now I have check mark and black for KB2798897 and blue for KB2728973.

Registry now shows KeyValue=1,0,2195,0 - the installation of KB2728973 changed the value for KB2798897!!! Why?

Selected Next > Finished > restarted AutoPatcher > still check mark and black for KB2798897 and KB2728973 blue.

Microsoft update started > custom > High-priority Update KB2798897 checked > installed.

Reviewed update history - KB2798897 installed three times in two days.

Re-started AutoPatcher > and KB2728973 black to check mark and black and KB2798897 again blue.

[ViroMan]

DesertJerry, on 22 January 2013 - 09:53 PM, said:

Registry now shows KeyValue=1,0,2195,0 - the installation of KB2728973 changed the value for KB2798897!!! Why?

I thought that was weird so I did some poking around and this is what I found in the KB2798897 article

Quote

This update replaces update 2728973.

SO, we should remove KB2728973.

[Whatacrock]

KB2728973 is on the deletes list for the batch and seems to have missed the removal...Please manually delete this apm and associated exe (rvkroots.exe)

[DesertJerry]

OK - items deleted - progress is being made.

[ViroMan]

Another sweet reason for sweepers existence.

[Whatacrock]

After quite a bit of research and sole searching have re-instated KB2798897 (rvkroots) in the Windows XP x64 script as well done the out of cycle update mentioned by DesertJerry ready for the February release of Patch Tuesday.

If there are no errors reported then can assume all is well for the release and will request to ViroMan to sign and move it to the main page...The same with Windows XP x86 as well.

[Whatacrock]

Win XP x64 has been updated and forwarded to ViroMan for him to upload to release2.list. -- will edit this post when release is ready for testing..





WINDOWS XP X64 is now on releases2

Usual deal report any problems

Edited by Whatacrock, 15 February 2013 - 02:44 AM.

[Whatacrock]

Any reports for this month or is the release all clear??

[DesertJerry]

XP Pro x64 w/SP2 > AutoPatcher
Everything looked good except for:
Microsoft Windows - Updated Components > .Net Framework 3.0 SP2:
black with no check - Microsoft .NET *** (KB958483)
Selected item and it installed - restarted AutoPatcher - still black. Have no idea why - superseded by another update?