> 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.md). # Manage 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*


Overview and Guidance Introduction to the Manage Conflicting Processes feature and general guidance
Policy section Understand and configure how Publisher handles update installation when a conflicting application process is detected on the device
Process Restart Prevention Learn how to prevent the end user from reopening the application whilst the update is in progress
Notification Policy Learn how to control how end-user notifications behave when a conflicting process is detected and the application is running
Management Options Learn how you can control which running processes are evaluated for conflicting process management and configure the notification branding
Conflicting Process UI Settings Learn how to customize the end-user notification experience shown when an application must be closed to complete an update

--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.patchmypc.com/patch-my-pc-publisher/customizations/list-customizations/manage-conflicting-processes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.