4 replies to this topic

[DesertJerry]

Two systems: #1 - XP Pro w/SP2 and all updates; #2 - XP Home now w/SP3.

#1 had PowerToys installed after being downloaded from Microsoft. #2 originally did not have any PowerToys installed.

Ran latest APUP then AutoPatcher on both.

AutoPatcher on #1 at Windows Addons > Microsoft PowerToys for Windows XP listed all items in blue indicating they were installed and 'found/recognized' by AutoPatcher.

Also on #1 at Windows Addons > TweakUI black for TweakUI 2.10 (eventhough it was actually installed) and blue for TweakUI Control Panel Shortcut.

AutoPatcher on #2 at the same location listed all items in black indicating not installed; same for TweakUI.

Checked ALL items on #2 for PowerToys and Tweakui - clicked Next and indications from AutoPatcher were that they were all installed and system rebooted.

Restarted AutoPatcher on #2 and PowerToys was blue only for TaskBar Magnifier and Image Resizer and TweakUi was blue for Control Panel Shortcut.

Figuring this had to be in error I copied all the PowerToys installer programs from #1 to #2. I then ran each PowerToy's installer and, in each case, was given a Repair or Remove option; selected Remove. When that was done I then re-ran the individual installers and this time selected a Custom install. I installed ALL in the folder I created and selected: \Program Files\Accessories\Powertoys. Each installed successfully and the VBS file I had was used to also create TweakUi in the Control Panel.

AutoPatcher on #2 restarted and now ALL PowerToys appeared in blue, indicating they were installed and found by AutoPatcher, same for the TweakUI Control Shortcut.

So, why, given the above, did the install from AutPatcher not appear to work; why did almost all stay black?

Also, I can't believe I'm the only one that this has happened to.

[Erik Ramey]

You're going to need to do some troubleshooting yourself since I don't have the powertoys in the APUP version. (Don't have access to the module right now too. When you need to do is to go to the module within Autopatcher. Once you find it, probably in the components subfolder, open up the module in notepad.

You are going to be looking for this portion of the module:

[DetectionRegistry]
RegistryPath= "If there is something in here, detection is based in the registry" This is the location of the key
KeyName= "This is the name of the key"
KeyValue= "This is the value of the key"

[DetectionFile]
FilePath="If there is something here, detection is based on a file on your computer" This is where it's located"
FileName= "This is the name of the file AP is looking for"
FileVersion= "This is the version of the name AP is looking for"

Once you have found what the module is looking for, go to that location on your computer/registry and compare.

[Cristiano]

TweakUI 2.10 doesn't have an proper detection. this is done by adding some info in windows registry. the version of this module that i have in here do that by adding this at registry:
Windows Registry Editor Version 5.00

;AutoPatcher Detection
[HKEY_LOCAL_MACHINE\SOFTWARE\AutoPatcher\PowerToys]
"Tweak UI"="Installed"

then, TweakUI210_x86_ptb.apm module checks if this is installed looking for this:
[DetectionRegistry]
RegistryPath=HKLM\Software\AutoPatcher\PowerToys
KeyName=Tweak UI
KeyValue=Installed

the same issue happends with several tweak modules. are you sure that you have the latest version (untouched) of this modules that you are trying to install? if you aren't 100% sure, i suggest you to install some version of your language and replace the ones that you have.

another issue that sometimes may happend in some windows: some registry permissions may be changed and deny adding things like AP does. you may be running an limited user account, etc.

by the way: this modules are exact the same since a lot of time ago. in deed, you may not be the only one with this issue. but nobody else has reported this issue that i can remember.

[DesertJerry]

Erik Ramey, on Dec 14 2007, 10:57 PM, said:

You're going to need to do some troubleshooting yourself since I don't have the powertoys in the APUP version. (Don't have access to the module right now too. When you need to do is to go to the module within Autopatcher. Once you find it, probably in the components subfolder, open up the module in notepad.

You are going to be looking for this portion of the module:

[DetectionRegistry]
RegistryPath= "If there is something in here, detection is based in the registry" This is the location of the key
KeyName= "This is the name of the key"
KeyValue= "This is the value of the key"

[DetectionFile]
FilePath="If there is something here, detection is based on a file on your computer" This is where it's located"
FileName= "This is the name of the file AP is looking for"
FileVersion= "This is the version of the name AP is looking for"

Once you have found what the module is looking for, go to that location on your computer/registry and compare.

I read the .APM file and the [DetectionRegistry] info matched with the same location in the registry.

The .APM file's [DetectionFile] had no info for FilePath=, FileName=, or FileVersion=.

Same for all PowerToys and TweakUI.

Note that this info is on #1 system that has the PowerToys installed in the location I selected for the Custom install.

[DesertJerry]

Cristiano, on Dec 15 2007, 02:06 AM, said:

;AutoPatcher Detection
[HKEY_LOCAL_MACHINE\SOFTWARE\AutoPatcher\PowerToys]
"Tweak UI"="Installed"

This key is not in my registry - remember I installed TweakUI as a PowerToy download - not from within AutoPatcher.

then, TweakUI210_x86_ptb.apm module checks if this is installed looking for this:
[DetectionRegistry]
RegistryPath=HKLM\Software\AutoPatcher\PowerToys
KeyName=Tweak UI
KeyValue=Installed

Again, this key is non-existant - see abovew.


the same issue happends with several tweak modules. are you sure that you have the latest version (untouched) of this modules that you are trying to install? if you aren't 100% sure, i suggest you to install some version of your language and replace the ones that you have.

I have TweakUI 2.10 from Microsoft; the latest version.

another issue that sometimes may happend in some windows: some registry permissions may be changed and deny adding things like AP does. you may be running an limited user account, etc.

I am the Administrator and was running the system as such.

by the way: this modules are exact the same since a lot of time ago. in deed, you may not be the only one with this issue. but nobody else has reported this issue that i can remember.