> 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/reboot.md).
# Reboot
The **Reboot** step restarts the computer after the specified delay and can display a message to the end user.
### Options
| Option | Description |
| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Reboot target | **Reboot to the installed OS** (default) or **Reboot to Windows PE**. Rebooting to Windows PE is only supported from the full OS; BitLocker is suspended and the DeployR Windows PE boot image is downloaded first. |
| Reboot message | Optional message to show before restarting. |
| Reboot delay | Number of seconds to wait before restarting. Default: `0`. |
| Wait for peering in Windows PE before rebooting | See below. Default: `false`. |
### Wait for peering
Starting with DeployR 1.4, the **Wait for peering in Windows PE before rebooting** option delays the restart until no other computers are downloading content from this one. When a device boots Windows PE with BranchCache peering, other devices can download content from it over port 1337. Turning this option on prevents those downloads from being interrupted by the reboot. The step checks for active connections to port 1337 every 10 seconds and restarts once there are none.
This option only applies when the step runs in Windows PE. Default: `false`.
---
# 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/reboot.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.
