# Custom Apps "File" tab

*Applies to: Patch My PC Cloud Custom Apps*

The **File** tab of the Patch My PC (PMPC) Cloud Custom Apps Deployment wizard lets you configure various settings for the Custom App you are creating.

To configure the **File** tab:

1. Select the relevant type of installer for this Custom App:
   1. **Installer File –** Select this option (selected by default) if the installation will be based on an installer file. Proceed to the [Add the Primary Install File](#add-the-primary-install-file) section.
   2. **Installation Script –** If the installation will be controlled based on a script, select this item and proceed to the [Add the Installation Script](#add-the-installation-script) section.

{% hint style="danger" %}
**Important**

The **Installer Type** feature is a pre-release feature still under development and, therefore, incomplete. As a result, both functionality and documentation are subject to change.

 Once this feature is released, it will be announced, and this banner will be removed.

 Also, changing the **Installer Type** will reset all of the settings in the Custom Apps Deployment Wizard.
{% endhint %}

<figure><img src="/files/ZJvqgSCQIYVVkwgUEn5p" alt="‘Installer Type’" width="563"><figcaption></figcaption></figure>

{% hint style="info" %}
**Note**

Scripts will be run in the same context as the application.

Also, we currently support the following script types:

* .BAT
* .CMD
* .PS1
* .VBS
  {% endhint %}

{% hint style="danger" %}
**Important**

Currently, Pre and Post scripts containing "`${env:ProgramFiles(x86)}`" or "${env:ProgramFiles}" cannot be uploaded as Cloudflare is falsely identifying them as a false positive related to Log4j exploits. We are actively working with them to resolve this, but as this is outside our control, we cannot provide an estimated resolution time.

To work around this issue, see the [Resolution](/patch-my-pc-cloud/troubleshoot/deployments/typeerror-failed-to-fetch-error-when-trying-to-upload-a-pre-or-post-script-in-cloud.md#resolution) section of ["TypeError: Failed to fetch" error when trying to upload a Pre or Post Script](/patch-my-pc-cloud/troubleshoot/deployments/typeerror-failed-to-fetch-error-when-trying-to-upload-a-pre-or-post-script-in-cloud.md).&#x20;
{% endhint %}

## Add the Primary Install File

To add the primary installer for a Custom App:

1. On the **File** page, either:
   1. Click **Add Primary Install File** and browse to the location containing the app’s installer (EXE or MSI).
   2. Drag and drop the installer file onto this page.

{% hint style="danger" %}
**Important**

We do not support macOS in Custom Apps. If you select a .pkg/.dmg you will see a warning stating this and explaining how you can upvote this idea.
{% endhint %}

<figure><img src="/files/QaprzHjz3Tfaw2E9KeG6" alt="Clicking ‘Add Primary Install File’" width="563"><figcaption></figcaption></figure>

{% hint style="success" %}
**Tip**

If you plan to deploy an EXE-based installer, use our free script to help you extract the required information from the registry. See [Finding properties for EXE-Based Installers](/patch-my-pc-cloud/custom-apps/custom-apps-reference/find-properties-for-exe-based-installers.md) for more information.
{% endhint %}

The hash for the file is calculated as it is uploaded to your Cloud Portal and will appear as completed once the upload has finished.

<figure><img src="/files/koXG4ClaPcNTaViRFvtW" alt="Uploading the installer" width="563"><figcaption></figcaption></figure>

2. If the installer does not require any additional folders or files, click **Next** to go to the [General Information](/patch-my-pc-cloud/custom-apps/create-a-custom-app/custom-apps-general-information-tab.md) tab. \
   \
   If the installer does require additional folders or files, go to [Add Extra Folders and Files](#add-extra-folders-and-files) .

## Add the Installation Script

To use an installation script to install the app, from the Script section, choose how you are going to add the script:

* [Import a Script](#import-a-script)
* [Add a Script Manually](#add-a-script-manually)

### Import a Script

To import an existing script:

1. Click **Import Script** and browse to the location containing the script and select&#x20;

<figure><img src="/files/2yaaHbd9HZHeoOqXBFfs" alt="Clicking ‘Import Script’" width="563"><figcaption></figcaption></figure>

The **App Installation Script** editor appears with the **Script Name** and **Script Format** fields automatically populated, and the script editor is populated with the imported script.

<figure><img src="/files/cqqf449KKTV3u1j97Bfx" alt="‘App Installation Script’" width="563"><figcaption></figcaption></figure>

{% hint style="info" %}
**Note**

If the script you are importing contains PSADT commands, we automatically detect this and update the **Script Format** to **PowerShell + PSADT**.

<img src="/files/7BhLjrfaGcVOx2fZL3FZ" alt="PowerShell and PSADT format" data-size="original">

Also, as the warning at the bottom of the script editor tells you, we do not sign scripts. If you want this script to be signed, click the **How to sign a script** link for a walkthrough.
{% endhint %}

2. Click **Save** to save the script and return to the **File** tab, where details of the script appear under the **Script** section.

<figure><img src="/files/KzcZAF9LWFrGmLiBd011" alt="Script details" width="563"><figcaption></figcaption></figure>

{% hint style="danger" %}
**Important**

If the script you imported contains PSADT commands, you will see the following warning under the **Script** section :

**PSADT functions were detected. Please ensure .NET Framework 4.7.2 or greater is installed on your device.**

As the warning states, you should ensure that .NET Framework 4.7.2 (or later) is installed on any devices to which this app will be deployed, so that it installs and functions correctly.
{% endhint %}

{% hint style="success" %}
**Tip**

You can edit the script by clicking the pencil icon or delete it by clicking the trash can.
{% endhint %}

3. If the installer does not require any additional folders or files, click **Next** to go to the [General Information](/patch-my-pc-cloud/custom-apps/create-a-custom-app/custom-apps-general-information-tab.md) tab. \
   \
   If the installer does require additional folders or files, go to [Add Extra Folders and Files](#add-extra-folders-and-files).

### Add a Script Manually&#x20;

To manually add a script:

1. Click **Add Manually**

<figure><img src="/files/qvpZxv4A8sn1mHs9Xd1U" alt="Clicking ‘Add Manually’" width="563"><figcaption></figcaption></figure>

The **App Installation Script** editor appears, prefilled with some values.

<figure><img src="/files/saZBJVbUuBX0CnwMj7yU" alt="‘App Installation Script’ editor" width="563"><figcaption></figcaption></figure>

2. If required, change the:
   1. Name of the script in the **Script Name** field.
   2. Type of script from the **Script Format** dropdown.

{% hint style="success" %}
**Tip**

You can also click **Import** to import an existing script.
{% endhint %}

3. In the script editor, type your script, then click **Save**

<figure><img src="/files/4rmmirjYTQRH1wmi80J2" alt="Entering a script and clicking ‘Save’" width="563"><figcaption></figcaption></figure>

{% hint style="info" %}
**Note**

If the enter any PSADT commands in the script editor, we automatically detect this and update the **Script Format** to **PowerShell + PSADT**.

<img src="/files/7BhLjrfaGcVOx2fZL3FZ" alt="PowerShell and PSADT format" data-size="original">

Also, as the warning at the bottom of the script editor tells you, we do not sign scripts. If you want this script to be signed, click the **How to sign a script** link for a walkthrough.
{% endhint %}

{% hint style="success" %}
**Tip**

You can also click **Export** to export this script to an external file.
{% endhint %}

The **File** tab is redisplayed, showing details of the script under the **Script** section.

<figure><img src="/files/U0LVpLqfs7W1XMGsh2Fq" alt="Script details" width="563"><figcaption></figcaption></figure>

{% hint style="danger" %}
**Important**

If your script contains PSADT commands, you will see the following warning under the **Script** section :

**PSADT functions were detected. Please ensure .NET Framework 4.7.2 or greater is installed on your device.**

As the warning states, you should ensure that .NET Framework 4.7.2 (or later) is installed on any devices to which this app will be deployed, so that it installs and functions correctly.
{% endhint %}

{% hint style="success" %}
**Tip**

You can edit the script by clicking the pencil icon or delete it by clicking the trash can.
{% endhint %}

4. If the installer does not require any additional folders or files, click **Next** to go to the [General Information](/patch-my-pc-cloud/custom-apps/create-a-custom-app/custom-apps-general-information-tab.md) tab. \
   \
   If the installer does require additional folders or files, go to [Add Extra Folders and Files](#add-extra-folders-and-files).

## Add Extra Folders and Files

{% hint style="info" %}
**Note**

Configuring Extra Folders and Files is optional, and the process is the same regardless of the **Installer Type** selected.
{% endhint %}

If the installer requires additional folders or files, either:

1. Click **Add Folder** or **Add Files** and browse to the location containing the additional folders/files\
   \
   \&#xNAN;*OR*<br>

   Drag and drop the folders/files onto this page.

{% hint style="danger" %}
**Important**

If you add any PSADT scripts to your Custom App, you need to ensure that .NET version 4.7.2 is installed on any devices to which this Custom App is deployed.
{% endhint %}

<figure><img src="/files/lSaVJuwMoOWPL5fGdXDq" alt="Adding files or folders" width="563"><figcaption></figcaption></figure>

2. Click **Next** to move to the [General Information](/patch-my-pc-cloud/custom-apps/create-a-custom-app/custom-apps-general-information-tab.md) tab.

<figure><img src="/files/4PX9yt942MjIyZs9RTFd" alt="Clicking &#x27;Next&#x27; to move to the &#x27;General Information&#x27; tab" width="563"><figcaption></figcaption></figure>


---

# 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/custom-apps/create-a-custom-app/custom-apps-file-tab.md?ask=<question>
```

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.