Boot Image File For Windows 10

[Armonia Bunda]

Atfirst, I thought I could easily download one of the millions of boot images from the web. But after two hours of searching the web, I have not found anything I could use. Well, I found only one site that had it and my anti-virus program warned me not to go to that site.

I then tried to extract the boot image from an existing ISO file using WinISO. However, WinISO can only extract it from a physical CD/DVD. What I have here is the Windows 10 ISO file (64 bit, version 1909) which is more than 5 GB (5,294,394 Kb) and cannot fit on a single layer DVD-5 (4.7 GB). Therefore, I cannot burn the ISO file to a DVD in order for WinISO to extract the boot image (unless I have a double layer blank DVD-9 (8.5 GB) disc). I guess the programmers of WinISO didn't expect people to extract boot image from existing ISO files.

A boot image in Configuration Manager is a Windows PE (WinPE) image that's used during an OS deployment. Boot images are used to start a computer in WinPE. This minimal OS contains limited components and services. Configuration Manager uses WinPE to prepare the destination computer for Windows installation.

Configuration Manager provides two default boot images: One to support x86 platforms and one to support x64 platforms. These images are stored in the x64 or i386 folders in the following share on the site server: \\\SMS_\osd\boot\. The default boot images are updated or regenerated depending on the action that you take.

The Configuration Manager log tool (CMTrace) is added to all boot images in the Software Library. When you're in Windows PE, start the tool by typing cmtrace from the command prompt.

When you upgrade the Windows Assessment and Deployment Kit (ADK) version, and then use updates and servicing to install the latest version of Configuration Manager, the site regenerates the default boot images. This update includes the new WinPE version from the updated Windows ADK, the new version of the Configuration Manager client, drivers, and customizations. The site doesn't modify custom boot images.

The site always uses the production version of the Configuration Manager client in default boot images. Even if you configure automatic client upgrades to use a pre-production collection, that feature doesn't apply to boot images.

When you upgrade Configuration Manager 2012 to current branch, the site regenerates the default boot images. This update includes the new WinPE version from the updated Windows ADK and the new version of the Configuration Manager client. All boot image customizations remain unchanged. The site doesn't modify custom boot images.

When you use the Update Distribution Points action from the Boot Images node in the console, the site updates the target boot image with the client components, drivers, and customizations.

You can reload the boot image with the latest version of WinPE from the Windows ADK installation directory. The General page of the Update Distribution Points wizard provides the following information:

This action is available for both default and custom boot images. During this process to reload the boot image, the site doesn't retain any manual customizations made outside of Configuration Manager. These customizations include third-party extensions. This option rebuilds the boot image using the latest version of WinPE and the latest client version. Only the configurations that you specify on the properties of the boot image are reapplied.

After you update the Windows ADK on the site server, the console won't immediately show the new version. If you use one these actions to update a boot image, the site uses the latest ADK version. To get the console to display the current ADK version, restart the WMI service. For more information, see Starting and Stopping the WMI Service.

When a boot image is based on the WinPE version from the supported version of the Windows ADK, you can customize or modify a boot image from the console. When you upgrade a site and install a new version of the Windows ADK, custom boot images aren't updated with the new version of Windows ADK. When that happens, you can't customize the boot images in the Configuration Manager console. However, they continue to work as they did before the upgrade.

When a boot image is based on a different version of the Windows ADK installed on a site, you must customize the boot images. Use another method to customize these boot images, such as using the Deployment Image Servicing and Management (DISM) command-line tool. DISM is part of the Windows ADK. For more information, see Customize boot images.

During site installation, Configuration Manager automatically adds boot images that are based on a WinPE version from the supported version of the Windows ADK. Depending on the version of Configuration Manager, you can add boot images based on a different WinPE version from the supported version the Windows ADK. An error occurs when you try to add a boot image that contains an unsupported version of WinPE.

Configuration Manager also supports Windows PE versions for boot images that aren't customizable from the Configuration Manager console. For example, you install the Windows ADK and WinPE add-on for Windows 11 on the site server. For x64 boot images based on WinPE version 11 from the WinPE add-on for Windows 11, you can customize them from the Configuration Manager console. However, while x86 boot images based on WinPE version 10 are supported, you need to manually customize them from a different computer. Use the version of DISM that's installed with the Windows ADK for Windows 10. Then, you can add the boot image to the Configuration Manager console.

In the Boot Image node of the console, the Size (KB) column displays the decompressed size for each boot image. When the site sends a boot image over the network, it sends a compressed copy. This copy is typically smaller than the size listed in the Size (KB) column.

Boot images are distributed to distribution points in the same way as you distribute other content. Before you deploy an OS or create media, distribute the boot image to at least one distribution point.

Add or remove device drivers to the image, or edit the properties of the boot image. The drivers that you add or remove can include network or storage drivers. Consider the following factors when you modify boot images:

After you make changes to a boot image, update the boot image on the distribution points that already have it. This process makes the most current version of the boot image available to clients. For more information, see Manage content you've distributed.

To only display drivers for the architecture of the boot image, select Hide drivers that do not match the architecture of the boot image. The architecture of the driver is based on the architecture reported in the INF from the manufacturer.

To only display storage and network drivers, select Hide drivers that are not in a storage or network class (for boot images). This option also hides other drivers that aren't typically needed for boot images, such as video or modem drivers.

Select the Enable Prestart Commands option to specify a command to run before the task sequence runs. When you enable this option, also specify the command line to run and any support files required by the command.

Add cmd /c to the start of the command line. If you don't specify cmd /c, the command won't close after it runs. The deployment continues to wait for the command to finish and won't start any other configured commands or actions.

During task sequence media creation, the wizard writes the package ID and prestart command line to the CreateTSMedia.log file. This information includes the value for any task sequence variables. This log is on the computer that runs the Configuration Manager console. Review this log file to verify the values for the task sequence variables.

Configure the Windows PE scratch space (MB), which is temporary storage (RAM drive) used by WinPE. For example, when an application is run within WinPE and needs to write temporary files, WinPE redirects the files to the scratch space in memory to simulate the presence of a hard disk. By default, this amount is 512 MB for devices with more than 1 GB of RAM, otherwise the default is 32 MB.

Select Enable command support (testing only) to open a command prompt by using the F8 key while the boot image is deployed. This option is useful for troubleshooting while you're testing your deployment. Using this setting in a production deployment isn't advised because of security concerns.

Set default keyboard layout in WinPE: Configure the default keyboard layout for a boot image. If you select a language other than en-us, Configuration Manager still includes en-us in the available input locales. On the device, the initial keyboard layout is the selected locale, but the user can switch the device to en-us if needed.

On the Optional Components tab, specify the components that are added to Windows PE for use with Configuration Manager. For more information about available optional components, see WinPE: Add packages (Optional Components Reference).

The Components list shows additional items that are added to this boot image. To add more components, select the gold asterisk. To remove a component, select it from the list, and then select the red X.

To specify that the site only distributes changed files when it updates the boot image package on the distribution point, select Enable binary differential replication (BDR). This setting minimizes the network traffic between sites. BDR is especially useful when the boot image package is large and the changes are relatively small.

If you use the boot image in a PXE-enabled deployment, select Deploy this boot image from the PXE-enabled distribution point. For more information, see Use PXE to deploy Windows over the network.

3a8082e126