> For the complete documentation index, see [llms.txt](https://doc.sitecorepowershell.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.sitecorepowershell.com/appendix/packaging/install-updatepackage.md).

# Install-UpdatePackage

Installs a Sitecore update package from the specified path.

## Syntax

Install-UpdatePackage \[-Path] \<String> \[\[-RollbackPackagePath] \<String>] -UpgradeAction \<Preview | Upgrade> -InstallMode \<Install | Update>

## Detailed Description

The Install-UpdatePackage command installs update packages that are used created by Sitecore CMS updates, TDS, and Courier.

Install-UpdatePackage. Install-UpdatePackage -Path "C:\Projects\LaunchSitecore.TDSMaster.update" -UpgradeAction {Preview or Upgrade} -InstallMode {Install or Update}

© 2010-2019 Adam Najmanowicz, Michael West. All rights reserved. Sitecore PowerShell Extensions

## Parameters

### -Path \<String>

Path to the .update package on the Sitecore server disk drive.

| Aliases                     |       |
| --------------------------- | ----- |
| Required?                   | true  |
| Position?                   | 1     |
| Default Value               |       |
| Accept Pipeline Input?      | false |
| Accept Wildcard Characters? | false |

### -RollbackPackagePath \<String>

Specify Rollback Package Path - for rolling back if the installation was not functioning as expected.

| Aliases                     |       |
| --------------------------- | ----- |
| Required?                   | false |
| Position?                   | 1     |
| Default Value               |       |
| Accept Pipeline Input?      | false |
| Accept Wildcard Characters? | false |

### -UpgradeAction \<UpgradeAction>

Preview / Upgrade

| Aliases                     |       |
| --------------------------- | ----- |
| Required?                   | true  |
| Position?                   | named |
| Default Value               |       |
| Accept Pipeline Input?      | false |
| Accept Wildcard Characters? | false |

### -InstallMode \<InstallMode>

Install / Update

| Aliases                     |       |
| --------------------------- | ----- |
| Required?                   | true  |
| Position?                   | named |
| Default Value               |       |
| Accept Pipeline Input?      | false |
| Accept Wildcard Characters? | false |

## Outputs

The output type is the type of the objects that the cmdlet emits.

* Sitecore.Update.Installer.ContingencyEntry

## Notes

Help Author: Adam Najmanowicz, Michael West

## Examples

### EXAMPLE

```powershell
PS master:\> Install-UpdatePackage -Path "C:\Projects\LaunchSitecore.TDSMaster.update" -UpgradeAction Preview -InstallMode Install
```

## Related Topics

* [Export-UpdatePackage](/appendix/packaging/export-updatepackage.md)
* [Get-UpdatePackageDiff](/appendix/packaging/get-updatepackagediff.md)
* <https://github.com/SitecorePowerShell/Console/>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.sitecorepowershell.com/appendix/packaging/install-updatepackage.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.