OSDCloud WinPE

New-OSDCloud.winpe has been renamed to New-OSDCloudWinPE (without the period in the name). The old name is now an Alias, but that will be removed on April 1, 2022
This function requires elevated Admin Rights


You can customize your OSDCloud WinPE with the Wallpaper parameter. Make sure to pick a JPG and you are good to go
[ADMIN]: PS C:\> Edit-OSDCloudWinPE -Wallpaper "C:\Users\David\Downloads\Wallpaper.jpg"
2022-03-03-235037 Mounting C:\OSDCloud\Media\Sources\boot.wim
2022-03-03-235051 Startnet.cmd: wpeinit
2022-03-03-235051 Startnet.cmd: start PowerShell -NoL -C Start-WinREWiFi
2022-03-03-235051 Startnet.cmd: start PowerShell -NoL
2022-03-03-235051 Wallpaper: C:\Users\David\Downloads\Wallpaper.jpg
Older 93710 C:\Users\David\AppData\Local\Temp\winpe.jpg
Newer 93710 C:\Users\David\AppData\Local\Temp\winre.jpg
2022-03-03-235051 Saving OSD Module to C:\Users\David\AppData\Local\Temp\Mount1189211421\Program Files\WindowsPowerShell\Modules
2022-03-03-235119 Edit-OSDCloudWinPE Completed in 00 minutes 41 seconds


You have a few methods to get Drivers in OSDCloud WinPE. The easiest method is to use a CloudDriver


I spent some time automating the download, extraction, and injecting the drivers in WinPE. I call these CloudDrivers. For this parameter I recommend you use install everything with the following command line
Edit-OSDCloudWinPE -CloudDriver *
This will download and inject the following drivers
  • Dell Enterprise Driver Cab
  • HP WinPE 10 Driver Pack
  • Intel Ethernet Drivers
  • Lenovo Dock Drivers (Microsoft Catalog)
  • Nutanix
  • USB Dongles (Microsoft Catalog)
  • VMware (Microsoft Catalog)
  • WiFi (Intel Wireless Drivers) [Requires WinRE]
These are handled by mixing and matching the following values
Edit-OSDCloudWinPE -CloudDriver Dell,HP,IntelNet,LenovoDock,Nutanix,USB,VMware,WiFi
Here's an example using Dell, USB, and Intel WiFi
Edit-OSDCloudWinPE -CloudDriver Dell,USB,WiFi


If you have a HardwareID, you can specify that with this parameter. This will download the appropriate driver from Microsoft Catalog and inject it into WinPE. Here's an example
Edit-OSDCloudWinPE -DriverHWID 'VID_045E&PID_0927','VID_0B95&PID_7720'


Finally, you can use a Driver Path to specify a folder containing driver INF's that you want to install
Edit-OSDCloudWinPE -DriverPath 'C:\SomePath'


You can configure your OSDCloud WinPE to startup a few different ways

Command Prompt

If you never run Edit-OSDCloudWinPE, then you will have a basic WinPE that doesn't have any Drivers or Wallpaper, and PowerShell won't open automatically
To get to OSDCloud at this point, simply open PowerShell and install the OSD Module (assuming your Network Adapter works with the In-Box Drivers)

PowerShell Prompt

Running Edit-OSDCloudWinPE without any additional parameters will enable the OSDCloud WinPE Startup sequence, which modify the WinPE Startnet. This enables WiFi (if using WinRE), updates the OSD PowerShell Module, and opens a PowerShell prompt. Additionally, the OSD PowerShell Module is saved to WinPE
Once the WinPE Startup sequence is complete, simply run Start-OSDCloud or Start-OSDCloudGUI. I prefer this startup as it allows flexibility


If you want to run OSDCloudGUI automatically when WinPE starts, use the following command
Edit-OSDCloudWinPE -StartOSDCloudGUI

OSDCloudGUI Brand

If you want to add a custom Brand to OSDCloud GUI, simply add the Brand parameter
Edit-OSDCloudWinPE -StartOSDCloudGUI -Brand 'SeguraOSD'
Recast Software
OSDeploy is sponsored by Recast Software