> 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/troubleshooting/task-sequence-debugging.md).

# Task Sequence debugging

### Setting Debug in Bootstrap file

The Bootstrap file lets you configure several task sequence options: automatically start a specific task sequence (by setting the TSID variable), pass in variables, or enable debug mode. When debug mode is enabled, a minimized PowerShell console opens as soon as WinPE boots, before you select a task sequence. This lets you access tools or other utilities embedded in your WinPE image.

The Bootstrap file is injected into WinPE when the boot image is generated. Therefore, you must regenerate the boot image whenever you change `bootstrap.json`. The Bootstrap file is located here:\
"C:\Program Files\2Pint Software\DeployR\Client\Bootstrap.json"

Update your bootstrap.json file to include:

```
"Debug":"true"
```

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

### Launching TS Menu in Dev mode | Debug mode

Before selecting a task sequence, click in the upper-right corner to reveal the hidden **Dev mode** button. When in Dev mode, task sequences that you have set to development will be available to run in the drop-down menu, shown in italics. This allows you as the DeployR admin to create development task sequences and test without having them automatically show up in your list for admins to select.

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

When the Dev button is blue, the additional task sequences will be displayed in the list:

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

When Debug mode is enabled (the icon is blue instead of gray or hidden), it will start the task sequence paused, so you can poke around before the task sequence kicks off.

### Using the Tool Menu in the Progress UI

The menu is available by clicking the two parallel lines, which resemble an equals sign (=), just past the "Close" button. Four options are available:

* PowerShell
* Command Prompt
* Event Viewer (does not work in WinPE)
* Registry Editor

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

### Using the Pause Button in the Progress UI

To pause the task sequence, press the Pause button in the progress UI. The current step completes, and then the task sequence pauses before continuing to the next step.

### Adding a Pause Step in your Task Sequence

To add a pause step to the task sequence, add a "Run PowerShell" step, and set it to:

```powershell
Wait-Debugger
```

When the task sequence gets to this step, it pauses the same way as if the Pause button was pressed.


---

# 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/troubleshooting/task-sequence-debugging.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.