> For the complete documentation index, see [llms.txt](https://www.osdcloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.osdcloud.com/osdcloud-v1/osdcloud/setup/osdcloud-winpe/startup.md).

# Startup

OSD 23.5.22.1+ Updated May 22, 2023

{% hint style="warning" %}
**Every time you run Edit-OSDCloudWinPE, even to add Drivers or change the Wallpaper, the WinPE Startup will reset to the Default**
{% endhint %}

## Default

The default for WinPE Startup is to open a PowerShell window.  This is the method I prefer as it gives me the flexibility to do anything I want, rather than to be locked into something specific.

```powershell
Edit-OSDCloudWinPE
```

<figure><img src="https://344220114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MVSV22dcsjKDdOxDA6n%2Fuploads%2FmIlqtaeHiOQwJqfPvVHU%2Fimage.png?alt=media&amp;token=d6289ad9-7655-4ec9-8c4f-a2e318873ba7" alt=""><figcaption></figcaption></figure>

### WinPE Startnet.cmd

This is the Startnet.cmd when using the Default WinPE Startup configuration.  This is what is edited when you make one of the changes below

```batch
@ECHO OFF
wpeinit
cd\
title OSD 23.5.21.1
PowerShell -Nol -C Initialize-OSDCloudStartnet
@ECHO OFF
start PowerShell -NoL
```

<figure><img src="https://344220114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MVSV22dcsjKDdOxDA6n%2Fuploads%2FbEHhFIKl8xFodRKacVTC%2Fimage.png?alt=media&amp;token=77bb5441-d718-42ff-8d65-1cec136008a4" alt=""><figcaption></figcaption></figure>

## WinPE Startup Options

These are the available WinPE Start options that you can configure

<figure><img src="https://344220114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MVSV22dcsjKDdOxDA6n%2Fuploads%2FqSEqzdS30MaAf76TCtBH%2Fimage.png?alt=media&amp;token=23c54853-5cea-4c3b-b77b-04f748763d63" alt=""><figcaption></figcaption></figure>

## StartOSDCloudGUI

This parameter will automatically launch **`Start-OSDCloudGUI`**

```powershell
Edit-OSDCloudWinPE -StartOSDCloudGUI
```

<figure><img src="https://344220114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MVSV22dcsjKDdOxDA6n%2Fuploads%2FBl1ZcNV7fCIqezKRkWyL%2Fimage.png?alt=media&amp;token=84e5980d-5db3-4fa5-b313-4050c47a702b" alt=""><figcaption></figcaption></figure>

## StartOSDCloudGUI -Brand

If you don't want OSDCloud displayed on the OSDCloud GUI, give it your own brand

```powershell
Edit-OSDCloudWinPE -StartOSDCloudGUI -Brand 'David Segura'
```

<figure><img src="https://344220114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MVSV22dcsjKDdOxDA6n%2Fuploads%2FFG98NZhfW6F92zzEoHpL%2Fimage.png?alt=media&amp;token=1f68923b-fc60-4c54-96f7-41855a5dc972" alt=""><figcaption></figcaption></figure>

```powershell
Edit-OSDCloudWinPE -StartOSDCloudGUI -Brand 'HP'
```

<figure><img src="https://344220114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MVSV22dcsjKDdOxDA6n%2Fuploads%2FERE1P5VH0zrKZnpOesLu%2Fimage.png?alt=media&amp;token=bd56d02a-f752-4830-a016-3da30c092aef" alt=""><figcaption></figcaption></figure>

## StartOSDCloud

Yes, WinPE can start OSDCloud (CLI) automatically using this parameter.  The value for this parameter need to be the parameters for Start-OSDCloud (CLI).  Here's an example:

{% code overflow="wrap" lineNumbers="true" fullWidth="false" %}

```powershell
Edit-OSDCloudWinPE -StartOSDCloud "-OSName 'Windows 10 21H2 x64' -OSLanguage en-us -OSEdition Pro -OSActivation Retail"
```

{% endcode %}

<figure><img src="https://344220114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MVSV22dcsjKDdOxDA6n%2Fuploads%2FSkATYvV8iLexpho5iCmh%2Fimage.png?alt=media&amp;token=5be33797-8508-4c87-a884-89c6915f139f" alt=""><figcaption></figcaption></figure>

## StartURL

Here is a cool example of putting your Command Line into a GitHub Gist

{% embed url="<https://gist.github.com/OSDeploy/a0643dd05ccc3a95eba87559e66ce397>" %}

Then use the 'view raw' URL as the value for **`StartURL`**.  This is great way to customize the launch of your WinPE, or make some last minute changes.

<figure><img src="https://344220114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MVSV22dcsjKDdOxDA6n%2Fuploads%2FSSH63bVaMBpMhPPYMuO6%2Fimage.png?alt=media&amp;token=81f9d14e-19a9-4fbc-a947-d7d80d5373d9" alt=""><figcaption></figcaption></figure>

<figure><img src="https://344220114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MVSV22dcsjKDdOxDA6n%2Fuploads%2FzTPxCaWQgJKDUeC2zoby%2Fimage.png?alt=media&amp;token=a8cbea77-1047-4800-9118-d81928ff6e76" alt=""><figcaption></figcaption></figure>

## StartOSDPad

{% hint style="info" %}
Example coming soon
{% endhint %}

## StartPSCommand

{% hint style="info" %}
Example coming soon
{% endhint %}

## Startnet

{% hint style="info" %}
Example coming soon
{% endhint %}


---

# 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.osdcloud.com/osdcloud-v1/osdcloud/setup/osdcloud-winpe/startup.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.
