> 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/fundamentals/how-publisher-works.md).

# How Patch My PC Publisher Works

*Applies to: Patch My PC Publisher V3.x*

At a high level, the workflow for Patch My PC (PMPC) Publisher is:

1. Publisher downloads a [curated catalog](/patch-my-pc-publisher/security/overview.md) from Patch My PC.
2. Administrators select which products to enable.
3. During synchronization, Publisher:
   * Validates catalog integrity
   * Downloads vendor binaries
   * Verifies file hashes
   * Packages content according to customizations and platform requirements
   * Publishes to Microsoft WSUS, ConfigMgr, and/or Intune.
4. The management platform then distributes the update or application to client devices using its native mechanisms.

<figure><img src="/files/MCPu47N4tJ6nsWi3KX0b" alt="How the Publisher Works" width="563"><figcaption></figcaption></figure>

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

The Publisher is installed on a Windows device and operates within your existing infrastructure and security boundaries.

If you are solely publishing to Intune, we recommend our SaaS based solution [Patch My PC Cloud](/patch-my-pc-cloud.md).
{% endhint %}


---

# 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/fundamentals/how-publisher-works.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.