9 replies to this topic

[bruto]

Progress bar would just skip a bit when it came to these and they would be black again next time I run AP.
Poked a bit around AP folder and found out that:

KB973540 - ran the file manually with suggested keys (/quiet, /norestart), it installed just fine, detection folder and file in windows/system/catroot appeared. Dunno why the hell AP couldn't do it

KB960859 - APM is in mdules/critical, while the patch itself is in modules/__MSIE_critical. Moved the .apm file, installed just fine, detection file appeared.

KB946691 - doesn't install because some required office component can't be found, but you only see the alert when run the patch without /quiet

[_def_x_]

...KB973540
Maybe the unique ID not matching the actual file location - not sure here?
UniqueID=KB973540_XP_x86_ENU /// KB973540_xp_wmp_x86_enu.apm_files

...KB960859
Confirmed - the executable and apm files are not in the same location.

...KB946691
This looks to be an Office 2007 update - not sure why it is in your XP release???
...KB946691 - More Info!

Followup:

When looking at the AutoPatcher log these errors confirm the above post.

Module 'L:\AP\XP.SP3\modules\Critical\KB960859_xp_x86_enu.apm' implicitly refers to its module folder as 'L:\AP\XP.SP3\modules\Critical\KB960859_xp_x86_enu.apm_files'. However, such folder does not exist!

Module 'L:\AP\XP.SP3\modules\Critical\__WMP_critical\KB973540_xp_x86_enu.apm' implicitly refers to its module folder as 'L:\AP\XP.SP3\modules\Critical\__WMP_critical\KB973540_xp_x86_enu.apm_files'. However, such folder does not exist!

But this also showed up...

Module 'Update for Windows Media Player 9 or 10 (KB895181)' (unique id: 'KB895181_WMP10_X86_ENU') reports 'WMP10_NONCRITICAL_PARENT' as its parent, but such module does not exist or is not loaded in the right order.

Edited by gUiTaR_mIkE, 21 August 2009 - 06:30 AM.

[bruto]

gUiTaR_mIkE, on 21 August 2009 - 04:33 AM, said:

...KB946691
This looks to be an Office 2007 update - not sure why it is in your XP release???
...KB946691 - More Info!

Because I have office 2007 installed and want updates for it too!

[_def_x_]

bruto said:

Because I have office 2007 installed and want updates for it too!

Well, I would say you are getting a little behind.

AutoPatcher for Office 2007 hasn't been touched it looks like since November 2008, SP1 for Office 2007 was released in December 2007,
this update you are having troubles with was released to fix an issue while trying to install SP1 for Office 2007.

What I would recommend is to update your Office 2007 to SP2 and then update your Office Suite with AutoPatcher for Office 2007 SP2,
which by the way will remove this update if present(from the AutoPatcher folder). SP2 for Office 2007 should bring you pretty well
up-to-date but read the info below to make sure you are ready for SP2...

...SP2 for MS Office 2007 Suite

Make sure you also read (from the link above) "KB953195", "KB968170", "KB968173"

[_def_x_]

I figured I would add this as a separate post so if need be you can move or delete it.

Service Pack 2 (English) for Office 2007

...KB953195 (SP2) - Details!

...SP2 (English) for Office 2007 - Direct Download

Size: 304293008 (304MB)

Note: The link so far has been resumable, the size is correct but it is too large for me to download so I have no md5hash.

[bruto]

thanks for the heads up!

[Cristiano]

> ...KB973540
> Maybe the unique ID not matching the actual file location - not sure here?
the unique id for each module can be anything. you can write in that field "spring" or even "strong winter" that it will work anyway, since those words stay unique in the collection

the reason for this one doesn't install is this:
autopatcher:\modules\Critical\__WMP_critical\KB973540_xp_x86_enu.apm
autopatcher:\modules\Critical\__WMP_critical\KB973540_xp_wmp_x86_enu.apm_files

the module folder isn't the same than the module name plus _files and, due that, it will not run. please run apup again that the first pre-action will do the trick without download anything, since this issue is related to wrong folders only

> KB895181
you are lacking this file. but it is included in the script. so please, check if you have that file. if the file is included, but not working, let us know. right now, my vms are down and i will have to find time to rebuild it. and time is an luxury that i don't have anymore

thanks for the reports and heads up

[]s

Edited by Cristiano, 21 August 2009 - 05:15 PM.

[_def_x_]

Followup:

...This PreAction counters the latest fix - creates and endless loop - needs removing.

# Cristiano: 2009-08-18
PreAction=rmdir /S /Q "autopatcher:\modules\Critical\__WMP_critical\KB973540_xp_x86_enu.apm_files"

#Cristiano: 2009-08-21
PreAction=ren autopatcher:\modules\Critical\__WMP_critical\KB973540_xp_wmp_x86_enu.apm_files KB973540_xp_x86_enu.apm_files

also, I already had __WMP10_noncritical.apm, file size and md5 match - not sure of the problem with KB895181. It looks like the
edit to the script fixed the issues with KB973540 and KB960859 - just edit out the PreAction listed and those 2 should be good.

[_def_x_]

Right in front of my face...

...KB895181_wmp_enu.apm_files
...KB895181_xp_wmp10_x86_enu.apm

[Cristiano]

well, for the endless loop, the problem is a little bit more complicated than it looks. lets see:
- without show the info in the log, you will have to find those commands into the script. it can be worst;
- by doing an shortcut to make it go straight to the right destination, an issue will be created. why? easy: all those that have run the script in that delay of time and didn't run the script again, may be lost in the middle of the way, because they could have run the script with the wrong move and, due this, their autopatcher would be unofficial forever. so, in order to have an script compatible to those guys, the old commands has to be in there as they was, even if they was wrong. by other hand, it creates an log longer than usual. but, as we are cleaning the script every 2-3 months, those moves will be deleted in 2-3 months. just as a sample, all the preactions from June will be removed next Patch day, making an considerable cleaning in the log.

as for KB895181, the issue shall be solved now, but not one had noticed that in almost 2 months. impressive

thanks

[]s