AutoPatcher Forum

Hi,

As I had told in the last bug report that I will come up with a fix instead of problem. I have come up with a fix for KB961260 on Windows Vista x64 SP1. I had faced this issue earlier but ended up with installing manually and ignored this error. Now, again I had to run autopatcher on another x64 machine, so I thought to give it a try.

Problem: Update installed status is not detected properly and the update is not installed.

Fix for apm file "KB960715_vista_x64.apm":
1. Detection issue:
Incorrect Line: FileName=FileName=Package_for_KB961260~31bf3856ad364e35~amd64~~6.0.1.0.cat
Correct Line: FileName=FileName=Package_for_KB961260~31bf3856ad364e35~amd64~~6.0.1.3.cat
2. Installation issue:
Incorrect Line: "Module:\Windows6.0-KB961260-x64" /quiet /norestart
Correct Line: "Module:\Windows6.0-KB961260-x64.msu" /quiet /norestart

These are the only issues while updating using AutoPatcher on a fresh installed Vista Ultimate x64 SP1 machine. And no other issues have been observed.

More fixes coming soon...

Keep up the good work

Fan of AutoPatcher

TR20xx

good. an issue that i didn't

this issue shall be fixed now. please, run apup again and choose the vista x64 script again, in order to get the new module

and, by the way:
# 30/03/2009: ~KB958690 module (cristiano) (thanks tr20xx)
# 03/04/2009: ~KB961260 module (cristiano) (thanks tr20xx)

2 good reports. really thanks

(by the way, this one will show also unofficial, since i don't have the tools to sign modules right now)

[]s

Thanks for the appreciation.

But you people are doing a great job. And I really appreciate it. I know as this is free you may get low on resoure and rigorous testing is also not possible. So, all these issues doesn't matter much.

Keep up the good work

Fan of AutoPatcher

TR20xx

pal, my mistake. i've only saw one issue and you have pointed 2. reading again your post i've notice my mistake and i've fixed the other one pointed by you, like described in the log:
# 03/04/2009: ~KB961260 module; ~KB960715 module (cristiano) (thanks tr20xx)

really thanks an sorry for the trouble

> and rigorous testing is also not possible.
in deed. with this one, we have an BIG issue. none of us has an x64 system, meaning that we can't test the scrip in the field. i'm just updating this one from an x32 machine, guessing detections and command-lines. but right now, this is the only choice that we have in order to not let this script die alone. unfortunelly, until an proper release maintainer shows-up, this is the only choice that we have. at least, several measures to allow that in an more properly way are already in place for some releases and this one is one that is already ready for it

[]s and thanks again

and, by the way: those 2 issues wasn't my fault at all. the one that did those had vista_x64, but everybody do mistakes. good thing that everything can be fixed without pain

Sorry, my mistake confused u a lot.

Did I do a screw up my fix wasn't at all for KB960715 apm file I mistakenly named it. My fix was for KB961260 apm file only.

Sorry I got u double work.

> KB960715
no worries, everything can be fixed without pain. i've did the detection for this one again. i may check it later when i come home, but can you please take a look if the detection for this one is working?

thanks for your report

[]s