> 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-conflicting-processes/overview-guidance.md).
# Overview and Guidance on Managing Conflicting Processes 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: WSUS Updates, ConfigMgr Apps, Intune Apps, Intune Updates*
The **Manage Conflicting Processes** right-click option in Patch My PC (PMPC) Publisher is used to handle scenarios in which an application being updated is currently running on an end-user device. Some third party updates require the application to be closed before the installer can run successfully.
This option allows you to define which running processes should be detected and how Patch My PC ScriptRunner (which manages the installation), should respond when those processes are found during installation.
## Guidance
Products shown in the Product Tree with a blue cross icon () indicate that the application must be closed before updating.
PMPC has identified that these applications cannot be reliably updated whilst running.
For these products, Publisher's default behavior is to configure conflicting processes to [Skip installation when conflicting processes are in use](/patch-my-pc-publisher/customizations/list-customizations/manage-conflicting-processes/policy-section.md#skip-installation-when-conflicting-processes-are-in-use).
This prevents installation failures when the application is open. The update will retry at the next configured retry interval, which differs between Microsoft ConfigMgr and Intune update workflows.
For many organizations, a better compromise for these applications is to configure [Notify the user to close the application](/patch-my-pc-publisher/customizations/list-customizations/manage-conflicting-processes/policy-section.md#notify-the-user-to-close-the-application) and allow the user to [defer the installation](/patch-my-pc-publisher/customizations/list-customizations/manage-conflicting-processes/notification-policy.md#defer-snooze-policy) a limited number of times.
This approach balances application compliance with a positive end-user experience by allowing users time to close the application and save work.
When the notification is presented to the end user, the available actions control how the update proceeds.
Selecting **Close All and Install** immediately closes the defined [conflicting processes](/patch-my-pc-publisher/customizations/list-customizations/manage-conflicting-processes/management-options.md#manage-process-list) and starts the update installation.
{% hint style="danger" %}
**Important**
If an application is closed by this process, it is not automatically reopened after the update completes. Application relaunch behavior depends on the application itself or user action.
{% endhint %}
Selecting **Snooze Install** records a deferral for the installation. The update does not run at that time and is retried during the next evaluation cycle based on the configured [deferral policy](/patch-my-pc-publisher/customizations/list-customizations/manage-conflicting-processes/notification-policy.md#defer-snooze-policy) and deployment platform.
## Applications that require closing during updates
See [Manage Conflicting Processes when Updating Third-Party Applications](https://patchmypc.com/kb/manage-conflicting-processes-when-updating) for a list we maintain of applications that should be closed during updates.
---
# 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-conflicting-processes/overview-guidance.md?ask=&goal=
```
`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.