> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/patch-my-pc-publisher/customizations/list-customizations/manage-app-experience.md).

# Manage App Experience option in Patch My PC Publisher

*Applies to: Patch My PC Publisher V3.x*\
*Available at level: All Custom Products, All Products, Vendor, Product*\
*Available on tab: ConfigMgr Apps*

The **Manage App Experience** right-click option in Patch My PC (PMPC) Publisher allows you to customize the user experience settings applied to the Microsoft ConfigMgr application deployment type created by Publisher.

These settings control how the application behaves during installation, including behavior, logon requirements, and user interaction.

When you right-click at a supported level and select **Manage App Experience**, the **Application User Experience** dialog is displayed.

<figure><img src="/files/UMhLhwDHNRdhsOgKikjc" alt="&#x27;Application User Experience&#x27; dialog" width="506"><figcaption></figcaption></figure>

## Specify user experience settings for application to inherit

This option can be configured at multiple levels.

When configured at the **All Products** or Vendor level, you can choose which specific user experience settings should be inherited by products below. This allows you to define consistent defaults across many applications whilst still allowing exceptions at the product level.

<figure><img src="/files/MFwIF52kKRmW907BnVfo" alt="Application User Experience settings when configured at a Vendor level" width="508"><figcaption></figcaption></figure>

At the Product level, all settings apply directly to that application and override inherited values.

<figure><img src="/files/UMhLhwDHNRdhsOgKikjc" alt="Application User Experience settings when configured at a Product level" width="506"><figcaption></figcaption></figure>

## Installation behavior Constraints

If an application only supports system-wide installation, the Installation behavior option is disabled. The interface prevents selecting user-based installation when the application does not support it.

<figure><img src="/files/fllug3OoPnCTSs0AZ4Qz" alt="Installation behavior for system-wide context apps" width="506"><figcaption></figcaption></figure>

For catalog applications that are user-based (identified by **User** in the product name), the following behavior applies:

* Installation behavior is fixed to user context.
* Logon requirement is fixed to require a logged-on user.

<figure><img src="/files/bFzPREUXJ11EDW5WV21f" alt="Installation behavior for user-based apps" width="507"><figcaption></figcaption></figure>

These settings are preconfigured by design, cannot be changed, and do not inherit values from the Vendor or All Products level.

## RunTime

The **RunTime** settings control how long ConfigMgr allows the application installation to run and how the installation time is communicated to users:

* **Maximum allowed run time (minutes)**\
  Defines the maximum amount of time ConfigMgr will wait for the installation to complete before marking it as failed. If the installer exceeds this time, the deployment is terminated and reported as unsuccessful.
* **Estimated installation time (minutes)**\
  Specifies the expected duration of the installation and is shown to users in the Software Center.\
  This value is informational only and does not affect enforcement or execution. It helps set user expectations during installation, particularly for longer-running installs.

<figure><img src="/files/oynYzx8qNByxDIqZ4j84" alt="RunTime settings" width="506"><figcaption></figcaption></figure>

## Restart Behavior

The **Restart Behavior** dropdown allows you to choose whether ConfigMgr should enforce a specific behavior you configure, regardless of the application's intended behavior.

If required, select the relevant option from the **Restart Behavior** dropdown.

<figure><img src="/files/iwfAVIzjr1WdAcZUhJ3h" alt="&#x27;Restart Behavior&#x27; dropdown" width="507"><figcaption></figcaption></figure>

## Reset button

The **Reset** button restores all user experience settings to PMPC recommended defaults. This is useful if custom values were applied previously and you want to return to a known good configuration.

<figure><img src="/files/dG1pEtkkPjQlzt4CrldZ" alt="&#x27;Reset&#x27; buton" width="506"><figcaption></figcaption></figure>


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.patchmypc.com/patch-my-pc-publisher/customizations/list-customizations/manage-app-experience.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.