> 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-automate-customizations-main-folder.md).

# WinpeStartup Core: Automate Customizations Using the main Folder

Automatically include shared WinpeStartup Core customizations in each OSDeploy WinPE build.

Store shared WinPE startup customizations in the `main` folder. `Build-OSDeployBoot` includes this folder automatically when it is present, without requiring a selection in the optional WinpeStartup Core folder picker.

## Add Shared Customizations

{% 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 Your Customization Files

Copy the files WinPE should use into `main`. For example, add a `.env` file, a `.reg` file, or a root certificate in `.cer` format.

See [Add WinPE Environment Variables](https://www.osdeploy.com/osdeploy-insider/how-to/winpestartup-core-add-environment-variables.md), [Modify the WinPE Registry](https://www.osdeploy.com/osdeploy-insider/how-to/winpestartup-core-modify-winpe-registry.md), and [Import a WinPE Root Certificate](https://www.osdeploy.com/osdeploy-insider/how-to/winpestartup-core-import-root-certificate.md) for examples.
{% endstep %}

{% step %}

### Build WinPE Media

Run the build command:

```powershell
Build-OSDeployBoot
```

OSDeploy copies the shared `main` folder into `WinpeStartup\core\main` in the mounted image. Boot the resulting media to run the 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-automate-customizations-main-folder.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.
