This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Advertised shortcut does not kick repair
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 22, 2011
03:01 PM
Advertised shortcut does not kick repair
So I am working on creating an MST for itunes...
Fresh install, everything is working great. The start menu shortcut is causing a repair for new users... as it should.
The problem I am running into is in an upgrade (manual install) situation.
If I manually install old version of itunes for user #1, then run on user # 2, it repairs as it should...
I then upgrade using msi/mst on user #2. It upgrades properly with my custom files etc.
If I login to user #1, run the start menu shortcut, it will not repair. Shouldn't it, since it was last run with old version?
The shortcut is advertised... the key file is itunes.exe (in [INSTALLDIR]). The way I thought it worked, is when advertised shortcut is run, it checks all key paths and kicks a repair if one is missing right? Or will it just check the target file key path?
Any ideas?
Fresh install, everything is working great. The start menu shortcut is causing a repair for new users... as it should.
The problem I am running into is in an upgrade (manual install) situation.
If I manually install old version of itunes for user #1, then run on user # 2, it repairs as it should...
I then upgrade using msi/mst on user #2. It upgrades properly with my custom files etc.
If I login to user #1, run the start menu shortcut, it will not repair. Shouldn't it, since it was last run with old version?
The shortcut is advertised... the key file is itunes.exe (in [INSTALLDIR]). The way I thought it worked, is when advertised shortcut is run, it checks all key paths and kicks a repair if one is missing right? Or will it just check the target file key path?
Any ideas?
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 22, 2011
07:04 PM
My understanding is, based on my experiment in early 2000, it checks key paths in the same feature as, in your case, iTunes.exe (please refer to Searching for a Broken Feature or Component), and repairs the feature; when the feature is a child feature, the same check ripples upward till top-level feature is reached.
dandirk wrote:Not sure why repair is expected if there is no broken/missing components. Is there?
If I login to user #1, run the start menu shortcut, it will not repair. Shouldn't it, since it was last run with old version?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 23, 2011
08:17 AM
That makes sense... but why does itunes repair for a new user then when first run? itunes.exe is in a shared location (no hkcu keys in component either). Going by that logic it shouldn't repair for a new user when first installed.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 23, 2011
10:17 PM
I would look at Event Viewer for events with MsiInstaller in Source column, it will indicate which components are casuing the repair.
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)