# Using Pre-Install Scripts in a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
A *Pre-Install Script* is a script that can be run before the installer runs.
To add a Pre-Install script:
1. Click **Add** beside the **Pre-Install** option.
The **Add Pre-Install Script** page is shown, highlighting that the default **Script Format** is **.ps1**, with built-in support for PSADT functions.
2. To import an existing script, click **Import,** then browse to the location containing the script and select it.
The **Script Name** field is populated with the filename of the script selected, and the **Add Pre-Install Script** page is populated with the imported script.
3. To manually add a script, enter a unique name for the script in the **Script Name** field.
4. Select the type of script from the **Script Format** dropdown.
5. In the script editor, type your script.
{% hint style="info" %}
**Note**
We currently have a limit of 50,000 characters per script. Use the **Number of characters used** counter to keep track of the number of characters you’ve entered in the script editor.
{% endhint %}
{% hint style="success" %}
**Tip**
Under the script editor, we include example syntax to help you understand the required syntax for referencing any additional files you've uploaded, which updates depending on the **Script Format** selected.
{% endhint %}
6. In the **Arguments** field, enter any arguments you want to provide to the script.
{% hint style="success" %}
**Tip**
You can use variable names as arguments, provided they are enclosed by percentage signs (`%`). We provide common variables under this field, which you can add by clicking the plus (+) symbol or relevant variable name.
{% endhint %}
{% hint style="danger" %}
**Important**
Using script Arguments is currently unsupported when deploying an app to macOS.
Also, if you add any PSADT scripts to your deployments, you need to ensure .NET version 4.7.2 is installed on any devices to which this app will be deployed.
{% endhint %}
7. Check the **Don’t attempt software update if the pre-script returns an exit code other than 0 or 3010** checkbox if you don’t want the app to be installed if the pre-script returns an exit code other than **0** or **3010**.
If you do not check this checkbox, we will attempt to install the app regardless of the exit code returned by the pre-install script.
8. Check the **Run the pre-update script before performing any auto-close or skip process checks** checkbox if you want to run the pre-install script before the conflicting process notification is displayed (if relevant).\
\
If you do not check this checkbox, we will run the pre-install script after the conflicting process notification.
9. Click **Save** to save your script.
The **Configurations** tab is re-displayed with the name of the configured script beside it.
{% hint style="success" %}
**Tip**
You can click **Edit** to edit a script or its settings. You can also click the red “`x`” beside a script to delete it.
{% endhint %}
## Next Steps
If you do not want to configure any additional settings, click **Next** to move to the [Assignments](https://docs.patchmypc.com/patch-my-pc-cloud/deployments/deploy-app/assignments-tab) tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
---
# Agent Instructions: 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:
```
GET https://docs.patchmypc.com/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/additional-tools/scripts/pre-install-scripts.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.
