Monthly Archives: June 2015

WinPE 5.0 GUI – Create Bootable ISO

In the post about WinPE 5.0 GUI, I’ve described the steps to build a bootable USB stick with a dual-boot WinPE 5.0 boot image. In the case that you need a dual-boot WinPE image in an environment that restrict use of USB drives, you can use Oscdimg command-line tool to create an image (.iso) file of a dual-boot WinPE 5.0, and then burn the .iso file to a CD or DVD.

Oscdimg Command-Line Tool

My assumption is that you have Windows ADK 8.1 installed, downloaded a WinPE-Plugin.zip package and run (as administrator) the PowerShell script named DualBoot-WinPE50.ps1. This script creates under WinPE-Plugin folder four subfolders: Media, Mount, WinPE50_amd64 and WinPE50_x64, see the picture here:

WinPE-PluginFolderAfter

Picture 01: content of WinPE-Plugin folder

The presence of the Media folder is important; it is the source location for our Oscdimg.exe tool.

Start command-line as administrator and make Oscdimg your current directory (e.g. cd C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\x86\Oscdimg).

Type the following command: Oscdimg -bootdata:2#p0,e,bEtfsboot.com#pEF,e,bEfisys.bin -u1 -udfver102 C:\WinPE-Plugin\Media C:\WinPE-Plugin\DualBootWinPE50.iso

OSCDimg

Picture 02: creating DualBootWinPE50.iso file

Note the syntax in this command: Oscdimg [<options>] <sourceLocation><destinationFile>

In the example above I’ve created a bootable DualBootWinPE50.iso file (use CD or DVD) for a UEFI-based or BIOS-based computer by using a multi-boot command. Note the following in the above command:

  • The bootdata option must be followed by the number of boot entries in the command (-bootdata:<number>).
  • Each multi-boot entry must be delimited by using a hash symbol (#).
  • Each option for a boot entry must be delimited by using a comma (,).
  • Each boot entry must specify the platform ID.

In addition, the C:\WinPE-Plugin\Media folder is the source location and the C:\WinPE-Plugin\DualBootWinPE50.iso is the destination file.





Please note: Although the author has made every reasonable attempt to achieve complete accuracy of the content, he assumes no responsibility for errors or omissions. Also, you should use this information as you see fit, and at your own risk.