> 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/9.3-install/pentaho-installation-overview-cp/manual-installation/manual-installation-process/prepare-your-windows-environment-for-a-manual-installation/download-and-unpack-installation-files/step-3-unpack-the-plugin-files-reuse.md).

# Step 3: Unpack the plugin files

Since the plugin files are package files, they must be unpacked.

1. Unzip the plugin file you would like to install. Inside is the packaged file.
2. Run the `install.bat` file to unpack the plugin file.

   The IZPak window appears.
3. Read the license agreement in the IZPack window.
   1. Select the **I accept the terms of this license agreement** check box
   2. Click **Next**.
4. In the **Select the installation path** text box, browse to or enter the directory where you created the `\pentaho\server\pentaho-server\pentaho-solutions\system` directory, and then click **Next**.

   A warning message appears informing you that the directory already exists.
5. Click **Yes**.

   Any existing files in the directory will be retained.
6. Click **Done** when the installation progress is complete.


---

# 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/9.3-install/pentaho-installation-overview-cp/manual-installation/manual-installation-process/prepare-your-windows-environment-for-a-manual-installation/download-and-unpack-installation-files/step-3-unpack-the-plugin-files-reuse.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.
