psmsi Wiki & Documentation Rss Feed

Updated Wiki: Documentation

heaths — Tue, 07 May 2013 20:19:52 GMT

Help

The list of features and help resources can be found for each major release in the Help section. You may also view the discussion threads from the tabs above. If you have found a bug or want to see a new features, use the issue tracker from the tabs above. Please be sure to provide sufficient steps to reproduce the problem along with a detailed description of what happen and what you expect to happen.

You may also discuss new feature ideas in the discussion tab.

Current release: 2.1.5

Version 2 provides a snap-in registered to the machine and a module that can be installed by a user without administrative privileges. The module is installed to a user profile but can also be installed to a secure machine location for use by all users. The snap-in and the module provide the same set of cmdlets, but the module does provide additional functions and aliases for backward call-compatibility with version 1 cmdlets.

To use either the module or the snap-in from from this release, you must install PowerShell 2.0. PowerShell 2.0 is included in both Windows 7 by default, and Windows Server 2008 R2 as an optional feature.

Help (v2.1.4) (Applies to 2.1.5)
Formats

Examples

Types sent through the pipeline by these cmdlets are designed to work with standard cmdlets so you can string many cmdlets together. See Examples for a few ideas of what you can do with the Windows Installer PowerShell snap-in.

Updated Wiki: Formats

heaths — Tue, 07 May 2013 20:17:53 GMT

Formats

Several formats are provided for display. You can also view the formats for an output type using the following expression.

get-formatdata -typename (get-msiproductinfo)[0].pstypenames | select -expand format*

To view all predefined views for the psmsi snap-in, use the expressions below.

$formats = dir (get-pssnapin psmsi).ApplicationBase -filter *formats.ps1xml
$formats | %{ [xml]$xml = gc $_.FullName; $xml.Configuration.ViewDefinitions.View } `
| sort {$_.ViewSelectedBy.TypeName}, Name `
| ft @{l="Type"; e={$_.ViewSelectedBy.TypeName} }, Name, @{l="Control"; e={$_.psbase.ChildNodes.ItemOf(2)} } -auto

PackageSource

Displays source list information for patches and products.

Format-Table -View Indexed

PS> get-msiproductinfo | get-msisource | ft -view indexed

 Index Type     Path
 ----- ----     ----
     0 Network  C:\MSOCache\All Users\{90120000-0030-0000-0000-0000000FF1CE}-C\
     0 Network  C:\MSOCache\All Users\{90120000-0021-0000-0000-0000000FF1CE}-C\

Format-List -View Indexed

PS> get-msiproductinfo | get-msisource | fl -view indexed

Index : 0
Type  : Network
Path  : C:\MSOCache\All Users\{90120000-0030-0000-0000-0000000FF1CE}-C\

Index : 0
Type  : Network
Path  : C:\MSOCache\All Users\{90120000-0021-0000-0000-0000000FF1CE}-C\

Format-Table -View Package

PS> (get-msiproductinfo), (get-msipatchinfo) | get-msisource | ft -view package

    ProductCode: {90120000-0030-0000-0000-0000000FF1CE}

Index Type    Path
----- ----    ----
    0 Network C:\MSOCache\All Users\{90120000-0030-0000-0000-0000000FF1CE}-C\

    PatchCode: {7CA106D1-664C-40D4-BD94-5783ED9B7E3E}

Index Type    Path
----- ----    ----
    0 Network \\products\public\Products\Applications\User\Office_2007\Visio_Professional_2007\updates\

PatchInfo

Displays patch information.

Format-Table -View Package

PS> get-msipatchinfo | ft -view package

PatchCode                                   State LocalPackage                      DisplayName
---------                                   ----- ------------                      -----------
{BEE75E01-DD3F-4D5F-B96C-609E6538D419}    Applied C:\Windows\Installer\312e0a2d.msp 2007 Microsoft Office Suite Serv...
{02B5A17B-01BE-4BA6-95F1-1CBB46EBC76E}    Applied C:\Windows\Installer\1a9654c8.msp Security Update for Office 2007 ...

Format-List -View Patch

PS> get-msipatchinfo | fl -view patch

PatchCode     : {BEE75E01-DD3F-4D5F-B96C-609E6538D419}
ProductCode   : {90120000-0030-0000-0000-0000000FF1CE}
DisplayName   : 2007 Microsoft Office Suite Service Pack 1 (SP1)
State         : Applied
Uninstallable : False

PatchCode     : {02B5A17B-01BE-4BA6-95F1-1CBB46EBC76E}
ProductCode   : {90120000-0030-0000-0000-0000000FF1CE}
DisplayName   : Security Update for Office 2007 (KB947801)
State         : Applied
Uninstallable : True

Format-Table -View Patch

PS> get-msipatchinfo | ft -view patch

PatchCode                                    State  Uninstallable DisplayName
---------                                    -----  ------------- -----------
{BEE75E01-DD3F-4D5F-B96C-609E6538D419}     Applied          False 2007 Microsoft Office Suite Service Pack 1 (SP1)
{02B5A17B-01BE-4BA6-95F1-1CBB46EBC76E}     Applied           True Security Update for Office 2007 (KB947801)

Format-Table -View State

PS> get-msipatchinfo | ft -view state

   ProductCode: {90120000-0030-0000-0000-0000000FF1CE}

PatchCode                                   State  Uninstallable DisplayName
---------                                   -----  ------------- -----------
{BEE75E01-DD3F-4D5F-B96C-609E6538D419}    Applied          False 2007 Microsoft Office Suite Service Pack 1 (SP1)
{02B5A17B-01BE-4BA6-95F1-1CBB46EBC76E}    Applied           True Security Update for Office 2007 (KB947801)

ProductInfo

Displays product information.

Format-Table -View Package

PS> get-msiproductinfo | ft -view package

ProductCode                             LocalPackage                      ProductName
-----------                             ------------                      -----------
{90120000-0030-0000-0000-0000000FF1CE}  C:\Windows\Installer\a5824.msi    Microsoft Office Enterprise 2007
{90120000-0021-0000-0000-0000000FF1CE}  C:\Windows\Installer\33704f3.msi  Microsoft Office Visual Web Developer 2007

Format-Table -View Product

PS> get-msiproductinfo | ft -view product

ProductCode                             ProductVersion       ProductName
-----------                             --------------       -----------
{90120000-0030-0000-0000-0000000FF1CE}  12.0.6215.1000       Microsoft Office Enterprise 2007
{90120000-0021-0000-0000-0000000FF1CE}  12.0.4518.1066       Microsoft Office Visual Web Developer 2007

Format-List -View Product

PS> get-msiproductinfo | fl -view product

ProductCode    : {90120000-0030-0000-0000-0000000FF1CE}
Manufacturer   : Microsoft Corporation
ProductName    : Microsoft Office Enterprise 2007
ProductVersion : 12.0.6215.1000
InstallDate    : 3/12/2008 12:00:00 AM

ProductCode    : {90120000-0021-0000-0000-0000000FF1CE}
Manufacturer   : Microsoft Corporation
ProductName    : Microsoft Office Visual Web Developer 2007
ProductVersion : 12.0.4518.1066
InstallDate    : 2/14/2008 12:00:00 AM

Updated Wiki: Documentation

heaths — Tue, 30 Apr 2013 23:37:38 GMT

Help

Current release: 2.1.5

Help (v2.1.4) (Applies to 2.1.5)
Formats

Examples

New Comment on "Get-MSIProductInfo.v2.1.4"

heaths — Sun, 21 Apr 2013 02:28:20 GMT

The Windows Installer APIs do not work across machine boundaries. You can use WMI but won't have quite the same Experience: get-wmiobject Win32_Product -computer name

Updated Wiki: Home

heaths — Sun, 20 May 2012 00:54:27 GMT

Project Description

Exposes Windows Installer functionality to PowerShell, providing means to query installed product and patch information and to query views on packages.

PowerShell is a powerful command shell that pipes objects - not just text. Because of this ability, you can string practically unrelated commands together in many different ways to work on different types of objects, all built on .NET. You can use all the properties and methods of those objects passed through the pipeline instead of being limited by the text sent to you as with traditional command shells.

This Windows Installer module for PowerShell provides cmdlets ("command-lets") - similar to functions - to query package states, patches registered and applied to products, and more. You can use it to query Windows Installer products and patches installed on your system.

get-msiproductinfo | where { $_.Name -like "*Visual Studio*" }

You can even use it to determine which products installed a particular file on your system.

get-msicomponentinfo `
    | where { $_.path -eq 'C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe'} `
    | get-msiproductinfo

You can find more Examples and usage in the Documentation.

News

Work has begun again! I'm taking any suggestions, but looking into more functionality including remote capabilities based on PSSessions (since Windows Installer APIs themselves are not remotable). I've also switched the project system over to Git and have got unit and functional tests working on PowerShell v3 Beta.

And after careful consideration, I've decided that functionality to modify packages will not be a priority. I might not do them at all. As a developer on the WiX Toolset, I've worked with others on helping setup developers avoid problems by adding lots of validation into the toolset. Allowing modifications of MSI files directory really goes against that. If modifications are needed, developers really should modify the source. But querying MSI packages (and related package types) is still helpful and I'll likely be including cmdlets for installing, repairing, and uninstalling packages as well.

I'm still considering previous requests as well, but be sure to include any ideas in the Issue Tracker.

New Comment on "Get-MSIProductInfo.v2.1.4"

hecktor — Thu, 26 Apr 2012 22:24:00 GMT

This is a very good cmdlet. Can it please be updated so that you can run this against a given ComputerName? Get-MSIProductInfo -ComputerName

Updated Wiki: Examples

heaths — Wed, 09 Mar 2011 06:47:10 GMT

Examples

Below are some examples of what you can do with Windows Installer PowerShell Extensions, organized by cmdlets. For pre-defined formats to use below, see Formats.

Get-MSIFileHash

Get-MSIFileHash gets the 128-bit hash of files in a format compatible for storing in the MsiFileHash table. The where-object clause is there because these MSIHashPart* properties are not added to directories, and format-table determines columns based on the first item passed to it which is typically a directory.

dir $env:temp | ? { $_.PSIsContainer -eq $False } | get-msifilehash -passthru | ft name, msi* -auto

Get the file hashes for all files in the TEMP directory.

Get-MSIPatchInfo

Get-MSIPatchInfo gets information for applied, superseded, and obsolesced patches. Patches are only published on the system if they apply to a product already installed or advertised.

get-msipatchinfo -filter all | get-itemproperty | format-table fullname, lastwritetime, length -autosize

Get patch sizes for all installed patches

get-msipatchinfo -filter superseded | format-table patchcode, patchstate -group productcode -autosize

Identify superseded patches for installed products

get-msipatchinfo | where { $_.DisplayName -like "*KB123456*" } | group ProductCode | foreach {
start msiexec.exe "/uninstall `"$( ($_.Group | select -expand PatchCode) -join ';')`" /package `"$($_.Name)`"" -wait
}

Uninstall all patches with the same identity from all products efficiently.

Get-MSIProductInfo

Get-MSIProductInfo gets information for installed and advertised products.

get-msiproductinfo | ? {$_.productname -match "Visual Studio"} | format-table productcode, productname, versionstring -autosize

Get which Visual Studio products are installed

$ntaccount = new-object System.Security.Principal.NTAccount "domain\user"
$sid = $ntaccount.Translate([System.Security.Principal.SecurityIdentifier])
get-msiproductinfo -install userunmanaged -user $sid

Get which products are installed for another user (requires elevation)

Get-MSISource

Get-MSISource gets the source list for installed products.

get-msiproductinfo | % { ($_.ProductName); $_ | get-msisource | sort Index | ft SourceType, Path -auto }

Show the source list for each installed product

Updated Wiki: Home

heaths — Wed, 09 Feb 2011 18:56:41 GMT

Project Description

get-msiproductinfo | where { $_.Name -like "*Visual Studio*" }

You can even use it to determine which products installed a particular file on your system.

get-msicomponentinfo `
    | where { $_.path -eq 'C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe'} `
    | get-msiproductinfo

You can find more Examples and usage in the Documentation.

News

Version 2.1.5 supports PowerShell 2.0 and is the recommended download. PowerShell 2.0 is included in both Windows 7 by default, and Windows Server 2008 R2 as an optional feature.

Updated Wiki: Home

heaths — Wed, 09 Feb 2011 18:56:29 GMT

Project Description

get-msiproductinfo | where { $_.Name -like "*Visual Studio*" }

You can even use it to determine which products installed a particular file on your system.

get-msicomponentinfo `
    | where { $_.path -eq 'C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe'} `
    | get-msiproductinfo

You can find more Examples and usage in the Documentation.

News

Version elease:35457 supports PowerShell 2.0 and is the recommended download. PowerShell 2.0 is included in both Windows 7 by default, and Windows Server 2008 R2 as an optional feature.

Updated Wiki: Formats

heaths — Mon, 06 Sep 2010 16:57:42 GMT

Formats

Several formats are provided for display. You can also view the formats for an output type using the following expression.

get-formatdata -typename (get-msiproductinfo)[0].pstypenames | select -expand format*

To view all predefined views for the psmsi snap-in, use the expressions below.

$formats = dir (get-pssnapin psmsi).ApplicationBase -filter *formats.ps1xml
$formats | %{ [xml]$xml = gc $_.FullName; $xml.Configuration.ViewDefinitions.View } `
| sort {$_.ViewSelectedBy.TypeName}, Name `
| ft @{l="Type"; e={$_.ViewSelectedBy.TypeName} }, Name, @{l="Control"; e={$_.psbase.ChildNodes.ItemOf(2)} } -auto

PackageSource

Displays source list information for patches and products.

Format-Table -View Indexed

PS> get-msiproductinfo | get-msisource | ft -view indexed

 Index Type     Path
 ----- ----     ----
     0 Network  C:\MSOCache\All Users\{90120000-0030-0000-0000-0000000FF1CE}-C\
     0 Network  C:\MSOCache\All Users\{90120000-0021-0000-0000-0000000FF1CE}-C\

Format-List -View Indexed

PS> get-msiproductinfo | get-msisource | fl -view indexed

Index : 0
Type  : Network
Path  : C:\MSOCache\All Users\{90120000-0030-0000-0000-0000000FF1CE}-C\

Index : 0
Type  : Network
Path  : C:\MSOCache\All Users\{90120000-0021-0000-0000-0000000FF1CE}-C\

Format-Table -View Package

PS> (get-msiproductinfo), (get-msipatchinfo) | get-msisource | ft -view package

    ProductCode: {90120000-0030-0000-0000-0000000FF1CE}

Index Type    Path
----- ----    ----
    0 Network C:\MSOCache\All Users\{90120000-0030-0000-0000-0000000FF1CE}-C\

    PatchCode: {7CA106D1-664C-40D4-BD94-5783ED9B7E3E}

Index Type    Path
----- ----    ----
    0 Network \\products\public\Products\Applications\User\Office_2007\Visio_Professional_2007\updates\

PatchInfo

Displays patch information.

Format-Table -View Package

PS> get-msipatchinfo | ft -view package

PatchCode                                   State LocalPackage                      DisplayName
---------                                   ----- ------------                      -----------
{BEE75E01-DD3F-4D5F-B96C-609E6538D419}    Applied C:\Windows\Installer\312e0a2d.msp 2007 Microsoft Office Suite Serv...
{02B5A17B-01BE-4BA6-95F1-1CBB46EBC76E}    Applied C:\Windows\Installer\1a9654c8.msp Security Update for Office 2007 ...

Format-List -View Patch

PS> get-msipatchinfo | fl -view patch

PatchCode     : {BEE75E01-DD3F-4D5F-B96C-609E6538D419}
ProductCode   : {90120000-0030-0000-0000-0000000FF1CE}
DisplayName   : 2007 Microsoft Office Suite Service Pack 1 (SP1)
State         : Applied
Uninstallable : False

PatchCode     : {02B5A17B-01BE-4BA6-95F1-1CBB46EBC76E}
ProductCode   : {90120000-0030-0000-0000-0000000FF1CE}
DisplayName   : Security Update for Office 2007 (KB947801)
State         : Applied
Uninstallable : True

Format-Table -View Patch

PS> get-msipatchinfo | ft -view patch

PatchCode                                    State  Uninstallable DisplayName
---------                                    -----  ------------- -----------
{BEE75E01-DD3F-4D5F-B96C-609E6538D419}     Applied          False 2007 Microsoft Office Suite Service Pack 1 (SP1)
{02B5A17B-01BE-4BA6-95F1-1CBB46EBC76E}     Applied           True Security Update for Office 2007 (KB947801)

Format-Table -View State

PS> get-msipatchinfo | ft -view state

   ProductCode: {90120000-0030-0000-0000-0000000FF1CE}

PatchCode                                   State  Uninstallable DisplayName
---------                                   -----  ------------- -----------
{BEE75E01-DD3F-4D5F-B96C-609E6538D419}    Applied          False 2007 Microsoft Office Suite Service Pack 1 (SP1)
{02B5A17B-01BE-4BA6-95F1-1CBB46EBC76E}    Applied           True Security Update for Office 2007 (KB947801)

ProductInfo

Displays product information.

Format-Table -View Package

PS> get-msiproductinfo | ft -view package

ProductCode                             LocalPackage                      ProductName
-----------                             ------------                      -----------
{90120000-0030-0000-0000-0000000FF1CE}  C:\Windows\Installer\a5824.msi    Microsoft Office Enterprise 2007
{90120000-0021-0000-0000-0000000FF1CE}  C:\Windows\Installer\33704f3.msi  Microsoft Office Visual Web Developer 2007

Format-Table -View Product

PS> get-msiproductinfo | ft -view product

ProductCode                             ProductVersion       ProductName
-----------                             --------------       -----------
{90120000-0030-0000-0000-0000000FF1CE}  12.0.6215.1000       Microsoft Office Enterprise 2007
{90120000-0021-0000-0000-0000000FF1CE}  12.0.4518.1066       Microsoft Office Visual Web Developer 2007

Format-List -View Product

PS> get-msiproductinfo | fl -view product

ProductCode    : {90120000-0030-0000-0000-0000000FF1CE}
Manufacturer   : Microsoft Corporation
ProductName    : Microsoft Office Enterprise 2007
ProductVersion : 12.0.6215.1000
InstallDate    : 3/12/2008 12:00:00 AM

ProductCode    : {90120000-0021-0000-0000-0000000FF1CE}
Manufacturer   : Microsoft Corporation
ProductName    : Microsoft Office Visual Web Developer 2007
ProductVersion : 12.0.4518.1066
InstallDate    : 2/14/2008 12:00:00 AM

Updated Wiki: Help

heaths — Mon, 06 Sep 2010 16:31:20 GMT

Help

A list of features and help is provided below for each major release.

1.0 RTW

Version 1 provides a snap-in registered to the machine that has a limited set of cmdlets available for querying products and patches on the system, along with a couple more utility cmdlets.

2.1.4

Updated Wiki: Home

heaths — Thu, 05 Nov 2009 02:41:37 GMT

Project Description

get-msiproductinfo | where { $_.Name -like "*Visual Studio*" }

You can even use it to determine which products installed a particular file on your system.

get-msicomponentinfo `
    | where { $_.path -eq 'C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe'} `
    | get-msiproductinfo

You can find more Examples and usage in the Documentation.

News

Version 2.1.4 supports PowerShell 2.0 and is the recommended download. PowerShell 2.0 is included in both Windows 7 by default, and Windows Server 2008 R2 as an optional feature.

Updated Wiki: Home

heaths — Thu, 05 Nov 2009 02:40:21 GMT

Project Description

get-msiproductinfo | where { $_.Name -like "*Visual Studio*" }

You can even use it to determine which products installed a particular file on your system.

get-msicomponentinfo `
    | where { $_.path -eq 'C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe'} `
    | get-msiproductinfo

You can find more Examples and usage in the Documentation.

News

Version 2.1.4 supports PowerShell 2.0. PowerShell 2.0 is included in both Windows 7 by default, and Windows Server 2008 R2 as an optional feature.

Updated Wiki: Home

heaths — Thu, 05 Nov 2009 02:37:19 GMT

Project Description

get-msiproductinfo | where { $_.Name -like "*Visual Studio*" }

You can even use it to determine which products installed a particular file on your system.

get-msicomponentinfo `
    | where { $_.path -eq 'C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe'} `
    | get-msiproductinfo

You can find more Examples and usage in the Documentation.

News

Version 2.1.4 that supports PowerShell 2.0. PowerShell 2.0 is included in both Windows 7 by default, and Windows Server 2008 R2 as an optional feature.

Updated Wiki: Help

heaths — Thu, 05 Nov 2009 02:24:45 GMT

Help

A list of features and help is provided below for each major release.

1.0 RTW

Version 1 provides a snap-in registered to the machine that has a limited set of cmdlets available for querying products and patches on the system, along with a couple more utility cmdlets.

2.1.4

Updated Wiki: Documentation

heaths — Thu, 05 Nov 2009 02:24:24 GMT

Help

Current release: 2.1.4

Examples

Updated Wiki: Documentation

heaths — Thu, 05 Nov 2009 02:20:42 GMT

Help

Current release: 2.1.4

Version 2 provides a snap-in registered to the machine and a module that can be installed by a user without administrative privileges. The module is installed to a user profile but can also be installed to a secure machine location for use by all users. The snap-in and the module provide the same set of cmdlets, but the module does provide additional functions and aliases for backward call-compatibility with version 1 cmdlets.

To use either the module or the snap-in from from this release, you must install Windows 7 RC. PowerShell 2.0 RC should be released downlevel in the near future.

Examples

Updated Wiki: Documentation

heaths — Thu, 05 Nov 2009 02:18:13 GMT

Help

Examples

Updated Wiki: Home

heaths — Thu, 05 Nov 2009 02:17:26 GMT

Project Description

Exposes Windows Installer functionality to PowerShell, providing means to query installed product and patch information and to query views on packages.

PowerShell is a powerful command shell that pipes objects - not just text. Because of this ability, you can string practically unrelated commands together in many different ways to work on different types of objects, all built on .NET. You can use all the properties and methods of those objects passed through the pipeline instead of being limited by the text sent to you as with traditional command shells.

This Windows Installer snap-in provides cmdlets ("command-lets") - similar to functions - to query package states, patches registered and applied to products, and more.

News

I have put up version 2.1.4 that supports PowerShell 2.0 RC on Windows 7 RC.

Updated Wiki: Help

heaths — Thu, 05 Nov 2009 02:17:00 GMT

Help

A list of features and help is provided below for each major release.

1.0 RTW

Version 1 provides a snap-in registered to the machine that has a limited set of cmdlets available for querying products and patches on the system, along with a couple more utility cmdlets.

2.1.4

Version 2 provides a snap-in registered to the machine and a module that can be installed by a user without administrative privileges. The module is installed to a user profile but can also be installed to a secure machine location for use by all users. The snap-in and the module provide the same set of cmdlets, but the module does provide additional functions and aliases for backward call-compatibility with version 1 cmdlets.

To use either the module or the snap-in from from this release, you must install Windows 7 RC. PowerShell 2.0 RC should be released downlevel in the near future.