> 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/1.1/reference/step-definitions/install-updates.md).
# Install updates
The **Install updates** step will install any needed Windows updates in the new OS, rebooting the device as required after those are installed.
If "Opt in to Microsoft Update" is checked, additional non-Windows updates will be installed. If "Install Windows Updates" is unchecked, Windows updates will not be installed (typically only useful if you only want 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're setup Group Policies for your WSUS, remember GPO does not get set when running in Setup Complete continuation method, we also have not done any testing with additional settings beyond setting the task sequence varaible. We do not support Client-Side targeting. While you might get it to work in your environment, we have not tested or plan to support additional options for WSUS.
---
# 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/1.1/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.
