> 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-create-profile-for-build-osdeployboot.md).

# WinpeStartup Core: Create a New Core Profile for Build-OSDeployBoot

Create an optional WinpeStartup Core profile folder that can be selected when building WinPE media.

Create a named folder under `winpestartup-core` when a customization should be optional. `Build-OSDeployBoot` displays every folder not named `main` in the WinpeStartup Core selection window.

## Create and Select the Core Profile

{% stepper %}
{% step %}

### Create the Profile Folder

Choose a descriptive folder name. This example creates a profile named `Contoso`:

```powershell
$CoreProfile = Join-Path $env:ProgramData `
    'OSDeployCore\boot-assets\winpestartup-core\Contoso'

New-Item -Path $CoreProfile -ItemType Directory -Force | Out-Null
```

Do not name the folder `main`. The `main` folder is included automatically and does not appear in the selection window.
{% endstep %}

{% step %}

### Add the Customization Files

Add the files required by this profile. For example, create an environment variable:

```powershell
@'
CONTOSO_SITE=BranchOffice
'@ | Set-Content -LiteralPath (Join-Path $CoreProfile '.env') -Encoding utf8
```

The folder can also contain `.reg` registry files and trusted root certificates in `.cer` format.
{% endstep %}

{% step %}

### Select the Profile During the Build

Start an interactive build:

```powershell
Build-OSDeployBoot
```

In the **Select WinpeStartup Core folders to add to this boot image** window, select `Contoso`, then complete the remaining build prompts. You can select more than one Core profile or cancel to skip all optional profiles.

OSDeploy copies the selected folder to `WinpeStartup\core\Contoso` in the mounted image. Boot the resulting media to run the selected customizations.
{% 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-create-profile-for-build-osdeployboot.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.
