> 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/manage/wsus-updates-tab.md).

# WSUS Updates tab of Patch My PC Publisher

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

The **WSUS Updates** tab in Patch My PC (PMPC) Publisher is where third-party updates are configured and customized for Microsoft Windows Server Update Services (WSUS).

<table data-view="cards"><thead><tr><th></th></tr></thead><tbody><tr><td><a href="/patch-my-pc-publisher/manage/wsus-updates-tab/overview-wsus-updates.md"><strong>Overview</strong></a><br>Explanation of what the WSUS Updates tab is used for</td></tr><tr><td><a href="/patch-my-pc-publisher/manage/wsus-updates-tab/product-tree.md"><strong>Product Tree</strong></a><br>Select, manage and customize third-party vendors and products</td></tr><tr><td><a href="/patch-my-pc-publisher/manage/wsus-updates-tab/wsus-options.md"><strong>WSUS Options</strong></a><br>More advanced options to control the publishing behaviour and manage updates in WSUS</td></tr><tr><td><a href="/patch-my-pc-publisher/manage/wsus-updates-tab/import-cve-ids.md"><strong>Import CVE IDs</strong></a><br>Learn how Publisher can bulk match CVEs against our catalog to quickly determine the status of a fix</td></tr><tr><td><a href="/patch-my-pc-publisher/manage/wsus-updates-tab/scan-configmgr.md"><strong>Scan ConfigMgr</strong></a><br>Learn how Publisher can leverage your ConfigMgr inventory to determine which third-party products are present in your environment</td></tr><tr><td><a href="/patch-my-pc-publisher/manage/wsus-updates-tab/update-manager.md"><strong>Update Manager</strong></a><br>Learn how you can see which third party updates have already been published to WSUS</td></tr></tbody></table>


---

# 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/manage/wsus-updates-tab.md?ask=<question>&goal=<user_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.
