> 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/customization/2pxe-boot-menu-configuration.md).

# 2PXE Boot Menu Configuration

DeployR Community includes 2PXE for PXE-booting Windows-based DeployR boot images (WinPE/RE x64 and ARM64). The default menu countdown is set for 10 seconds, and the default menu selection is configured to exit. These defaults can now be changed by using the 2PXE Config Editor.

**Default menu countdown:** To change the countdown, open the 2PXE Config Editor. Enable **Show advanced**, then locate the `EnableMenuCountdown` option. Change this to the desired value. A value of 30000 is equal to 30 seconds.

<figure><img src="https://content.gitbook.com/content/8m0VARX9oyZ2zXWCdPgr/blobs/4ua1yMqUdsGXBDjIcUa9/image.png" alt=""><figcaption></figcaption></figure>

**Default menu selection:** To set the DeployR boot image as the default selection, enable advanced options in the 2PXE Config Editor and locate `DefaultMenuItemId`. Find the corresponding boot image in the DeployR dashboard and copy its full GUID from the address bar. Paste this value in the DefaultMenuItemId field. When finished, click **Verify**, then click **Save**. The next PXE boot should now reflect the changes:

<figure><img src="https://content.gitbook.com/content/8m0VARX9oyZ2zXWCdPgr/blobs/gqjbaZ4WwwxlMhm4QkDR/image.png" alt=""><figcaption></figcaption></figure>


---

# 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/customization/2pxe-boot-menu-configuration.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.