[RESOLVED] Windows Installer doesn't open .msi files
Results 1 to 4 of 4

Thread: [RESOLVED] Windows Installer doesn't open .msi files

  1. #1
    Join Date
    May 2002
    Location
    Carol Stream, IL
    Posts
    63

    Resolved [RESOLVED] Windows Installer doesn't open .msi files

    W2KSP4
    When I try to open any legitimate .msi or .exe linked to an .msi, I get only the following syntax displayed in a box titled Windows Installer. There's an OK button that closes it.

    I encountered this once before and reinstalled Windows to fix it. I don't have any other issues now, so I don't want to reinstall if it can be avoided. Windows Installer service does start automatically and is running. I've installed 2.0, 3.0 and 3.1, but problem remains. I've got several things I need to install and have to get this fixed. Thanks




    Windows Installer. V 3.01.4000.1823

    msiexec /Option <Required Parameter> [Optional Parameter]

    Install Options
    </package | /i> <Product.msi>
    Installs or configures a product
    /a <Product.msi>
    Administrative install - Installs a product on the network
    /j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
    Advertises a product - m to all users, u to current user
    </uninstall | /x> <Product.msi | ProductCode>
    Uninstalls the product
    Display Options
    /quiet
    Quiet mode, no user interaction
    /passive
    Unattended mode - progress bar only
    /q[n|b|r|f]
    Sets user interface level
    n - No UI
    b - Basic UI
    r - Reduced UI
    f - Full UI (default)
    /help
    Help information
    Restart Options
    /norestart
    Do not restart after the installation is complete
    /promptrestart
    Prompts the user for restart if necessary
    /forcerestart
    Always restart the computer after installation
    Logging Options
    /l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
    i - Status messages
    w - Nonfatal warnings
    e - All error messages
    a - Start up of actions
    r - Action-specific records
    u - User requests
    c - Initial UI parameters
    m - Out-of-memory or fatal exit information
    o - Out-of-disk-space messages
    p - Terminal properties
    v - Verbose output
    x - Extra debugging information
    + - Append to existing log file
    ! - Flush each line to the log
    * - Log all information, except for v and x options
    /log <LogFile>
    Equivalent of /l* <LogFile>
    Update Options
    /update <Update1.msp>[;Update2.msp]
    Applies update(s)
    /uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi | ProductCode>
    Remove update(s) for a product
    Repair Options
    /f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
    Repairs a product
    p - only if file is missing
    o - if file is missing or an older version is installed (default)
    e - if file is missing or an equal or older version is installed
    d - if file is missing or a different version is installed
    c - if file is missing or checksum does not match the calculated value
    a - forces all files to be reinstalled
    u - all required user-specific registry entries (default)
    m - all required computer-specific registry entries (default)
    s - all existing shortcuts (default)
    v - runs from source and recaches local package
    Setting Public Properties
    [PROPERTY=PropertyValue]

    Consult the Windows Installer SDK for additional documentation on the
    command line syntax.

    Copyright Microsoft Corporation. All rights reserved.
    Portions of this software are based in part on the work of the Independent JPEG Group.

  2. #2
    Join Date
    Sep 1999
    Location
    Dallas, Tx.
    Posts
    20,713
    Might check the file association in folder options->file types and see if there is anything weird there.
    "Imagine a world where dogs took bad owners to the pound."

    http://www.hopeforpaws.org/

  3. #3
    Join Date
    Jun 2001
    Location
    Albuquerque, NM USA
    Posts
    14,457
    Jim
    WIN7 Ultimate SP1 64bit, IE 11, NTFS,
    cable, MS Security Essentials, Windows 7 firewall

  4. #4
    Join Date
    May 2002
    Location
    Carol Stream, IL
    Posts
    63
    This is strange. Problem was resolved after Steve's post. I posted quick reply, but for whatever reason, it's not posted. Here it is again:

    I had checked file associations, but after Steve's post, I thought I should investigate further. I tried to delete msi from file types, but couldn't, so I changed open action to IE and closed/saved it. Then I reopened it, changed it to point to c:\winnt\system32\msiexec.exe

    That did it. Thanks Steve, and I'll keep those kb links in file, Welshjim.

    Here's to another speedy resolution to the credit of this great forum!

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •