AutoPatcher Forum

Problem corrected and on main list

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

Looks okay here for x86 XP/SP3 (English). I found this on the main list and not the test list.

I got someone to check it and then I signed and moved to main. Sorry didn't post about it. I moved a few things over to main after getting them checked out.

Minor change to XP script. Re-signed and on main.

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

Updated script for Win XP x86 is now on releases 2.
Script date 20 April 2013

The following apms for XPSP3 x86 are incorrect:

KB2481109 - Belongs to RDC 6.1 and should be suppressed from displaying if RDC 7.0 is installed. Also this fix is in the wrong section and should be in Critical. When suppressing use:
[SystemComponents]
ComponentFile=system:\lhmstscx.dll
KB2813347 - Belongs to RDC 7.0 and should be suppressed from displaying if RDC 6.1 is installed. There is base a cat file when you install RDC 7.0 which is KB969084.cat which can be used, but not KB2483614 which is superseded and does not exist and will suppress this fix for everyone. This is one disadvantage of using cat files for suppression since they may get superseded along the way.

KB2797052 - is superseded by KB2817183 (Vgx.dll 8.0.6001.23480) and should be removed.
Edited by click-click, 24 April 2013 - 11:38 AM.

KB2807986 also needs to be fixed. There is a tab character at the end of the ParentID which needs to be removed.

Module 'Security Update for Windows XP (KB2807986)' (unique id: 'WindowsXP-KB2807986-x86-ENU') reports 'WINDOWS_XP_X86_NON-CRITICAL_PARENT ' as its parent, but such module does not exist or is not loaded in the right order.

Edited by click-click, 24 April 2013 - 12:31 PM.

Noted the changes and have applied to apms, updated the script etc and sent to VM for uploading and re-signing

Viroman when are you planning on updating the XP SP3 x86 changes that WAC sent you?
Edited by click-click, 29 April 2013 - 10:06 AM.

They were already applied yesterday. I uploaded them ... noted the errors and he fixed them. Just now I uploaded the new changes for the errors.

Why did you put this back on the release2 list since it was already on the main release list? All this back and forth is getting annoying. You really can't test without a valid .rti
Edited by click-click, 29 April 2013 - 07:04 PM.

Any reason why TweakUI was removed from the XP Addons and not included as part of the Ms PowerToys?

click-click, on 29 April 2013 - 08:06 PM, said:

Started APUP and selected XP Pro update 29 April - AutoPatcher v5.7.36 shows TweakUI under Windows Admin - and not where it should be - under Windows Addons > Microsoft PowerToys for Windows XP. (Everyhting els looked ok.)
Edited by DesertJerry, 29 April 2013 - 08:33 PM.

I believe the Admin Tool package is no longer being maintained and I don't have it on my system.
Edited by click-click, 29 April 2013 - 10:44 PM.

Well the admin tool package was dropped and then picked back up as a side job, both by WAC. He says he will work on the admin tool package but, don't expect regular updates.

Booted systems #1 and #2 into XP Pro w/SP3 > started AutoPatcher v5.7.36. #1 has 29 April update, #2 does not.

#1 and #2 system - still get Application Error overflow in GlobalVariables.StrToInt at line 112 when Loading Progress Loading modules... vsto05se_enu.apm invoked > OK twice continues.

Both XP x86 Critical Updates have same item in black (as previously mentioned - not an issue.)

Windows Addons > #1 system has one submenu: Microsoft PowerToys for Windows XP. #2 system has the same submneu plus: TweakUI, Windows Desktop Search, and Network Monitor Parsers submenus. Also, #2 system includes the following separate items not listed on #1: Copy Profile Tool, ActiveSync 4.5, Microsoft Wndows User State Migration Tool (v3.0.1),

#1 system has Windows Admin with submenu of: Network Monitor and Parsers and listing that includes Copy Profile Tool, ActiveSync 4.5, Microsoft Windows User State Migration Tool (v3.0.1), and Tweak Me!

#2 system has Microsoft Windows Admin with two items: 7 ZIP and X-Setup.

So, given the above I must assume one of the scripts I have is out-of-date. Problem is, when I start APUP v1.4.14 and use releases2.list I can't really determine which of the Available Releases pertains - there is no listing for Windows Addons or Microsoft Windows Admin. There is Extras (which includes what?) and Admin Tools (which includes what?).

Might enhance things if the Release Name included more information and/or matched the name of the items listed in the List of available items when AutoPatcher is started.

DesertJerry, on 02 May 2013 - 09:17 PM, said:

What release is 'vsto05se_enu.apm' from, what exe file does it install? Is it a stray? If this is the redistributable package I don't see an apm with this name. Is the release Official?

DesertJerry, on 02 May 2013 - 09:17 PM, said:

It sure looks like you have some test scripts mixed with old scripts, hacked scripts - and you can't keep track what you download at this point. The parsers, monitors, usmt, and profile tools were (IIRC) moved from Extras. X-Setup was a tool talked about for a moment in the user submitted threads.

Is all this mess Official? What does Sweeper say when you run it with /test /verbose

The easiest way to determine the contents of a script prior to downloading it is to load the script in your browser, copying & pasting the link from the releases list. I save a 'copy' of any scripts I may have questions about later, I do this while they are still in \temp_bin (assuming I download the release), before closing APUP. Everything is spelled out in the script in case I forget later.

IMO, aside from a worthwhile admin package, most of this other crap should have stayed in Extras.

looking at these 2 apm files, I noticed this...

...vstor_redist_x86.apm

[DetectionRegistry]
RegistryPath=HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{A0FE0292-D3BE-3447-80F2-72E032A54875}
KeyName=DisplayVersion
KeyValue=10.0.40308

[OperatingSystem]
WindowsVersion=XP_X86,2K3_X86,VISTA_X86,SEVEN_86
SystemLanguage=ANY

...vstor_redist_x64.apm

[OperatingSystem]
WindowsVersion=XP_X64,2K3_X64,VISTA_64,SEVEN_X64
SystemLanguage=ANY