AutounattendGUI

A setup script for OSDCloud that automates its configuration, embeds custom scripts to inject an Autounattend.xml file into the Windows installation, and adds enhancements to the overall OSDCloud deployment process.

Warning

This is designed to be used with Ventoy, the bootable flash drive swiss army knife. Please have a Ventoy flash drive prepared.

• https://www.osdcloud.com
• https://www.ventoy.net

Special thanks to the NinjaOne Community, some of the script functions and techniques are from the awesome people over there who were oh-so-patient with me learning PowerShell over the last year or so!

Important

Please read through this entire README before starting. This helps cut down on confusion and misunderstanding.

Table of Contents

• AutounattendGUI
  • Table of Contents
• Build
  • Script Options
  • Setup
    • ADK
    • Git
    • Settings.json
    • Setup-AutounattendGUI.ps1
  • Prepare Files
  • Build-AutounattendGUI.ps1
• Install
  • New Ventoy Drive
  • Custom/Existing Ventoy Setup
• Usage
  • Internet
  • GUI
  • Confirmation
• Troubleshooting
  • Missing Menu Options

---

Build

Script Options

The two main scripts are:

1. Setup-autounattendGUI.ps1 — Prepares the build environment.
2. Build-AutounattendGUI.ps1 — Builds or updates the .wim file.

Both Setup-AutounattendGUI.ps1 and Build-AutounattendGUI.ps1 use these same flags. Here is a breakdown of each:

Flag	Description
-WorkspacePath	The full path where OSDCloud will build its workspace and temporary files. This is where the Windows PE environment and necessary scripts are staged.
-OutPath	The path where the completed output files (including the final .wim) will be saved. Typically, this is a directory you copy to your Ventoy USB drive.
-WimName	Filename (including .wim extension) to use for the final Windows Imaging file. This is the file that will be booted by Ventoy.
-WifiProfilePath	(Optional) Path to a valid Windows Wi-Fi profile XML. Used to automatically connect to Wi-Fi from the WinPE environment.
-WallpaperPath	(Optional) Path to a .jpg image that will be used as the background wallpaper in Windows PE.
-Brand	A custom name or label that is shown in Start-OSDCloudGUI and logs. Typically set to your company or project name.
-DriverHWID	(Optional) An array of hardware IDs (e.g., VID_2357&PID_011E) that will trigger downloading and injecting specific drivers into the image.
-AutounattendXML	Full path to a valid Autounattend.xml file. This file is automatically copied and used during the OS installation process.
-GUI_JSON	Full path to a customized Start-OSDCloudGUI.json file, which sets default values for the OSDCloud GUI options.
-Language	Specifies the default language for Windows installation (e.g., en-us, de-de).
-NoUpdateConfig	When set, the script will not update or create the Settings.json file. Useful for testing temporary changes without overwriting saved configurations.
-ConfigFile	(Optional) Path to a custom JSON configuration file containing all the above options. Overrides Settings.json if both are present.
-Mode	Setting this to AIO Triggers a "All In One" build, which embeds the Start-OSDCloud.json and Autounattend.xml files into the .wim file for easy use with tools like WDS.

Each of these options (Except -NoUpdateConfig and -ConfigFile) can be passed directly to the PowerShell scripts or included in your Settings.json file for convenience and reusability.

Setup

Caution

!!!THIS MUST BE RUN ON WINDOWS 10!!!

As stated here: https://www.osdcloud.com/osdcloud/setup#machine-configuration, Windows 11's PE environment is not compatible with several key devices and drivers. To function properly, AutounattendGUI requres the latest version of Windows 10.

Warning

You must have Windows 10 version 2004 (April 2020) or newer.

ADK

First, install ADK and ADK-WinPE:

1. Go to https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install
2. MAKE SURE to use THIS version of ADK and ADK-WinPE (Download both):
   
3. Run the ADK installer first (Not ADK-WinPE). Just use the defaults till you get to the step shown below.
4. When you get to this screen, only select the option highlighted below:
   
5. Just use defaults for the rest of the installation.
6. Once the ADK is finished installing, run ADK-WinPE. Just keep all the defaults and keep pressing next.

Git

Run this in an Admin PowerShell:

git clone https://github.com/GraphicHealer/AutounattendGUI.git
cd .\AutounattendGUI\

Leave the powershell window open, you will need it later.

Settings.json

Create a folder for your build (e.g. MyOrgName\), and copy Settings.json into it, and open the copy in your favorite editor (I recommend Notepad++).

You will see this:

{
    "AutounattendXML": ".\\Build-Files\\Autounattend.xml",
    "Brand": "AutounattendGUI",
    "DriverHWID": [
        "VID_2357&PID_011E",
        "VID_17E9&PID_4307"
    ],
    "GUI_JSON": ".\\Build-Files\\Start-OSDCloudGUI.json",
    "Language": "en-us",
    "Mode": "Drive",
    "OutPath": ".\\Ventoy-Drive",
    "WallpaperPath": ".\\Build-Files\\Wallpaper.jpg",
    "WimName": "1_AutounattendGUI.wim",
    "WorkspacePath": ".\\AuGUI-Workspace"
}

Change the paths to include the new folder you setup:

{
    "AutounattendXML": ".\\MyOrgName\\Autounattend.xml",
    "Brand": "MyOrgName",
    "DriverHWID": [
        "VID_2357&PID_011E",
        "VID_17E9&PID_4307"
    ],
    "GUI_JSON": ".\\MyOrgName\\Start-OSDCloudGUI.json",
    "Language": "en-us",
    "Mode": "Drive",
    "OutPath": ".\\MyOrgName\\Ventoy-Drive",
    "WallpaperPath": ".\\Build-Files\\Wallpaper.jpg",
    "WimName": "1_AutounattendGUI.wim",
    "WorkspacePath": ".\\MyOrgName\\AuGUI-Workspace"
}

Warning

You must use double backslashes (\\) in paths. This is a JSON spec requirement.

Setup-AutounattendGUI.ps1

Switch back to the Admin Powershell you left open, and run the following:

Set-ExecutionPolicy Bypass
.\Setup-AutounattendGUI.ps1 -ConfigFile .\MyOrgName\Settings.json

This will setup your build environment.

Prepare Files

1. Generate Autounattend.xml from https://schneegans.de/windows/unattend-generator/, and copy it to .\MyOrgName\Autounattend.xml
2. Copy Start-OSDCloudGUI.json to .\MyOrgName\Start-OSDCloudGUI.json, and open it in your favorite editor. Follow this guide to set it up correctly: https://www.osdcloud.com/osdcloud-automate/osdcloudgui-defaults
3. If you setup a custom wallpaper, Copy your .jpg wallpaper file to the path in Settings.json

Build-AutounattendGUI.ps1

Go back to the Admin Powershell window you have open, and run the following (replacing MyOrgName):

.\Build-AutounattendGUI.ps1 -ConfigFile .\MyOrgName\Settings.json

Caution

DO NOT STOP THIS COMMAND! YOU MUST WAIT FOR IT TO COMPLETE! IT CAN BREAK YOUR BUILD ENVIRONMENT, REQUIRING A FULL WINDOWS REINSTALL!

---

Install

New Ventoy Drive

Warning

You will need to have wimboot mode setup on your Ventoy drive: https://www.ventoy.net/en/plugin_wimboot.html

Copy OutPath contents to your Ventoy drive’s root (e.g. D:\).

Expected structure:

D:\
  |- ventoy\
  |   |- ventoy.json
  |   `- ventoy_wimboot.img
  |- OSDCloud\
  |   |- Automate\
  |   |   |- autounattend.xml
  |   |   `- Start-OSDCloudGUI.json
  |   `- OS\
  `- 1_AutounattendGUI.wim

Custom/Existing Ventoy Setup

Caution

Only for users with existing Ventoy setups.

1. Copy only the OSDCloud\ folder to Ventoy root.
2. Do not overwrite ventoy.json if customized.
3. Refer to provided ventoy.json for merging changes.

---

Usage

Internet

If no internet is detected:

Options:

• Enter Wifi Credentials — shows if WifiProfilePath is set
• Offline Install — shows if .wim is available in OSDCloud\OS\

GUI

Edition selection defaults to current system edition (if not using Offline installer). Click Start.

Confirmation

Confirm installation disk:

Enter Y to proceed.

Windows will install with your custom Autounattend.xml and GUI settings.

---

Troubleshooting

Missing Menu Options

If Start-OSDCloudGUI.json becomes corrupted, it can disable some menu options.

To fix it:

1. Plug in your Ventoy drive to a working PC
2. Navigate to \OSDCloud\Automate\
3. Delete Start-OSDCloudGUI.json
4. Rename Start-OSDCloudGUI.json.bak to Start-OSDCloudGUI.json

This will restore functionality to OSDCloudGUI.