> For the complete documentation index, see [llms.txt](https://www.osdeploy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.osdeploy.com/osdeploy-insider/how-to/winpestartup-core-modify-winpe-registry.md).

# WinpeStartup Core: Modify the WinPE Registry with a .reg File

Apply WinPE registry settings from a .reg file in the shared WinpeStartup Core main folder.

Add a `.reg` file to the shared WinpeStartup Core `main` folder to apply registry settings when WinPE starts.

{% hint style="warning" %}
Registry files modify the running WinPE registry. Review the keys and values before adding a `.reg` file to a build.
{% endhint %}

## Apply Registry Settings

{% stepper %}
{% step %}

### Create the main Folder

Create the shared folder on the OSDeploy build computer:

```powershell
$MainDirectory = Join-Path $env:ProgramData 'OSDeployCore\boot-assets\winpestartup-core\main'
New-Item -Path $MainDirectory -ItemType Directory -Force | Out-Null
```

{% endstep %}

{% step %}

### Add a .reg File

Create a standard Windows Registry Editor `.reg` file. This example adds a value under `HKLM\SOFTWARE\Contoso\WinPE`:

```powershell
@'
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Contoso\WinPE]
"BuildTag"="BranchOffice"
'@ | Set-Content -LiteralPath (Join-Path $MainDirectory 'Contoso.reg') -Encoding utf8
```

Replace the example key and value with the settings required by your WinPE workflow.
{% endstep %}

{% step %}

### Build WinPE Media

Run the build command. OSDeploy includes the shared `main` folder automatically when it is present:

```powershell
Build-OSDeployBoot
```

Boot the resulting media to apply the registry settings.
{% endstep %}
{% endstepper %}


---

# 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://www.osdeploy.com/osdeploy-insider/how-to/winpestartup-core-modify-winpe-registry.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.
