Documentation for each release is linked from the releases' pages. 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.2.1
This a servicing release
which addresses certain issues
. It includes all changes from previous versions and will automatically upgrade any previous versions installed.
See the documentation
for more information about cmdlets and to see examples, or use get-help
with any of the cmdlet names.
To use the module 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. PowerShell 3.0
is recommended, and is included in Windows 8 and Windows Server 2012.
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 module. Many cmdlets also contain examples you can read by using get-help <cmdlet name> -examples
Code contributions are welcome, but you will have to sign a legal form prior to a pull request being accepted.
Click on the Source Code tab and click on the Fork button to get started. Once forking is completely, click on the Clone button. Follow the instructions.
If you want to create a code change from a specific release, you can either branch from a specific commit or a release tag. To see all the tags, type git tag
in the local repository.
You can add my public key used for verifying signed tags directly from the repo:
git cat-file blob pubkey | gpg --import
You can then verify tags:
git tag -v v2.2.0
For a great resource on Git, see http://git-scm.com/book