AutoPatcher Bug Reports

[+theblazingangel MVC]

AutoPatcher Bug Reports

Please report bugs with modules or AutoPatcher 5.1 itself here in this thread.

Make sure you've read the FAQ before posting!

Note this thread is not for reporting updates, thats what this thread is for!

Off topic posts will be moved or deleted from this thread.

Blaze,

AutoPatcher Team Member

www.autopatcher.com

New Layout by

raptor

Edited January 12, 2007 by theblazingangel

[supermouse]

division by 0: that happends randomly, with official or home made versions of ap, including 5.1.0.40. it happends after select updates, when you click at the begin button. it happends usually on machines that was already updated by some source, but it can happends too on a fresh instalation. memory of some of this machines was tested by memtest86+ (3 or more rounds) and it shows any clue. hd was tested too and nothing was found. after this sort of message, the user just need runs ap again and set his updates again and usually everything runs fine.

[acetken]

(Gathered from other thread)

- Remove non-working "Disable sticky keys" option. It does nothing since SP2.

- The security updates for .NET Framework 2 do not always install on the first run with APXP. I suspect this is because on clean systems without .NET Framework 2 already installed, they are run before .Net Framework 3 is installed.

If the ordering was changed to install .Net Framework 3 first then this issue might be resolved.

- The Euro Flags ScreenSaver is NEVER installed from within APXP

- The two ClearType tweaks NEVER seem to work and in fact remove ClearType if it's already applied. Is this tweak broken?

- KB891122 never seems to show as installed. I am not sure if this is a detection or an installation issue at this point.

- IE7 doesn't seem to install half the time, even on a verified legal Windows that can use the Microsoft update site with no problems and everything shut down.

- Still reboots midway through updating a machine that has been AP'd in the past.

* sunjava 6 entry removed, we dont want software updates reported here, thanks for the rest though! - theblazingangel *

Edited December 14, 2006 by theblazingangel

[the_guy]

KB891122 won't install with WMP11 installed.

that's why.

the_guy

[PsiMoon314]

KB891122 won't install with WMP11 installed.

that's why.

the_guy

Well that explains that then! :) Should KB891122 not install before WMP11 anyway? Unless the install ordering is stranger that I thought ...

I have also wondered if the Windows Media Connection 2.0 module should be installed with WMP11? I have not installed it as I would suspect this to be part of WMP11 anyway.

Kind Regards

Simon

[acetken]

(More from other thread)

first test with december version done. seems that can be removed:

KB911567

KB922760

for updates to .net 2, install it just after .net 3 doesn't work. at windows update, that updates for .net 2 are still there. but a restart maybe be needed in order to that updates work. anyway, if .net 2 is there, it can be done at once

KB918766 and KB920214 are also able to be removed. Replaced by MS06-076.

[+theblazingangel MVC]

note: no need to post things like "x replaces x" here, those belong in the release threads or the hotfix thread, bugs only ;)

(Gathered from other thread)

- Remove non-working "Disable sticky keys" option. It does nothing since SP2.

- The security updates for .NET Framework 2 do not always install on the first run with APXP. I suspect this is because on clean systems without .NET Framework 2 already installed, they are run before .Net Framework 3 is installed.

disable sticky keys: please vote on / discuss what to do with it here

.net 2 updates: i will alter the installation order!

- The two ClearType tweaks NEVER seem to work and in fact remove ClearType if it's already applied. Is this tweak broken?

i dont know what might be wrong with these two tweaks, they look fine to me...? if anyone can tell me i'll fix them, but otherwise theres nothing i think i can do...

- The Euro Flags ScreenSaver is NEVER installed from within APXP

found the problem but bad news! running the installer manually works fine, however when you run it silently a broken directX dependency check cancels the installation!i found that out by using the /qb switch rather than the qn switch! te module will be removed in the dec06 release!

[supermouse]

ClearType, if you are speaking of cleartype tunner and activate cleartype works pretty fine. i've duble checked that yesterday. also this part of autopatcher come from translation pack, i believe that english release must be fine too

[PsiMoon314]

Hi,

With reference to the ClearType Tweaks then if you actually use them once you have rebooted ClearType (and Font Smoothing) is completely disabled (unticked and greyed out).

In addition the Transition effect is also disabled or changed to something other than the settings you previously selected.

I have seen this issue dozens of times so I am sure it's not PC specific.

As a test Enable ClearType and the Fade Transition effect then use the APXP tweaks to enable ClearType on for the user and the default user (Welcome Screen).

Once you have rebooted I am sure you will see what I mean :)

Here are the settings which are in the Registry when everthing is configured correctly:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Control Panel\Desktop]
"FontSmoothing"="2"
"FontSmoothingOrientation"=dword:00000001
"FontSmoothingType"=dword:00000002

Kind Regards

Simon

[Marcin.Riki]

RMS_x86_enu.amc

you use in AutoPatcher ENG:

[install With Backups]

"Module:\WindowsRightsManagementServicesSP2-KB917275-Client-ENU-x86.exe" /quiet /norestart /overwriteoem

[install Without Backups]

"Module:\WindowsRightsManagementServicesSP2-KB917275-Client-ENU-x86.exe" /quiet /norestart /overwriteoem /nobackup

but RMS not install ......

i must unpack the file and use in Autopatcher Polish:

[install With Backups]

"Module:\msdrmclient.msi" /quiet /norestart

"Module:\rmclientbackcompat.msi" /quiet /norestart

[install Without Backups]

"Module:\msdrmclient.msi" /quiet /norestart /nobackup

"Module:\rmclientbackcompat.msi" /quiet /norestart /nobackup

[supermouse]

Marcin.Riki, yep. i've already notice that. mine is already builded (PT-BR) like that. but is missing webfolders update, and it will not be released unless it becomes complete and fully working

[PsiMoon314]

Hi,

From the APXP DeCc Thread the switches are reported to be:

The correct command line for KB917275 (WRM) should contain the switches "-override 1 /I /quiet". Perhaps another fix to come?

I have not tried this as yet.

Kind Regards

Simon

[dkdk_it]

RMS_x86_enu.amc

you use in AutoPatcher ENG:

but RMS not install ......

i must unpack the file and use in Autopatcher Polish:

Same problem for me... I have excluded it from this release... I hope to re-add in January.

[supermouse]

dkdk_it, this works. but you need unpack RMS:

[install With Backups]

"Module:\msdrmclient.msi" /quiet /norestart

"Module:\rmclientbackcompat.msi" /quiet /norestart

[install Without Backups]

"Module:\msdrmclient.msi" /quiet /norestart /nobackup

"Module:\rmclientbackcompat.msi" /quiet /norestart /nobackup

[allesok]

BUG REPORT?

I had AutoPatcher 2K Nov. 06 Full installed to "E:\Autopatcher\Autopatcher Nov 06" but the Dec update couldn't update that installation!

First it reported that it didn't find the Nov AutoPatcher. Then I chose my installation folder and continued anyway. But no new entries were found when I ran AutoPatcher...

I had to uninstall and reinstall to ...\Program Files\AutoPatcher 2K, and then I could update.

If you cannot update an installation done to another location of your own choice, this is a BUG that needs FIXING...

Or did I do something wrong?

[kilis]

I downloded AutoPatcher (Nov 06). Than patch (Dec 06). Than i run that. The AutoPatcher.exe dond work.

I try this

6) When i double click the AutoPatcher shortcut nothing happens

Go to: C:\Program Files\AutoPatcher\tools, run 'AutoPatcher Module Editor.exe' and close it - next run autopatcher.

If that doesn't help, copy comdlg32.ocx from the AutoPatcher \bin folder to c:\windows\system32 (overwrite existing file if there is one).

and it doesn't work too. Help me.

[Bruce A. Johnson]

I've installed Internet Explorer 7 on four computers. Two using AutoPatcher, and two downloading and installing via MS Update.

The two that I used AutoPatcher to install IE7 had major problems with IE7. It didn't work.

The two that I downloaded & installed IE7 via MS Update worked fine.

One of each were Dell computers, similar. The other two were other brands.

[PsiMoon314]

Hi,

It didn't work.

Care to elaborate?

Kind Regards

Simon

[Penn_Boy]

Installed IE7 from AP XP. Got the following message

"The requested lookup key was not found in any active activation context"

Any ideas?

Penn Boy

[Bruce A. Johnson]

Hi,

Care to elaborate?

Kind Regards

Simon

Regarding IE7 not working when installed using AutoPatcher. The two computers were very different.

In both cases, when I ran IE7, it still had the appearance of IE6.

Computer 1: If I tried to access any website other than the "homepage", I got an error: "The requested lookup key was not found in any active activation context."

Computer 2: The "homepage" would load, and links from it would work, but when I tried to go to any other webpage, either using Favorites, or direct address entry, the mouse pointer would momentarily turn to an hourglass, then nothing would happen.

In both cases when I installed AutoPatcher, and when I tested IE7 later, I shutdown all anti-virus, anti-spyware, and firewall software, including Windows Firewall.

Update on Computer 2: I'm still working on it. I just reinstalled Win XP, and did NOT use AutoPatcher on it, instead, downloading all updates from MS Update, including IE7, and IE7 is working perfectly.

[Bruce A. Johnson]

Hi Bruce,

...<snip...

Did you also install or upgrade the .Net Framework at the same time (the same APXP session) you did the IE7 install via AutoPatcher?

In every case, either .NET Framework was already up-to-date before installing IE7 with AutoPatcher, or AutoPatcher was used to update .NET Framework during the same session as the IE7 install.

More information about the one computer where IE7 didn't work when installed with AutoPatcher, but did when installed via MS Updates:

Due to another problem (which has nothing to do with AutoPatcher, or IE7), I ended up reinstalling Win XP several (3) times. This was an eMachines T3110, and re-installation was accomplished through a "Destructive System Recovery". "Destructive" meaning that it re-formated the HD before installing Win XP and applications from a recovery partition.

The first time I performed the system recovery, I used AutoPatcher to do all the updates and to install IE7 (plus Media Player 11, and other goodies). IE7 was screwed up as I mentioned before.

The second time I performed the system recovery, I never got to the point of installing IE7, before I decided to start over again.

The third (and final), time I performed the destructive system recovery, I did not use AutoPatcher at all. I used MS Update to install all the updates, including IE7. This time IE7 worked fine.

For this particular computer, it seems conclusive that AutoPatcher was the problem. How, I can only speculate. Maybe it didn't like the order that AutoPatcher installed the various components (IE7 getting installed before .NET Framework was installed?). Maybe there was a problem with .NET Framework in it originally, until it got updated, before IE7 was installed? I don't know.

--

As for the other computer that had the same AutoPatcher/IE7 problem (a 4 year-old Dell), I had previously used AutoPatcher on it to update it. When I worked on it recently, it had been several months since I last saw it and used AutoPatcher on it. Rather than download and install all the AutoPatcher updates for those months, I uninstalled the old AutoPatcher, then installed AutoPatcher November 2006 Full, the December 2006 Update, then the December 2006 Patch, before running it to update and install IE7. When IE7 failed to work properly, I uninstalled IE7 so that it rolled back to IE6. I figured that this client didn't care what version of IE was running, as long as it worked. I didn't have the time to experiment by trying to install IE7 again via MS Update, which I would have liked to try.

How's that for detail?

[greg232]

*.ini file with settings works randomly, I'm saving setting and after running AP with suitable parameter lot of settings have dissapeared, other aren't properly loaded (looks to be included and properly set in *.ini), into *.ini file there's lot of missing setting which AP includes

[LINEMAN78]

I had the same problem today as Bruce using the microsoft update system so I do not believe that this is limited to the Autopatch system. IE opens my homepage and looks like IE6 but when I look at About it says IE7. Also, if I attempt to go to a different site other than my home page it will display the message. Also, it displays the same message when I attempt to open windows update. I have found 3 possable fixes but have not had a chance to try them yet. 2 are registry modifications, the 3rd is modifying the windows installer Group Policy. I will let you know if I am successful

[Angelico_Payne]

I got 3 issues after applying AP on clean system (AP NOV full + dec&jan updates)

1.IE will not install, no matter what I do, including trying to install it singe after AP has finished

2.WMP11 is installed, but wants to go online to be validated. Otherwise it won't start. (Someone on forum said no online validation is required as long as u have valid key) and i dont want to crack validation every time i do AP.

3.System seems slower and slugish after installing AP.

*All testing have been done on real comp, not a V-sys.

[onionstick]

I just uninstalled IE7, works fine now.