Skip to content Skip to main navigation Skip to footer

TBWinPE/RE Builder – Build Modes & Types

This article provides details on the different build modes and build types that can be selected in TBWinPE/RE Builder.

Build Modes

TBWinRE

Creates builds based on the Windows Recovery Environment (WinRE). WinRE is installed with Windows and does not require downloading and installing the Windows ADK/AIK.

By default, the installed WinRE determines the build's architecture and WIM version.

TBWinPE

Creates builds based on the Windows Preinstallation Environment (WinPE). For Windows 7 through Windows 10 2004, this includes both x64 (64-bit) and x86 (32-bit) build architectures. For newer Windows versions, only x64-based builds are supported (x86 architecture is not available for these versions).

The applicable Windows ADK/AIK must be downloaded and installed (or otherwise made available) to use as the source for the build. The build's architecture and WIM version is determined by the source allowing a greater range of WIM architectures and versions. For example, if you need a build that includes a program that doesn't support x64 (no 64-bit version available), using an x86 WinPE source would be an option.

Build Types

Boot Media - Create a CD, USB Flash Drive (UFD), or ISO file

Modes supported: TBWinPE, TBWinRE

This build type is used when creating CD/DVD, USB Flash Drive (UFD), or ISO file boot media. This build type is also recommended for normal builds that will be used with Builder's BootWIM feature.

Update WinRE - Modify the installed Windows Recovery Environment (WinRE)

Modes supported: TBWinRE

This build type modifies the installed Windows Recovery Environment (WinRE). WinRE is accessed from the Boot/Restart menu in Windows 8.x/10/11 or via F8 when booting Windows 7. By default, WinRE is also automatically booted when Windows fails multiple times to boot properly so repairs can be performed.

Certain build options/settings are overridden for this build type. In most cases, the WinRE Shell Link is also applied so Image for Windows will show in the Windows Recovery menu.

This build type (if current) is also a valid IFW WinRE build.

Boot File - Create boot file for use with TeraByte's BOOTFILE program

Modes supported: TBWinPE, TBWinRE

This build type creates the boot file TBwinRE.bin (for TBWinRE builds) or TBWinPE.bin (for TBWinPE builds) for use with TeraByte’s BOOTFILE program. Requires TBOSDT 1.47+ and bootfile.exe/bootfile64.exe 2.0.5 or later.

The TBOSDT BOOTFILE program can be used to set up the MBR to boot an NTFS, FAT, or FAT32 partition that is contained in a continuous file in an NTFS, FAT, or FAT32 partition.

Note: In most cases, BOOTFILE should only be used on MBR/EMBR drive types. Refer to the BOOTFILE documentation included with TBOSDT for more information on using this utility.

IFW WinRE - Create TBWinRE WIM for use with Image for Windows Reboot

Modes supported: TBWinRE

This build type updates the installed WinRE with a TBWinRE build for use with the Image for Windows Reboot feature. For example, when restoring the running Windows partition, Image for Windows can automatically create the build, reboot into it and restore the backup image, and then boot back into Windows.

Note: Both IFW WinRE and IFW BootWIM builds support the Image for Windows Reboot feature. IFW WinRE is selected by default (this can be changed in Builder's settings if IFW BootWIM is preferred).

Requirements are checked when the build is used and it will rebuild if necessary. The most common cause for a rebuild is newer program versions. A backup can be used instead of rebuilding if it exists and meets the requirements.

  • A functional WinRE is required. Since the build depends on booting into the installed WinRE, it must be in a working state. An IFW BootWIM build can be used in most cases where the installed WinRE is broken, but the WinRE WIM is available.

  • The installed WinRE is used as the source for the build (not the saved backup WIM). This allows most custom Update WinRE builds to still function normally while still providing the support IFW WinRE needs. (In some cases, the build may need to revert to using the backup WIM due to size restrictions.)

  • For plugins, the user can override including the plugin in this build type even if it's supported by the plugin.

  • Certain build options can be overridden by the user. These can be found in Builder's settings on the IFW WinRE tab.

  • The build maintains its own ifw.ini file to use specifically for IFW WinRE boots. With TBLauncher 1.37 or later, the current installed ifw.ini file will be copied into the build after booting (if found). This allows the current settings to be used while not replacing a custom build's Image for Windows settings.

  • A minimal build may be created if there is not enough free space available on the WinRE partition for a full TBWinRE build.

  • The WinRE Shell Link is not applied.

  • The build will be used by any set of Builder build files. For example, a build in the installed folder (installed with Image for Windows), a build in C:\tbwinre, and a build in D:\tbwinre would all use and manage the same IFW WinRE build at the installed WinRE location. However, in general use, you would normally want this build to be managed by the installed build.

IFW BootWIM - Create TBWinRE WIM for use with Image for Windows Reboot

Modes supported: TBWinRE

This build type is very similar to IFW WinRE. However, there are some important differences between them:

  • The installed WinRE is not updated or modified.

  • A functional WinRE is not required. However, a valid WinRE WIM file must be available to create the build. By default, the backup WinRE WIM (saved in the build's WinRE_Backup folder) is used as the source for the build.

  • The build is separate for each location of build files and resides in the build's IFW_BootWIM folder. For example, if you have a build in C:\tbwinpe and another build in D:\tbwinpe, they will each have their own IFW BootWIM build.

  • Since the build does not reside on the WinRE partition there are no size restrictions (a full build is created).

  • With the exception of the build created by the installed Builder (installed with Image for Windows), these builds will not be used by Image for Windows. They can, however, be used manually from the command line. For example, a custom build could take advantage of the ability to automatically update the build as necessary when performing the desired operations.

  • Since the WIM from this build is booted from its partition, the partition must be accessible from outside Windows or the boot will fail.

Note: Both IFW WinRE and IFW BootWIM builds support the Image for Windows Reboot feature. IFW WinRE is selected by default (this can be changed in Builder's settings if IFW BootWIM is preferred).

Was This Article Helpful?

0