Hello all... Please help...

I am attempting to package my first 'self-repair on first use' style installation and I'm running into some issues that are about to make my head explode.

The software is SecureFX v6 and my packaging app is Wise Package Studio 7 SP3. SecureFX is an MSI installer wrapped in an EXE. I have been able to extract the MSI and create a transform. Now I'm trying to add two files that need to exist in the currently logged on user's profile and a regkey that needs to exist in HKCU for the currently logged on user.
The two files (Global.ini and SFXMenuToolbar.xml) are meant to configure the app to disable automatic updates and hide certain items in the toolbar. They need to exist in each user's profile under %APPDATA%\VanDyke\SecureFX\Config\. The HKCU regkey tells the app to where to set the app config folder.

I created a new top-level feature called CurrentUser. I added the two files and regkey to this feature as individual compontents and set each as the keypath for its component. I then set the shortcuts to advertised by changing the Target to the CurrentUser feature and the component to Securefx.exe. The shortcuts are not advertised by default. Securefx.exe is in the SecureFX feature, which is a sub-feature of CurrentUser.

The install works great for the username I run the install as. The two files are placed in the correct directory and the regkey is created properly. The app launches without issue and all my config settings are present. When I log in as another user and launch the app the self-repair appears to run, but the only component that gets created is the HKCU regkey. The two files never get created. I've also noticed that the icons for the shorcuts don't always get created. In other words, the shortcuts get created but they appear with no icons. I get the same results whether running the app as admin or basic user.

What am I doing wrong?

BTW, I can get repair to work using the ActiveSetup regkey method but I'm hoping to get the repair to launch on first use, not after a reboot\logon.

Any help would be GREATLY appreciated.
0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


You need to either put all of the files and registry key into one component and set the registry key as the keypath. Or keep them in individual components and place a different registry key into each of them settings the registry keys as the keypaths.

Self healing for the user will not work if a file is the keypath, it has to be a reg key.
Answered 06/05/2009 by: michaelnowell
Second Degree Blue Belt

Please log in to comment
BAH! Did not know that... Stupid learning curve. Thanks for the advice. I will give it a shot and let you know my results.
Answered 06/05/2009 by: mturman
Orange Belt

Please log in to comment
Thanks so much, michaelnowell, your suggestion worked perfectly. I am still experiencing some issues with the shorcut icons though.

The advertised shortcuts get created and work, but the icons for them do not always appear. It seems as though they appear prior to first-launch for the user I run the initial install as, but they dissapear after first-launch.
Also, they are usually not present at first-launch for other users on the system but do seem to appear after first-launch.

Any ideas???
Answered 06/10/2009 by: mturman
Orange Belt

Please log in to comment
Might be the icon is not getting cached properly.
Try to browse the icons after installing your application in admin from the source folder in the icon table.It will create entries separately and the icons will get cached properly.
Give it a try
Answered 06/10/2009 by: sapto123
Senior Yellow Belt

Please log in to comment
...or it may be the well-known "Windows disappearing up its own icon cache" problem. Sometime, it just gets confused. Deleting the icon cache file fixes that issue. Windows rebuilds at next start-up. In XP, it's C:\Documents and Settings\[%USERNAME%]\Local Settings\Application Data\IconCache.DB. Some people have reported that the file isn't always rebuilt. If you find that to be the case, change the screen colour depth and then change it back. In earlier Windows OSs, IIRC, the file is %SystemRoot%\ShellIconCache.

In both cases, the file has the 'Hidden' attribute.
Answered 06/11/2009 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity