> 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-right-click-options/add-the-executable-name-s-in-the-deployment-types-install-behavior.md).

# Add the Executable Name(s) in the Deployment Type’s Install Behavior

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

## Overview

The **Add the Executable Name(s) in the Deployment Type’s Install Behavior** option allows the Publisher to define which running processes must be closed for a ConfigMgr application installation to succeed. 

<figure><img src="/files/abrhSrWX1faRAcCFp3pa" alt="Add the Executable Name(s) in the Deployment Type’s Install Behavior" width="563"><figcaption></figcaption></figure>

These executables are applied to the deployment type’s **Install Behavior** settings and control how ConfigMgr responds when an application is in use during an install.

<figure><img src="/files/MkMFUQRKgFJLGgn8buGR" alt="Install Behavior" width="476"><figcaption></figcaption></figure>

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

We strongly recommend using the [Manage Conflicting Processes](/patch-my-pc-publisher/customizations-right-click-options/manage-conflicting-processes.md) right-click option to notify users about running applications. That option provides greater flexibility and control, allowing for a smoother and more predictable user experience during installations and updates.
{% endhint %}

## Deployment Behavior

### Available Deployments&#xD;

If any of the specified executables are running when the user initiates the installation from Software Center, the installation will fail.&#x20;

<figure><img src="/files/Vs7WNF4WJy1Oy7voBgj0" alt="Available Deployments" width="563"><figcaption></figcaption></figure>

The user is notified and must close the application before retrying the install.

<figure><img src="/files/RTW8WESVqHSwkhvXNeSq" alt="Install Behavior User Notification from the Software Center" width="473"><figcaption></figcaption></figure>

### Required Deployments&#xD;

If the executable remains running, the required installation will fail. If an installation fails due to a running executable, the failure reason can be reviewed in **CIAgent.log** on the client device.

<figure><img src="/files/UuT34FouoZzy0Fs1D4q0" alt="Install Behavior failure in CIAgent.log" width="563"><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-right-click-options/add-the-executable-name-s-in-the-deployment-types-install-behavior.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.