> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/install/10.2-install/pentaho-upgrade-cp/using-the-pentaho-upgrade-installer-in-silent-mode-cp/using-silent-mode-to-upgrade-pentaho-products/use-silent-mode-to-upgrade-archive-installation-pentaho-upgrade-installer-silent-mode.md).

# Use silent mode to upgrade archive installation

To upgrade an archive installation without using a graphical interface, use the Pentaho Upgrade Installer in silent mode from a command line.

Perform the following steps to upgrade an archive installation in silent mode:

1. Exit out of any Pentaho products you are currently running.

   If you are upgrading your Pentaho Server, stop the server. For instructions on stopping the server, see [Stop and start the Pentaho Server and repository](/install/10.2-install/pentaho-configuration/tasks-to-be-performed-by-an-it-administrator/configure-the-pentaho-server/stop-and-start-the-pentaho-server-and-repository.md).
2. At the command line, enter one of the following commands to run the installer and start the upgrade process:

   * **Linux**

     `./pentaho-update-<version>.bin -i silent -DEULA=true -DUSER_INSTALL_DIR=<dir> -DHASH_FILE_ZIP=installer-hash-files-<version>.zip`
   * **Windows**

     `pentaho-update-<version>.exe -i silent -DEULA=true -DUSER_INSTALL_DIR=<dir> -DHASH_FILE_ZIP=installer-hash-files-<version>.zip`

   When the server upgrade process is complete, the console displays an [exit code](/install/10.2-install/pentaho-upgrade-cp/using-the-pentaho-upgrade-installer-in-silent-mode-cp/exit-codes-pentaho-upgrade-installer-silent-mode.md).
3. If any errors occur, review the log file generated by the installer.

   The default location of the log file is `<*root installation directory*>/*Pentaho\_\_Installation*/logs`.
4. If you are upgrading your Pentaho Server, restart the server.

   For instructions on starting the server, see [Stop and start the Pentaho Server and repository](/install/10.2-install/pentaho-configuration/tasks-to-be-performed-by-an-it-administrator/configure-the-pentaho-server/stop-and-start-the-pentaho-server-and-repository.md).

After upgrading your Pentaho products to version 10.2, complete the [Post-upgrade tasks](/install/10.2-install/pentaho-upgrade-cp/post-upgrade-tasks-pentaho-ugrade-cp.md) to verify that your Pentaho configuration is ready to use.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pentaho.com/install/10.2-install/pentaho-upgrade-cp/using-the-pentaho-upgrade-installer-in-silent-mode-cp/using-silent-mode-to-upgrade-pentaho-products/use-silent-mode-to-upgrade-archive-installation-pentaho-upgrade-installer-silent-mode.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.