65 replies to this topic

[Pedro]

Bugs still standing with script 3.2

1) Still showing on Windows Update

Microsoft GDI+ Detection Tool (KB873374)
Update For Windows XP (KB938828)

2) Updates that never turn blue after install and reboot

Root Certificates Update (1st Aug 2007)
Cumulative Security Update for IE for Windows XP SP2 (KB939653)
European Union Expansion Font Update

New bugs: although Script 5.7 was downloaded correctly, the list still shows 5.6 which doesn't turn blue after install and reboot

[Erik Ramey]

Pedro, on Nov 26 2007, 04:28 PM, said:

Bugs still standing with script 3.2

1) Still showing on Windows Update

Microsoft GDI+ Detection Tool (KB873374)
Update For Windows XP (KB938828)

2) Updates that never turn blue after install and reboot

Root Certificates Update (1st Aug 2007)
Cumulative Security Update for IE for Windows XP SP2 (KB939653)
European Union Expansion Font Update

New bugs: although Script 5.7 was downloaded correctly, the list still shows 5.6 which doesn't turn blue after install and reboot

After talking to Renato, I'm going to be updating the script to fix the Root and the Cumulative Security update. I haven't heard any reports of the European Union Font update so I'll look into this a bit latter. No worries, they will be fixed

It sounds like you have an older version of AP that you are running APUP over (Script 5.6 showing). Could you run APUP and download everything from scratch?

[Pedro]

Thanks, Eric!
The whole 610Mb, are you crazy? Only when you make .net an option

[Cyrus]

Looking at bug #12 in the first post, could someone elaborate on this for me to test? I have quite a few x64 machines, and I don't have any trouble with apup when downloading the x64 release on 32 OR 64 bit versions of windows. If someone could post exactly what they do to get the error I will be more than happy to try to debug it.

[Renato]

^ If you have already the .NET 3.5 folder, just put it in the place that it's supposed to be and avoid downloading 197 MB.

[Rudy]

Cyrus, on Nov 28 2007, 11:18 AM, said:

Looking at bug #12 in the first post, could someone elaborate on this for me to test? I have quite a few x64 machines, and I don't have any trouble with apup when downloading the x64 release on 32 OR 64 bit versions of windows. If someone could post exactly what they do to get the error I will be more than happy to try to debug it.

I will test tonight - the runtime error (0) i got was with apup.exe (25 Nov), will test with the new apup.exe (27 nov), and latest script. I forgot to run that one with the /log option.

[Pedro]

I was trying to do a clean download as suggested by Erik. Of course I will put the .net 3.5 in place (thanks for the reminder Renato).
This is not really a bug but more of a request: why doesn't it start by downloading the Critical updates (instead of the Non-critical as it does now?

[Cyrus]

Pedro, on Nov 28 2007, 12:16 PM, said:

I was trying to do a clean download as suggested by Erik. Of course I will put the .net 3.5 in place (thanks for the reminder Renato).
This is not really a bug but more of a request: why doesn't it start by downloading the Critical updates (instead of the Non-critical as it does now?

That's because it adds the critical updates that do not exist on your machine to the download "stack" first, and then layers the recommended and component updates on after that. So then when it goes to actually download them, the non-critical updates are on the top of the stack. This could be "fixed" (it's not really a bug) by reversing the order of updates in the scripts or by reversing the order that apup downloads the stack in. My guess is that the first one would be more simple but the later more effective. As a user, you are unable to do it yourself.

[Rudy]

Cyrus, on Nov 28 2007, 11:18 AM, said:

Looking at bug #12 in the first post, could someone elaborate on this for me to test? I have quite a few x64 machines, and I don't have any trouble with apup when downloading the x64 release on 32 OR 64 bit versions of windows. If someone could post exactly what they do to get the error I will be more than happy to try to debug it.

I've tested with latest script beta 2.0 - only received a file failed verification

it looks like a hash mismatch with wmp11-windowsxp-x64-enu.exe

Starting detection routine for item wmp11-windowsxp-x64-enu.exe
Looking for file C:\Program Files\AutoPatcher\Windows64bit_2003\modules\Components\wmp11_xp_2k3_x64_enu.apm_files\wmp11-windowsxp-x64-enu.exe
MD5 Hashes do NOT match. Expecting 17913c4251ae6bfae97a6d76a060e8ab, but found 1269e4628cb3f8ab7b9cca3915b464ad!!!

[Cyrus]

Rudy, I already posted that in the x64 forum a little while ago, and there's also a checksum error with one of the .apm files, but that should be very simple for Renato to fix.

[Rudy]

Cyrus, on Nov 29 2007, 08:28 AM, said:

Rudy, I already posted that in the x64 forum a little while ago, and there's also a checksum error with one of the .apm files, but that should be very simple for Renato to fix.

Great minds think alike.

[PrEtoRiaN]

found a minor bug..
when running autopatcher it says..
blue items already installed to select the ones we want to install ou uninstall..
when we choose one to uninstall it adds to install
see pic..

[Cyrus]

Right click it and then click uninstall.

[Pedro]

Thank you for the previous answer Cyrus. I hope Antonis considers my suggestion of downloading the Critical updates first.

I had already asked the uninstall question (and it was already answered). I think this proves that the current method of right clicking to Uninstall is not intuitive. Couldn't it be changed to be a toggle option? i.e. if it is installed (blue) then selecting it means you want to uninstall.

I think this is the logic in most (if not all) windows installers and programs, so it makes sense to follow what people are used to...

[Cyrus]

I was just answering his question. Although I agree with you, you should post in the feature request form to propose that change.

[kahuana]

Erik Ramey, on Nov 27 2007, 12:31 AM, said:

After talking to Renato, I'm going to be updating the script to fix the Root and the Cumulative Security update. I haven't heard any reports of the European Union Font update so I'll look into this a bit latter. No worries, they will be fixed

It sounds like you have an older version of AP that you are running APUP over (Script 5.6 showing). Could you run APUP and download everything from scratch?

The MD5Sum for the detection file KB939653.cat in KB939653_xp_x86_enu.apm doesn't match for the patched file.
I have a successful patch of KB939653 received via Windows Update on October 30.

My KB939653.cat file details:
size: 24698 bytes
timestamp: August 22, 2007, 9:01:37 AM
MD5Sum: E6DADF2103810ACF0807E52940EEB754

My OS:
Windows XP Professional - English.

Edited by kahuana, 03 December 2007 - 08:25 PM.

[Erik Ramey]

kahuana, on Dec 3 2007, 12:24 PM, said:

The MD5Sum for the detection file KB939653.cat in KB939653_xp_x86_enu.apm doesn't match for the patched file.
I have a successful patch of KB939653 received via Windows Update on October 30.

My KB939653.cat file details:
size: 24698 bytes
timestamp: August 22, 2007, 9:01:37 AM
MD5Sum: E6DADF2103810ACF0807E52940EEB754

My OS:
Windows XP Professional - English.

Good to go. This one is now detecting like it should

[Pedro]

Yes! This one is fixed!
Now, the only update which refuses to show as installed is the Root Certificates.
When I run Autopatcher on my work PC (which is updated via Windows Update) it also shows Root Certificates as not installed although I know it is up to date.

[Pedro]

Root Certificates is fixed.

Still showing on Windows Update after installing all updates from script beta 3.4:

Microsoft GDI+ Detection Tool (KB873374)
Update For Windows XP (KB938828)

Great work. There are still some ocasional Run Time Error 0 but it seems to be going the good direction. Thank you!

[Rudy]

Pedro, on Dec 13 2007, 09:14 AM, said:

Root Certificates is fixed.

Still showing on Windows Update after installing all updates from script beta 3.4:

Microsoft GDI+ Detection Tool (KB873374)
Update For Windows XP (KB938828)

Great work. There are still some ocasional Run Time Error 0 but it seems to be going the good direction. Thank you!

the runtime error (0), is most of the time due to network timeout, file not found, but this will be fixed in newer releases of apup.exe. We just a couple of better error handling fixes, and then we should be flying.