> 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/wsus-options/update-republishing-options.md).
# Update Republishing section of Patch My PC Publisher
*Applies to: Patch My PC Publisher V3.x*
The **UPDATE REPUBLISHING** section on the **WSUS Options** tab in Patch My PC (PMPC) Publisher controls how republished third party updates are named. Republishing is required when an existing update needs to be replaced due to changes in content or metadata.
Common scenarios requiring republishing include updates where you added or modified customizations, corrected detection logic, or need to sign the update with a new code signing certificate. In general, any change that affects the update CAB file or its digital signature requires republishing the update.
{% hint style="success" %}
**Tip**
For more information on Republishing, see [Customizations](/patch-my-pc-publisher/customizations.md).
{% endhint %}
By default, when an update is republished, Publisher appends a timestamp to the update name indicating when the republish occurred. This makes it clear in the Microsoft Configuration Manager (ConfigMgr) console that the update is a republished revision and shows the exact republish date and time. The example shown in the image above demonstrates how a republished Google Chrome update would appear with this appended information.
## Do not append republished updates with a republished datetime
If the **Do not append republished updates with a republished datetime** option is enabled, the republished update keeps the original update name, and no timestamp is added.
The update is still republished and supersedes the previous revision (if that option was selected during republishing), but the name shows no visible indication that a republish occurred.
{% hint style="info" %}
**Note**
Republishing only applies to an existing update version. When an update is republished, Publisher republishes the same version and creates a new revision of that update with a new Update ID.
If an administrator attempts to republish an update and the specified version is not found, Publisher does not republish. Instead, it performs a standard publish for the newer version and treats it as a new update rather than a republished revision.
{% 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 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/wsus-options/update-republishing-options.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.
