8 replies to this topic

[dfdff3000]

apup proceeds without any errors, but when autopatcher is run it shows as Unofficial. As far as I know, it's been showing this way since the latest updates. My apologies for not posting sooner.

[Cristiano]

one issue was reported with this one. i don't remember right now the kb number, but it's easy to find. run autopatcher once, then look at windows folder for an file named autopatcher.log. in that file, will be reported an folder that may be wrong. issue: i was unable to contact domenico so far. but i will keep trying

[]s

[dfdff3000]

Per your instructions Cristiano, this was the error indicated in my most recent autopatcher log.

Spoiler

Module 'F:\Autopatcher\Windows7-32bit\modules\Critical\XXX-KB975561_seven_x86.apm' implicitly refers to its module folder as 'F:\Autopatcher\Windows7-32bit\modules\Critical\XXX-KB975561_seven_x86.apm_files'. However, such folder does not exist!

Many thanks to you and domenico.

Edited by dfdff3000, 24 June 2010 - 02:03 AM.

[Cristiano]

this is the issue that i was talking about. i still didn't downloaded the seven x86 script, but looking into the script himself, this update is commented, booth .apm file and the update, but there's not an removal for those in the script. as an guess, the script was signed without KB975561 and, due that, the removal of any references to KB975561 from the modules folder shall fix the issue until domenico track the issue related to this one.

[]s

[DesertJerry]

I just checked here, I only have this version: KB975561_xp_x86_enu.apm and the folder: KB975561_xp_enu_.apm_files

No similar file or folder with seven found.

[_def_x_]

My guess would be this module is causing the problem - XXX-KB975561_seven_x86.apm - I would delete it, see if this fixes the problem.

I don't know if AutoPatcher would add place holders in the log but the 'delete' command is for -> 'KB975561_seven_x86.apm' - not 'XXX-KB975561_seven_x86.apm', so this could be a stray file. DesertJerry has mentioned he has no instance of KB975561 in his 7 release so it looks to me this may be the issue.

[dfdff3000]

Deleting XXX-KB975561_seven_x86.apm did restore the folder to Official status. Many thanks gents.

I tried to do a little research, and while I saw there was no XXX-KB975561_seven_x86 .. there did seem to be a file available from Microsoft named MM26-KB975561.exe. It's an update from March that was rated important and is in regard to Windows Movie Maker and Microsoft Producer 2003. Not sure if that was replaced by any other update from Microsoft though - or whether it would even apply here.

[Cristiano]

i'm not sure as well. but domenico shall knows something

[]s

[_def_x_]

@dfdff3000

It does look as if Domenico is aware of MM26-KB975561.exe, it was added around March 9 and by March 30 he decided to 'comment' the update out of the script.

Spoiler

...the apm

#DetectFile=autopatcher:\modules\Critical\KB975561_seven_x86.apm
#DetectHash=

...the executable

#Item=MM26-KB975561.exe
#
#DetectFile=autopatcher:\modules\Critical\KB975561_seven_x86.apm_files\MM26-KB975561.exe
#DetectHash=56684aa2bfd91977d6cabdbb9aea2a8c
#DownloadFrom=http://download.microsoft.com/download/E/8/B/E8B5E621-0A9E-465A-BEB3-D91F81E236C7/MM26-KB975561.exe
#DownloadTo=autopatcher:\modules\Critical\KB975561_seven_x86.apm_files\MM26-KB975561.exe
#ExpectedSize=1556328
#ExpectedHash=56684aa2bfd91977d6cabdbb9aea2a8c

He's got something goin' on with this update