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?
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: 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?
Not sure why repair is expected if there is no broken/missing components. Is there?
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.
