> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/deployr/whats-new-and-upgrades/updating-deployr-community.md).

# Updating DeployR Community

New DeployR Community releases will periodically be released with fixes and additional features.  The installation process for these follows the same basic steps as a new installation:

* Download the latest DeployR Community .zip file from <https://releases.2pintsoftware.com>.  Extract the .exe file from the .zip and run it elevated.
* Since everything is already configured, fewer questions will be asked.  Any updates needed to the Microsoft dependencies will be automatically downloaded and installed, and then any new 2Pint Software product versions will be installed.

After upgrading, it is recommended to regenerate the Windows PE boot images and update any boot media that you may have previously created.  Also, refresh the Dashboard web site using Control-F5 to ensure that the latest version is being used.


---

# 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://documentation.2pintsoftware.com/deployr/whats-new-and-upgrades/updating-deployr-community.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.
