> For the complete documentation index, see [llms.txt](https://docs.i3d.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.i3d.net/game-hosting/processes/index/utilitypatching.md).

# Utility patching

The ONE Game Hosting platform now has a utility patching mechanism that makes it easy for you to update builds for already running application instances. This document explains the following:

* **Before you begin: Prerequisites for the utility patch**
* **Create a utility patch job**

## Before you begin

You must have the following elements to patch a utility:

* A VM or a BM with utilities included.
* A new application build for your utility.

Once you have met the prerequisites above, you can create a patch job.

## Create a utility patch job

{% hint style="info" %}
At the moment, you cannot use the front end to create the patch job for utilities, however the API will accept it. See the [Create a patch job API documentation](/api/api_one.md#v3-patchjob) for reference.
{% endhint %}

1. Create a utility patch job.
2. Wait for the patch job to commence.
3. Your target fleet will be put into manual operational status. You cannot change this while the patch is running. The system will not touch your fleet at this point. This means the system will not add or remove new application instances, VMs, or BMs.
4. Wait for the patch job to complete.
5. Once complete, review the patching changes. You can review through the sent emails or manually checking your monitoring tools to ensure that your patch has successfully completed the changes based on your requirements.
6. After a successful review, place the fleet back in your desired operational status (Auto deployment or Auto scaling).

## Results

The patch job will download the new application build on the machine. It will slowly stop the existing application instances, replace the file, and start them again. The Game/Utility deployment template's builds will be updated to the new build as soon as the patch job completes. When you reactivate the fleet, new application instances will now use the new application build.

## Related topics

* [Patching process](/game-hosting/processes/index.md)
* [Forced Deployment](/game-hosting/processes/index/forced-deployment.md)
* [Rolling Deployment](/game-hosting/processes/index/rolling-deployment.md)
* [A/B Deployment](/game-hosting/processes/index/ab-deployment.md)


---

# 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.i3d.net/game-hosting/processes/index/utilitypatching.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.