ApplyImage.bat
WindowsPE batch file to format and apply windows installation.
- Make a bootable WindowsPE drive.
https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/winpe-create-usb-bootable-drive - Copy Windows-Deployment folder on the USB drive.
- Copy install.wim file from Windows installation media in the sources folder and copy it to Windows-Deployment folder on the USB drive. Rename it, if needed.
Windows 10 - https://www.microsoft.com/en-ca/software-download/windows10
Windows 11 - https://www.microsoft.com/en-ca/software-download/windows11
Convert ESD to WIM - https://www.poweriso.com/tutorials/convert-esd-to-wim.htm - Boot on the WindowsPE environment.
- Find the drive letter of the USB key and start ApplyImage.bat
- Chose the .wim file you want.
- Chose index (Windows edition).
- Select disk to formate and apply windows installation.
- CompactOS (Yes or No) - https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/compact-os
- Erase all data and continue? (Yes or No)
- 15 second timeout then reboot.
You must use the Sysprep /generalize command to generalize a complete Windows installation before you can use the installation for deployment to a new computer, whether you use imaging, hard disk duplication, or another method. Moving or copying a Windows image to a different computer without running the Sysprep /generalize command is not supported.
Moving or copying a Windows image to a different PC without generalizing the PC is not supported. If the hardware is not identical, severe system problems may result.
The hardware must be connected to identical locations and must use the same drivers, and the drivers must have a consistent, unique naming scheme.
https://en.wikipedia.org/wiki/Naming_convention_(programming)
Types of problems that can occur with a hardware-configuration change Even seemingly minor changes to the hardware or hardware configuration can cause severe or easily-overlooked problems, such as the following:
-
System instability.
-
Inability to use some of the basic or extended functionality of a device.
-
Extended boot times and extended installation times.
-
Misnamed devices in the Devices and Printers folder, Device Manager, and other device-related user interfaces.
-
Severe system problems that leave the computer in a non-bootable state. For more information about which devices Windows Setup relies upon to boot, see the Hardware-configuration changes that can cause the system to fail to boot section of this whitepaper
Windows 10 and Windows 11 have tools and features that help you save disk space and optimize your image.
https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/compact-os
Choose UEFI or legacy BIOS modes when booting into Windows PE (WinPE) or Windows Setup. After Windows is installed, if you need to switch firmware modes, you may be able to use the MBR2GPT tool.
In general, install Windows using the newer UEFI mode, as it includes more security features than the legacy BIOS mode. If you're booting from a network that only supports BIOS, you'll need to boot to legacy BIOS mode.
After Windows is installed, the device boots automatically using the same mode it was installed with.
Secure boot is a security standard developed by members of the PC industry to help make sure that a device boots using only software that is trusted by the Original Equipment Manufacturer (OEM). When the PC starts, the firmware checks the signature of each piece of boot software, including UEFI firmware drivers (also known as Option ROMs), EFI applications, and the operating system. If the signatures are valid, the PC boots, and the firmware gives control to the operating system.
https://docs.microsoft.com/fr-ca/windows-hardware/design/device-experiences/oem-secure-boot
https://docs.microsoft.com/fr-ca/windows/threat-protection/secure-the-windows-10-boot-process
The disk partition for Windows RE tools must be at least 300 MB. Typically, between 250-300 MB is allocated for the Windows RE tools image (Winre.wim), depending on base language and added customizations.
The allocation for Windows RE must also include sufficient free space for backup utilities to capture the partition. Follow these guidelines to create the partition:
If the partition is smaller than 500 MB, it must have at least 50 MB of free space.
If the partition is 500 MB or larger, it must have at least 320 MB of free space.
If the partition is larger than 1 GB, it must have at least 1 GB free of free space.
This partition must use the following Type ID: DE94BBA4-06D1-4D40-A16A-BFD50179D6AC
The Windows RE tools should be in a partition that's separate from the Windows partition. This separation supports automatic failover and the startup of partitions that are encrypted by using Windows BitLocker Drive Encryption.
By adding those following commande to the WinPE Startup Scripts(startnet.cmd), when the USB key will boot on the WinPE environement the command will search for the folder 'Windows-Deployment', and will start ApplyImage.bat in the Windows-Deployment folder on the USB key.
for %%p in (A B C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %%p:\Windows-Deployment set drive=%%p
echo The USB drive is on letter %drive%
call %drive%:\Windows-Deployment\ApplyImage.bat
WinPE optional components are included in the the WinPE add-ons for the Windows Assessment and Deployment kit (ADK).
Optional components are available in Amd64 and Arm64 architectures. The OCs you add to your WinPE image must be from the same ADK build and have the same architecture as your WinPE image. You can find WinPE optional components in the following locations after you install the Windows PE add-ons for the ADK:
Amd64 C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs
Arm64 C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\arm64\WinPE_OCs\
-
Add drivers to your Windows image
https://docs.microsoft.com/fr-ca/windows-hardware/manufacture/desktop/oem-deployment-of-windows-10-for-desktop-editions#add-drivers-to-your-windows-image -
Add a license agreement and info file
https://docs.microsoft.com/fr-ca/windows-hardware/manufacture/desktop/oem-deployment-of-windows-10-for-desktop-editions#add-drivers-to-your-windows-image -
Customize Windows with an answer file
https://docs.microsoft.com/fr-ca/windows-hardware/manufacture/desktop/oem-deployment-of-windows-10-for-desktop-editions#customize-windows-with-an-answer-file