How to add your own scripts to WinPE

You can add your own scripts to the PE system by modifying one of the Startnet.cmd, Unattend.xml, and Winpeshl.ini files. We can create custom Winpeshl.ini files so that we can run our own applications. Now follow the actual combat.

Before adding any custom scripts to PE, you must first load the basic WinPE image (Winpe.wim) with the ImageX tool.

First, add custom scripts using Startnet.cmd, and use Startnet.cmd to add custom command-line scripts in WinPE. By default, WinPE includes the Startnet.cmd script, which is located in the%systemroot%system32 of the WinPE image. Currently, Startnet.cmd starts Wpeinit.exe. The Wpeinit.exe is used to install Plug and Play (PNP) devices, handle Unattend.xml settings, and load network resources. Edit the Startnet.cmd to include the custom commands.

Note: For PNP and network support, make sure that you include a call to Wpeinit in your custom Startnet.cmd script.

Second, run Imagex/info d:boot.wim to view information about the WinPE image. We should pay attention to this line:

Image Count:2

Description This WinPE image file contains two images in fact. Detailed information about each image is shown later in detail. Specifically, what we need to edit here is the second image called WDS, because WDS uses this image to boot the computer.

Use the ImageX command plus parameter mountrw to load *.wim into the Pemount directory first:

IMAGEX/MOUNTRW C:winpe2pe2.wim 2 C:pemount

Use the peimg command to add third-party drivers to WinPE 2.0, and repeat this step if you need to add multiple device drivers.

Peimg/inf=c:winpe2netdrvxxx.inf c:pemountwindows

Use the ImageX command to add parameters unmount and commit to write the modifications to *.wim

Imagex/unmount C:pemount/commit

Third, use Winpeshl.ini to add your own script, you can use a file named Winpeshl.ini to launch the custom application. Winpeshl.exe will process the statements in Winpeshl.ini during startup. Use a text editor, such as Notepad, to write a winpeshl.ini text file with the following structure. For example:

[Launchapp]

AppPath =%systemdrive%myshell.exe

[Launchapps]

%systemdrive%mydirapplication1.exe,-option1-option2

Application2.exe,-option1-option2

Note: Write the AppPath entry to the application's path. This path can be an absolute path, or you can use environment variables, such as%systemroot%system32myshell.exe. The AppPath item does not support command-line options. Save this file to the%systemroot%system32 of the WinPE image.