> 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/about-tab/about.md).

# About section of Patch My PC Publisher

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

The **ABOUT** section on the **About** tab of Patch My PC (PMPC) Publisher shows key version information for Publisher, allows you to restart the publishing service, and upgrade to a later version.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FI8NuJDdk1GKeoqX1J0Tl%2Fimage.png?alt=media&amp;token=7f257d0e-4f92-42a4-a184-7e31df169c51" alt="&#x27;ABOUT&#x27; section" width="563"><figcaption></figcaption></figure>

This section consists of the following fields:

## **Currently Installed Version**

Shows the version of Publisher currently installed.

## Status field

Shows the current service state of the Publishing Service, which should be **Running** during normal operation.&#x20;

## **Latest Version**

Shows the latest available version of Publisher.

## **Last Check for New Version**

Shows the last date and time that Publisher checked for a new version.

## Restart Service button

Clicking the **Restart Service** button restarts the Publishing Service and refreshes the current service state. This is useful after configuration changes or troubleshooting scenarios.

## Upgrade Now button

If a newer version of Publisher is available and assigned to your update ring, the **Upgrade Now** button is available. Patch My PC uses a ringed deployment model for Publisher, which means updates may be available on demand depending on your assigned ring.


---

# 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/about-tab/about.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.
