WinPE: Create a bootable USB drive. Everything you need to know to create a bootable Windows PE disk Creating a Windows PE image

There are a million scattered articles about what Windows PE is and why it is useful. There are a million ways to create this very Windows PE on the Internet. which one is the best? We will try to summarize the basic necessary information and draw conclusions in this article.

Why do you need Windows PE?

Windows PE (Windows Preinstallation Environment) - Windows preinstallation environment, with limited services, built on the regular Windows kernel. It is used to prepare your computer for Windows installation, copy a Windows image from a network file server, and run Windows installation. It is a built-in element of other installation and system recovery tools, such as Windows Setup, Windows Deployment Services (WDS), SCCM Server Operating System (OS) Deployment Tool Kit, and Windows Recovery Environment (Windows RE). Windows PE was originally created to help hardware manufacturers, system builders, and corporations boot a computer without a running operating system. Thus, PE is most often launched either from an external drive or over the network from the company’s WDS/TFTP server.

Yes, don't confuse Windows PE and Windows RE. Windows RE (Recovery Environment) is an environment for recovering Windows after a failure. However, Windows RE as a set of tools can be run from under PE. And then the thought arises: why not use PE for tasks of restoring fallen systems, integrating the necessary applications into PE? Yes, that's exactly what we need.

What tasks can we perform under it:

managing hard disk partitions using a utility Diskpart or third party tools;
Capture volumes into a WIM image using the utility ImageX and saving them to another partition of the hard drive or USB drive;
applying WIM images to a partition of an existing hard drive using the utility ImageX and its varieties;
launching automatic Windows installation using scripts and XML response files;
copying and replacing files, as well as editing the registry of the installed operating system if it does not boot;
diagnose equipment malfunctions;
fight viruses using various antivirus utilities for Windows PE.

After downloading the archive, unzip it and run the application BuilderSE.exe. Next, follow the instructions: specify the Source with the OS installation files (install.wim should be there), configure the subprojects (each has a settings page) and start building the project.

Read also the article about the new version of Windows PE used with Windows 8: Creating a bootable disk with the .NET Framework and PowerShell 3

Windows PE is the Windows Preinstallation Environment that is used to prepare for the installation of the Windows Vista, Windows Server 2008, and Windows 7 operating systems. However, you can use Windows PE to perform a variety of tasks. For example,

managing hard disk partitions using a utility or third-party tools,
Capture volumes into a WIM image using the utility ImageX and saving them to another hard drive partition or USB drive,
applying WIM images to a volume using the utility ImageX,
launching automatic installation of Windows XP, Windows Vista, Windows Server and Windows 7,
copying and replacing files, as well as editing the registry of the installed operating system if it does not boot.

Windows PE is also often used by OEMs to restore the system to factory settings using their own tools. Windows PE becomes especially valuable for diagnosing and restoring the operating system when it includes the Microsoft Diagnostics and Recovery Toolset (MSDaRT), which is included in the Desktop Optimization Pack. Unfortunately, MSDaRT for Windows Vista is only available through Software Assurance or VL/OL/EA volume licenses.

One way or another, a Windows PE disk may be useful to you for working with WIM images or restoring the operating system, so below I will look at the process of creating it using the Windows Automated Installation Kit (WAIK). The process of creating a basic Windows PE disk is quite simple - it literally takes 10 minutes.

Creating a Basic Set of Files

This article discusses how to create a disk with a 32-bit version of Windows PE. In addition, I assume that you have a folder created on your disk C:\7Work. If you are creating a 64-bit Windows PE drive and/or using a different folder, you will need to change the architecture in all commands ( x86 on amd64) and folder paths.

On the menu Start click successively All programs, Microsoft Windows AIK and - all subsequent commands will be entered into this command line window.

Note. If you are running Windows Vista or later, Windows PE Command Line Utilities should be run as administrator by right-clicking on the shortcut and selecting the item in the context menu Run as administrator. This will avoid problems with access rights to folders and files.

A basic set of files is created with one command:

Copype.cmd x86 c:\7Work\winpe_x86

After its completion in the folder winpe_x86 the structure will be created as shown in the screenshot.

Mounting a Windows PE image and working with it

To change the original Windows PE image, you need to connect it with the command

Dism /Mount-Wim /WimFile:c:\7Work\winpe_x86\winpe.wim /index:1 /MountDir:c:\7Work\winpe_x86\mount

Once you've mounted the image, you can install packages and add your own files to it.

Installing packages

Using the utility DISM You can add additional packages to the connected image that expand the capabilities of Windows PE, as well as integrate drivers for mass storage controllers. The latter may be necessary if you use controllers whose drivers are not included in Windows PE. Below is a list of packages that can be installed.

For example, if you plan to run WSH scripts on Windows PE, you should install the WinPE-Scripting-Package. This is done with one command:

Dism /image:c:\7Work\winpe_x86\mount /Add-Package /PackagePath:<путь>WinPE-Scripting-Package

The value for the /PackagePath: parameter is the full path to:

CAB or MSU file
folder with one unpacked CAB file
folder with one MSU file
folder with several CAB or MSU files

You can view the list of packages installed in the image with the command

Dism /image:c:\7Work\winpe_x86\mount\ /Get-Packages

Adding your own files

You can extend the functionality of Windows PE by adding your own files. For example, in order to be able to capture volumes into a WIM image, you need to include the utility in the disk ImageX.

You can add files either directly to the Windows PE WIM image or to the disk on which the preinstallation environment is located. I will consider the advantages and disadvantages of both methods in more detail.

Adding files to a Windows PE WIM image. In this case, the size of the Windows PE WIM image increases, which is initially about 200 MB. Since when Windows PE starts, the contents of the image are loaded entirely into the computer's RAM, the size of the WIM image should not be increased unnecessarily. The advantage of adding files to a WIM image is that the drive letter of the loaded Windows PE environment is known in advance (this is always X:\) and it is convenient to use environment variables (%SystemRoot%, %SystemDrive%, etc.). The target folder for adding files to the WIM image is winpe_x86\mount\Windows.

Adding files to disk. By adding files to disk, you avoid increasing the size of the Windows PE WIM image and save RAM when running the preinstallation environment. All your files will be available - they are included in the boot disk. The disadvantage of this approach is that the drive letter from which Windows PE is launched is unknown in advance. If desired, you can bypass this obstacle. The target folder for adding files to disk is winpe_x86\ISO- it is equivalent to the root of the boot disk (of course, you can create subfolders in it).

Let's look at an example of adding files to disk. Let's start with ImageX. Since the utility is included in WAIK, just run the command:

Xcopy "%ProgramFiles%\Windows AIK\Tools\x86\imagex.exe" c:\7Work\winpe_x86\iso\

If you plan to use the utility ImageX to capture images, you can (but not necessarily) immediately prepare a list of exceptions - files and folders that will not be included in the saved image. Create a file in any text editor Wimscript.ini and indicate in it the files and folders that you want to exclude from the image. Default ImageX uses the following exceptions:

\$ntfs.log \hiberfil.sys \pagefile.sys "\System Volume Information" \RECYCLER \Windows\CSC *.mp3 *.zip *.cab \WINDOWS\inf\*.pnf

File Wimscript.ini located in the same folder with ImageX.

To add a package manager ( PkgMgr) you need to copy the entire folder Servicing, as well as MSXML6 files:

Xcopy "%ProgramFiles%\Windows AIK\Tools\x86\Servicing" c:\7Work\winpe_x86\iso\Servicing /s xcopy %windir%\system32\msxml6*.dll c:\7Work\winpe_x86\iso\Servicing

Now let's look at an example of adding files to a Windows PE image. Let's say I want to include the Total Commander file manager in the WIM image. I copy his folder TotalCmd to the root of the folder winpe_x86\mount. This can be done manually or from the command line:

Xcopy "%ProgramFiles%\TotalCmd" c:\7Work\winpe_x86\mount\TotalCmd /s

Setting up the launch of your own applications and scripts

If this is your first time creating a Windows PE disc, you may want to skip this section so that the material doesn't seem more complicated than it actually is. Once you've successfully created your first Windows PE disk and enjoyed its magical command-line interface, you'll be able to get back to customizing how applications run.

You can run your own applications and scripts in Windows PE in a variety of ways.

startnet.cmd

File startnet.cmd located in the folder Windows\System32 mounted Windows PE image and already contains one command - wpeinit. This command is needed to initialize network support and Plug-and-Play devices. As a command line option for wpeinit.exe you can specify the path to the answer file that configures Windows PE settings, which will be discussed below. When loading Windows PE file startnet.cmd runs automatically, so it's convenient to use to run your own commands.

You can add commands to this file using standard command file syntax. For example, to launch Total Commander, which I included in the image earlier, you can add the following command:

In this example, the path to the Total Commander configuration file is specified as a command line parameter (this is described in the program help).

winpeshl.ini

The standard Windows PE shell is the command line. However, you can define your own shell using the file winpeshl.ini, specifying the batch file or program to run. The file is not included with Windows PE. It must be created in any text editor and placed in the folder Windows\System32 mounted Windows PE image. Example of program launch myshell.exe, acting as a shell, is given below.

AppPath = %SystemDrive%\myshell.exe

In this example, the program is located in the root of the mounted Windows PE image, i.e. in the root of the folder winpe_x86\mount.

Note. File not executed when running native shell startnet.cmd.

If you need network support or Plug-and-Play devices, you need to configure the command to run wpeinit. In this case, it is better to use the section, which allows you not only to execute several commands, but also to specify command line parameters for applications.

For example, launch wpeinit and the Total Commander file manager, which I included in the image earlier, can be implemented like this:

Wpeinit %SystemDrive%\TotalCmd\TOTALCMD.EXE,"I=%SystemDrive%\TotalCmd\Profiles\PE\main.ini"

Please note how in winpeshl.ini sets command line parameters for applications.

Note. Because an application launched from a file winpeshl.ini acts as a shell; closing it ends the Windows PE session.

Attention! Do not use both partitions at the same time, as in this case applications may not start. This point is not reflected in the documentation.

Answer file

You can use a response file to automate command execution in Windows PE. When Windows PE starts, it automatically searches for the file Unattend.xml in the root of the disk from which the boot was performed. Alternatively, the path to the answer file can be explicitly specified as a command line parameter as follows:

Wpeinit -unattend=<путь\ФайлОтветов.xml>

You can use synchronous commands added to the pass to run your own applications and scripts 1 windowsPE. Continuing with the example of running Total Commander, the synchronous command would look like this:

%SystemDrive%\TotalCmd\TOTALCMD.EXE "I=%SystemDrive%\TotalCmd\Profiles\PE\main.ini"

An example of a response file that runs a synchronous command can be found on the Examples page. This file can be saved with the name Unattend.xml in folder winpe_x86\ISO, and it will be recognized automatically.

This review of ways to launch your own programs can be considered complete.

Saving the Windows PE image and replacing boot.wim

After you add your own files to the Windows PE image and configure the rest of the preinstallation environment startup options, you need to save the image.

Dism /unmount-Wim /MountDir:c:\7Work\winpe_x86\mount /Commit

If you remember, all the work was done with the image winpe.wim. And for the Windows PE boot disk the file is used boot.wim, located in the folder winpe_x86\ISO\sources. Therefore it is necessary to replace the file boot.wim file winpe.wim, performing a rename.

Xcopy /y c:\7Work\winpe_x86\winpe.wim c:\7Work\winpe_x86\ISO\sources\boot.wim

You are now all set to create a bootable Windows PE disk. Your further actions depend on what type of media you choose. You can create an ISO image and burn it to a CD, or you can create a bootable USB drive.

Creating a Windows PE ISO Image

Since all the files have already been prepared, all that remains is to run the command:

Oscdimg -n -bc:\7Work\winpe_x86\etfsboot.com c:\7Work\winpe_x86\ISO c:\7Work\winpe_x86\winpe_x86.iso

Note. For the 64-bit version of Windows PE designed for Itanium (IA-64) processors, you must specify the file as the bootloader efisys.bin.

Now you can connect the image to a virtual machine and test Windows PE.

Creating a bootable Windows PE USB drive

Note. The procedure below can only be performed on Windows Vista, Windows Server 2008 and newer operating systems. This is due to the fact that in Windows XP the utility defines flash drives as removable, so they are not displayed in the list of drives. Copying the utility from Windows Vista to Windows XP does not solve the problem. If you are running Windows XP, use alternative tools (for example, the Swissknife program).

At the command prompt, enter the following commands in sequence.

Then display a list of drives.

List disk

The list and numbering of disks depends on the number of disks connected to the system. In my example, the USB drive is Disk 1. This is easy to determine by the size of the drive. The commands below perform operations on "Disk 1". You need to make changes if your USB drive has a different index.

Select disk 1

Attention! Further actions will lead to complete deletion of information on the drive you have selected.

Clean the disk.

Create a main section.

Create partition primary

The partition will take up all the disk space. If you want to create a partition of a specific size, add the parameter to the command size=N, Where N— number in megabytes. However, Windows XP and Vista see only one partition on removable USB drives and do not allow you to create others. This problem can be overcome if you need to multiboot from a USB drive, but the solution is beyond the scope of this article. Therefore, I will limit myself to referring to one of the possible solutions.

Select the first section.

Select partition 1

Make it active.

Format to FAT32.

Format fs=fat32 quick

Initialize the letter assignment.

Quit the utility.

All that remains is to copy the Windows PE files to a USB drive. All files are in the folder winpe_x86\ISO. You can copy them using Explorer or another file manager, or with the following command:

Xcopy c:\7Work\winpe_x86\iso\*.* /s /e /f K:\

In this example, the USB drive has the letter TO.

At this point, the creation of a bootable USB drive with Windows PE can be considered complete.

Useful information about Windows PE

In conclusion, I will provide a number of facts about Windows PE that you may find useful.

The original version of Windows PE takes up less than 200 MB of disk space.
The entire contents of the Windows PE image (WIM file) is loaded into RAM, i.e., a RAM disk is created. This drive is assigned a letter X. In Windows PE, this letter is equivalent to the system partition letter in Windows.
The minimum amount of RAM for a computer that boots into Windows PE is 256 MB. Preferably - at least 512 MB.
Windows PE automatically reboots after 72 hours of operation.
Settings for running Windows PE can be configured using the utility wpeutil, which is described in detail in the help documentation.
To restart a computer running Windows PE, you can use the command wpeutil reboot, and to turn off - wpeutil shutdown. In addition, closing the command line or your own shell causes a reboot.
The keyboard layout can be set using the command wpeutil SetKeyboardLayout. For example, by placing in a file startnet.cmd team wpeutil SetKeyboardLayout 0409:00000409, you will assign an English layout. This is convenient for working with the command line, since the Windows PE image supplied with the Russian WAIK has a Russian keyboard layout by default.
To run Windows PE from a USB drive, you must configure the boot device order in the BIOS so that the USB device is first in the list.
When starting Windows PE from a USB drive, you are not prompted to press any key to boot.
If you want to run Windows PE from a CD Not prompted to press any key to load, delete the file bootfix.bin from folder ISO\boot before creating an ISO image.
If your network does not use DHCP, you can use static IP addresses. For example, you can set a static address with the command: netsh int ip set address local static 10.80.10.35 255.255.255.0 10.80.10.1
You can use the net use command to map network drives: net use * \\server\share /user:mydomain\username

For more information about Windows PE, see the Windows PE User's Guide CHM help file included with

Hello friends. Many of our readers are familiar with LiveDisk, which is created using the AOMEI PE Builder program. As a tool, it is used to carry out various operations described in many articles on our site. And in There were even instructions on how to create the disc itself. From time to time, I update the ISO image of the already created such a disk as a ready-made solution for you, friends, and post it on my cloud. And so I decided to refresh it again. Relatively recently, the PE Builder program was updated to version 2.0 and acquired support for Windows 10. In this article, I propose to talk in detail about the capabilities and innovations of the program, as well as look at the process of creating a LiveDisk using its tools.

AOMEI PE Builder: what kind of program is it?

PE Builder is a free program from AOMEI, designed to promote other products of the developer company, but at the same time bringing real, undeniable benefits. Using PE Builder, a LiveDisk is created with two main AOMEI products - Backupper and Partition Assistant Standart - and some supporting tools. But the main feature of this method of obtaining self-loading software for resuscitating computers, and at the same time the reason why LiveDisk is not posted on the AOMEI website in the form of a ready-made ISO image, is the ability to add custom portable software to the disk. We, friends, will be able to assemble our own “live” disk and include in it exactly what we need - our programs, our folders and files.

The basis of the PE Builder “live” disk is the WinPE environment - a greatly stripped-down assembly of regular Windows. The program can generate WinPE from the environment of the current version of the operating system. Those. if we create a LiveDisk inside Windows 7, we get it based on a stripped-down version of System 7, and inside Windows 8.1, we get it based on a stripped-down version of 8.1.

Previously, this was the only way to create a “live” disk, and as for Windows 8.1, it, alas, worked properly only in its English edition. In PE Builder version 2.0, nothing has changed in this regard; recent tests have shown that problems with WinPE based on Russian-language Windows 8.1 remain. But the program began to support Windows 10, both as its installation environment and as the software basis for LiveDisk. So, we can choose the WinPE 10 environment as the basis of the disk, regardless of the version of the system in which we will work to create the disk - be it Windows 7 or 8.1.

The ready-made WinPE 10 environment is already downloaded from the Internet, and it is the program creators who recommend choosing it as a stable working option.

Advantages

The ability to create a LiveDisk with your own content is the main, but not the only advantage of AOMEI PE Builder. This program also:

A completely legal way to get a “live” disk. Initially, LiveDisk comes with only free software. This means that the program download site tomorrow will not be covered by Roskomnadzor or some other structure that defends the copyrights of licensed software developers.

Software that passes Secure Boot verification. When booting from AOMEI PE Builder media in the BIOS of modern devices, you do not need to disable the Secure Boot protocol, which checks the software for authenticity.

A method for creating a bootable USB flash drive that is compatible with both regular BIOS and UEFI BIOS. The PE Builder program provides three scenarios for completing the process of creating a “live” disk - packaging into an ISO image, burning an optical disk, and writing to a removable flash drive. In the latter case, a bootable flash drive is created from which you can start a computer with any type of BIOS.

A solution for owners of small flash drives. The output of the program is a small ISO file - 400-500 MB. If you do not increase this volume by adding unnecessary software and abandon the programs supplied by default, LiveDisk along with the Windows installation process can fit into a 4 GB multiboot flash drive.

Download

On the AOMEI official website, on the PE Builder download page

https://www.aomeitech.com/pe-builder.html

We will find two types of its installer: one without the AOMEI Backupper and Partition Assistant programs included in the disk, and the other with them. I will choose the latter option for downloading, since I often work with AOMEI backup and disk manager.

What else, besides these programs, is on board the LiveDisk AOMEI PE Builder?

Composition of LiveDisk

Of the standard operating system tools on board LiveDisk, we only have access to Explorer, command line and notepad. During the disk creation process, you can add the following third-party software:

Bootice boot record editor;

QtWeb Browser;

Network management program PENetwork;

Program for diagnosing computer components CPU-Z;

Recuva program for recovering data deleted after emptying the recycle bin;

Archiver 7-Zip;

Program for mounting disk images OSFMount;

Imagine Image Viewer;

Reader for PDF, ePub, DjVu, XPS, etc. Sumatra PDF formats;

File manager Q-Dir;

Everything data search engine.

When creating a disc, you can abandon any of these programs in favor of your own portable software. Well, now, friends, let's look at PE Builder in action.

Creating a LiveDisk

Launch the program, click “Next”.

In any version of Windows (and for the “Ten” this will be the only possible option), check the box to load the WinPE 10 environment. And select the bit depth - 32 or 64. Choose, friends, you need the bit depth for which you have portable software . Click “Next”.

And add portable software: click “Add files” if you need to add only EXE files, or “Add Folder” if the software is stored in folders. Using the same principle, we add regular files and folders. In my case, portable programs are located in folders.

We add several folders with portable programs one by one.

Click “Ok”.

Click “Next”.

Good afternoon, dear blog readers, we finally got around to writing the third part of the article, in which we create our own build of Windows 10. If anyone is not reading from the beginning, then I am sending you to the first part in which . I would like to note that in the first part we already installed the ADK, but since Redstone was released and Microsoft now has its own ADK for each ten, I’ll show you where and how to download the one you need, who already has it, just scroll a little lower and go to the point with WinPE.

In the second part, we anonymized all personal data in Windows 10 redstone and turned it off in OOBE (out of box experience) mode. Now you and I need to get a wim image from this virtual machine, which we will then integrate into our distribution.

To solve this problem, we need the windows adk kit for windows 10, and some of its utilities.

WinPE > a stripped-down version of the operating system from which we will boot.
ImageX > wim image capture utility

This is what it looks like in the diagram, we boot from a bootable USB flash drive or ISO with the WinPE Windows 10 environment onto our virtual machine (The one that is turned off, you may have a reference computer), and using the command line and the imageX utility, capture the wim image. This wim image will essentially be your entire system that you previously prepared to create an image with Windows 10 redstone.

You can install this distribution either on another computer or another virtual machine, not on the one we sealed

So let’s download ADK for Windows 10 with you. You can download it from the link below. Please note that you need to download it specifically for your version of the assembly.

https://developer.microsoft.com/ru-ru/windows/hardware/windows-assessment-deployment-kit

Recently we installed windows 10 redstone, its version was 1607.

As a result, you will download a small file, one and a half megabytes, this is an online installer

Run adksetup.exe and the installation wizard window for the Windows adk kit for Windows 10 opens. You can change the installation directory, or simply download it for further deployment. (Download the Windows 10 Deployment and Assessment Toolkit for installation on another computer) I leave it as is and will install it on my computer.

We say no, since there is no need to participate in the Microsoft program.

We agree to the ADK license agreement and click accept.

We select two components:

Deployment Tools
Windows PE Preinstallation Environment

Click install. Please note that you will need access to the Internet and will download about 3.5 gigabytes.

The ADK download process will begin.

Everything was working fine for me, you can now look for ADK in our launcher.

Open the start button and find this item Windows kit

Installation Manager
Deployment Tool Environment

The next step will be for you and me to create an ISO Image with Windows PE, with which we will boot onto the reference computer to create an image of the operating system.

Create winpe for windows 10

Our task is to create an ISO image containing the winPE preinstallation environment for tens; to do this, open the Deployment Tools Environment as an administrator. To do this, right-click on the shortcut, then select Advanced > Run as administrator.

Since my future assembly has x64 architecture, I enter the following command

copype amd64 c:\winpe

where c:\winpe is the folder to be created on the C: drive, and amd64 is an indication of the architecture

copype x86 c:\winpe

For 32-bit systems, the command is higher, there is the x86 parameter. As a result of executing the required command, in your winpe folder, the entire directory structure necessary to create a bootable ISO with winPE will be copied.

Going to drive C: you will see these three folders in the parent folder:

fwfiles
media
mount

Each of them has its own purpose, we will talk about this below.

Now we need to copy the necessary utilities into our winPE, go to the folder with the installed ADK.

C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools

Select the folder with your architecture, for me it is amd64. Go to the DISM folder and copy these two files from it:

dism.exe
imagex.exe

Copy path C:\winpe\media

We have already met. But we haven't covered the process of creating installation media with Windows PE. Therefore, as promised, we will try to create this very bootable Windows PE.

As I said, Windows PE is included in the Windows AIK. We will now look at creating such bootable media with Windows PE along with the ImageX utility, which allows you to capture and deploy images. And we will need this program soon.

How to create a Windows PE image?

First of all, we naturally need to install the package. If you have not changed anything, then by default it is installed in the folder " C:Program Files\Windows AIK", and if this is not the case for you, then adjust subsequent commands accordingly. We need to create a Windows PE build folder: the folder “ C:\Windows PE". You can create any other folder in any other place, it does not matter.

A message was left in the comments that if you immediately create a build folder for the Windows PE image, there may be problems when copying the build files. Unfortunately, I don’t remember whether such problems occurred, so I advise you to postpone the creation of this folder until the command to copy the Windows PE assembly files.

The main thing is not to forget to correct your addresses with those presented below. After creating the folder, open a command prompt with administrator rights and run the following commands and actions:

cd c:\program files\windows aik\tools\petools\
Thus, we went to the folder in which the files necessary to create the Windows PE image are stored
copype.cmd x86 c:\Windows PE
x86 is the architecture of this computer. Can also take values amd64 And ia64. ia64- these are computers based on processors Itanium, but you are unlikely to find one like this. Well, if you meet him, then you should recognize him. As you can see, the second path is where Windows PE is built. If you created a different folder for building Windows PE, then please adjust the path.
copy "c:\program files\windows aik\tools\x86\imagex.exe" "c:\Windows PE\iso\"
Quotes are used here because there are spaces in the directory names. If you do not use quotes, the command line will read up to the first space after the unrecognized command. In the presented case, he will say that he does not know how to respond to the command
Copy c:\program
In the team itself, you need to know that X86 here also, depending on the computer architecture, it should be (if necessary) replaced with either amd64, on either ia6 4. This command copies the program to the Windows PE build folder.

How to create an iso image of Windows PE?

The build of Windows PE ends here, all that remains is to make bootable media out of it. And for this you need to create its iso image. To do this, you need to open the menu, find Microsoft Windows AIK, select the field in this folder Deployment Tools Command Line and in the command line window that opens, enter the command:

oscdimg -n -bc:\Windows PE\etfsboot.com c:\Windows PE\iso c:\Windows PE\winpe_x86.iso

And as you can guess, in the folder C:\Windows PE there will be an iso image of Windows PE. This means that we completed the task and created a Windows PE image. Next we need Windows PE, after which you can use Windows PE.