1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

More on the installer

Discussion in 'Support' started by vefatica, May 30, 2012.

  1. vefatica

    Joined:
    May 20, 2008
    Messages:
    5,507
    Likes Received:
    9
    I now have these:

    Code:
    c:\users\vefatica\appdata\roaming\jp software> ffind /m /s tcmd.msi | cut -c47-
    Take Command 13.04 13.04.53\install\B321F08\tcmd.msi
    Take Command 13.04 13.04.54\install\6CDFEDC\tcmd.msi
    Take Command 13.04 13.04.55\install\4849765\tcmd.msi
    Take Command 13.04 13.04.56\install\A0D33EA\tcmd.msi
    Take Command 13.04 13.04.57\install\0036A24\tcmd.msi
    Take Command 13.04 13.04.58\install\CAB9432\tcmd.msi
    Take Command 13.04 13.04.59\install\085C848\tcmd.msi
    Take Command 13.04 13.04.60\install\A3AB90E\tcmd.msi
    Take Command 13.04 13.04.61\install\D20B69A\tcmd.msi
    Take Command 13.04 13.04.62\install\A12BD11\tcmd.msi
    Take Command 13.04 13.04.63\install\779AB05\tcmd.msi
    Take Command 14.0 14.00.14\install\2308B41\tcmd.msi
    Take Command 14.0 14.00.15\install\B3A33F1\tcmd.msi
    Take Command 14.0 14.00.16\install\9135A33\tcmd.msi
    Take Command 14.0 14.00.17\install\303C29A\tcmd.msi
    Take Command 14.0 14.00.18\install\91D8BDC\tcmd.msi
    Take Command 14.0 14.00.19\install\E6BFA0E\tcmd.msi
    They would not accumulate if, when updating from minor version N to N+K, the tree for minor version N were deleted. That would have worked nicely for v13 because, of all these foldernames associated with v13
    Code:
    B321F08 6CDFEDC 4849765 A0D33EA 0036A24 CAB9432 085C848 A3AB90E D20B69A A12BD11 779AB05
    only the last (current) one appears in the text of any registry key, value, or data. And the last, current one has extensive install/uninstall/modify info in the registry.

    It's different for v14 (at least from build 14 on). Even ones that have been updated have (apparently useless) registry entries. For example here are the entries for v14b14 [and there are similar ones for b15, b16, b17, and b18].

    Code:
    Take Command 14.0 14.00.14\install\2308B41\tcmd.msi
    Searching registry for 2308B41
     
    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Folders
     
        Value: C:\Windows\Installer\{146CB12F-D64D-4F15-81D7-4DC8E2308B41}\
     
    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\TempPackages
     
        Value: C:\Windows\Installer\{146CB12F-D64D-4F15-81D7-4DC8E2308B41}\tcmd.exe
     
    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\TempPackages
     
        Value: C:\Windows\Installer\{146CB12F-D64D-4F15-81D7-4DC8E2308B41}\TakeCommand.exe
    Only the last, current, b19, has useful entries. Please see the attached TCMSIFILES.TCT.
     

    Attached Files:

    #1
  2. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    7,200
    Likes Received:
    21
    It doesn't matter how often you complain about this -- I do not have source code for the Windows Installer, and I cannot do anything about your problem.
     
    #2
  3. Steve Fabian

    Joined:
    May 20, 2008
    Messages:
    3,531
    Likes Received:
    4
    Would it not be possible for the start up code in TCC to check for such junk files and delete them, possibly using a specific TCC batch file included in the distribution (which might delete itself once successfully run)?
     
    #3
  4. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    7,200
    Likes Received:
    21
    If you want to delete the files (and if you even have them; most people don't), put it in your TCSTART. I am not going to embed anything in TCC.
     
    #4
  5. vefatica

    Joined:
    May 20, 2008
    Messages:
    5,507
    Likes Received:
    9
    Windows installer has not changed here (no auto-updates) but the registry remnants of a minor version update have changed between v13 and v14 (from none to a few apparently useless ones). Did you look at the document I attached to my recent post?

    Can't you, at the end of a minor version update, delete the APPDATA tree for the minor version just updated?
     
    #5
  6. vefatica

    Joined:
    May 20, 2008
    Messages:
    5,507
    Likes Received:
    9
    This is eerie (and long, sorry). The system event log shows that at 2010-05-31, 00:43:46 the Windows Installer service started. The security log shows that at the same time, SYSTEM logged on (services.exe) and SYSTEM acquired special priveleges. KEYTIMES reveals that these keys were modified a few seconds later:
    Code:
    2012-05-31  00:43:53  HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Folders
    2012-05-31  00:43:53  HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer
    2012-05-31  00:43:53  HKU\S-1-5-21-1441759175-1591074457-3961414381-1000\Software\Microsoft\RestartManager
    And @FILEDATA/@FILETIME reveal that at 2012-05-31, 00:43:53 the folder c:\windows\installer was modified.

    The reg keys/values and the files in c:\windows\installer\ that I had complained references older/updated versions of TCv14 (but were absent for older/updated versions of TCv13) are now gone. They were references like these (found after updating b18 to b19 a week after installing b14):
    Code:
    Take Command 14.0 14.00.14\install\2308B41\tcmd.msi
    Searching registry for 2308B41
     
    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Folders
     
        Value: C:\Windows\Installer\{146CB12F-D64D-4F15-81D7-4DC8E2308B41}\
     
    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\TempPackages
     
        Value: C:\Windows\Installer\{146CB12F-D64D-4F15-81D7-4DC8E2308B41}\tcmd.exe
     
    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\TempPackages
     
        Value: C:\Windows\Installer\{146CB12F-D64D-4F15-81D7-4DC8E2308B41}\TakeCommand.exe
    At the time all this happened, I was downstairs, drinking beer and watching Charlie Rose (and I couldn't have done it that fast anyway). I could not find a scheduled task that would account for it. So ...

    Does anyone have an idea why it happened, and why it happened when it did?

    With respect to TCMD installations, I'd now call the registry "clean"; that is, it contains only references to the most recently installed minor versions. I have attached an updated file showing this.

    So my only remaining gripe is the updating a minor version does not delete the tree for the minor version that was uninstalled. That is, I still have these (below) and still wonder if we're supposed to collect these forever!

    Code:
    Take Command 13.04 13.04.53\install\B321F08\tcmd.msi
    Take Command 13.04 13.04.54\install\6CDFEDC\tcmd.msi
    Take Command 13.04 13.04.55\install\4849765\tcmd.msi
    Take Command 13.04 13.04.56\install\A0D33EA\tcmd.msi
    Take Command 13.04 13.04.57\install\0036A24\tcmd.msi
    Take Command 13.04 13.04.58\install\CAB9432\tcmd.msi
    Take Command 13.04 13.04.59\install\085C848\tcmd.msi
    Take Command 13.04 13.04.60\install\A3AB90E\tcmd.msi
    Take Command 13.04 13.04.61\install\D20B69A\tcmd.msi
    Take Command 13.04 13.04.62\install\A12BD11\tcmd.msi
    Take Command 13.04 13.04.63\install\779AB05\tcmd.msi
    Take Command 14.0 14.00.14\install\2308B41\tcmd.msi
    Take Command 14.0 14.00.15\install\B3A33F1\tcmd.msi
    Take Command 14.0 14.00.16\install\9135A33\tcmd.msi
    Take Command 14.0 14.00.17\install\303C29A\tcmd.msi
    Take Command 14.0 14.00.18\install\91D8BDC\tcmd.msi
    Take Command 14.0 14.00.19\install\E6BFA0E\tcmd.msi
     

    Attached Files:

    #6

Share This Page