> 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/reference/step-definitions/install-updates.md).
# Install updates
The **Install updates** step installs the required Windows updates in the new operating system and reboots the device as needed.
If **Opt in to Microsoft Update** is selected, additional updates for Microsoft products other than Windows are installed. If **Install Windows Updates** is not selected, Windows updates are not installed. This is typically useful only when you want to install driver updates. If "Install driver updates" is checked, any available driver updates needed on the device will also be installed.
### WSUS
In DeployR 1.1, this step will now pull from a WSUS server if you set the variable WsusServer before the step.
If you use Group Policy to configure WSUS, note that Group Policy is not applied when using the SetupComplete continuation method. Settings other than the task sequence variable have not been tested. Client-side targeting is not supported. While you might get other WSUS options to work in your environment, they have not been tested and are not supported.
---
# 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/reference/step-definitions/install-updates.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.
