Startup

OSD 23.5.22.1+ Updated May 22, 2023

Every time you run Edit-OSDCloudWinPE, even to add Drivers or change the Wallpaper, the WinPE Startup will reset to the Default

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.

Edit-OSDCloudWinPE

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

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

WinPE Startup Options

These are the available WinPE Start options that you can configure

StartOSDCloudGUI

This parameter will automatically launch Start-OSDCloudGUI

Edit-OSDCloudWinPE -StartOSDCloudGUI

StartOSDCloudGUI -Brand

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

Edit-OSDCloudWinPE -StartOSDCloudGUI -Brand 'David Segura'

Edit-OSDCloudWinPE -StartOSDCloudGUI -Brand 'HP'

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:

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

StartURL

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

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.

StartOSDPad

Example coming soon

StartPSCommand

Example coming soon

Startnet

Example coming soon