> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/unigetui/guides/install/custom-options.md).

# Install with custom options

Choose the version, architecture, install folder, scope or installer arguments for a specific app, and UniGetUI reuses them every time.

Most of the time, the defaults are fine. When they aren't, for example you need an older version, a different install folder, or an app installed for all users, you can set custom options for that app. UniGetUI saves them and reuses them each time the app is installed, updated or removed.

## Open the options of an app

1. Find the app:
   * Not installed yet: search for it in ***Discover Packages***.
   * Already installed: find it in ***Installed Packages*** or ***Software Updates***.
2. Right-click the app and choose ***Install options*** (or ***Uninstall options***, ***Update options***, depending on the page). Shortcut: <kbd>***Alt***</kbd>***+***<kbd>***Enter***</kbd>.
3. Click ***Change this and unlock***, or turn off ***Follow the default options when installing, upgrading or uninstalling this package***.
4. In ***Operation profile:***, choose which operation you're configuring: ***Install***, ***Update*** or ***Uninstall***.

## Set what you need

Options the package manager doesn't support are grayed out. The most useful ones:

<table><thead><tr><th width="250">YOU WANT TO…</th><th>WHERE</th></tr></thead><tbody><tr><td>Install a specific or pre-release version</td><td><em><strong>General</strong></em> – <em><strong>Version to install:</strong></em></td></tr><tr><td>See the installer and answer its questions</td><td><em><strong>General</strong></em> – <em><strong>Interactive installation</strong></em></td></tr><tr><td>Install for all users, or only for you</td><td><em><strong>Architecture / Location and Scope</strong></em> – <em><strong>Installation scope:</strong></em></td></tr><tr><td>Install in another folder</td><td><em><strong>Architecture / Location and Scope</strong></em> – <em><strong>Install location:</strong></em></td></tr><tr><td>Force x64, arm64…</td><td><em><strong>Architecture / Location and Scope</strong></em> – <em><strong>Architecture to install:</strong></em></td></tr><tr><td>Close an app before it's updated</td><td><em><strong>Close apps</strong></em></td></tr><tr><td>Pass silent switches or a license key to the installer</td><td><em><strong>Command-line</strong></em></td></tr><tr><td>Run a script before or after the operation</td><td><em><strong>Pre-install / Post-install</strong></em></td></tr></tbody></table>

The full list of options is in [All settings](/unigetui/reference/settings.md).

{% hint style="info" %}
Installing **for the current user only** often avoids the administrator prompt, when the app supports it.
{% endhint %}

## Check and save

1. Look at ***Command-line to run:*** at the bottom of the window. It shows exactly what UniGetUI will send to the package manager, and updates as you change options.
2. Click:
   * ***Save and close*** to keep the options for later, or
   * ***Install*** (or ***Update***, ***Uninstall***) to save them and run the operation now.

To go back to the defaults, open the options again, turn on ***Follow the default options when installing, upgrading or uninstalling this package***, then click ***Save and close***.

## Custom arguments and scripts are off by default

The ***Command-line*** and ***Pre-install / Post-install*** tabs are locked until you allow them. Malformed arguments can break an app, and a script runs with the same rights as the installer.

To unlock them, click ***Go to UniGetUI security settings*** in the tab, then, under ***Restrictions on package operations***:

* turn on ***Allow custom command-line arguments*** for the ***Command-line*** tab;
* turn on the second setting for pre-install and post-install commands.

{% hint style="warning" %}
The setting that allows pre-install and post-install commands is currently labeled ***Ignore custom pre-install and post-install commands when importing packages from a bundle***. Despite its name, turning it on **allows** the commands. It's the one right below ***Allow custom command-line arguments***.
{% endhint %}

{% hint style="danger" %}
Only add arguments or commands you understand. They can do anything the installer can, including with administrator rights.
{% endhint %}

## Good to know

* **Same options for every app of a package manager?** Click ***Change default options*** in the options window to set them once, for all apps of that package manager.
* **The options travel with bundles.** When you add an app to a bundle, its options go with it. See [Create a bundle of your apps](/unigetui/guides/new-computer/create-a-bundle.md).
* **The operation fails after a change.** Compare ***Command-line to run:*** with the publisher's documentation, then see [An update or installation fails](/unigetui/help/troubleshooting/update-or-install-fails.md).
* **Want to lock these settings for your users?** See [Lock down risky settings](/unigetui/for-it-teams/organization/restrict-settings.md).


---

# 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.devolutions.net/unigetui/guides/install/custom-options.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.