mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-20 21:03:42 +00:00
Update Boot Image with CU Article 33
This commit is contained in:
Frank Rojas
@ -85,9 +85,9 @@ Before modifying the desired boot image, make a backup copy of the boot image th
|
||||
|
||||
- For the 64-bit boot image included with the **Windows PE add-on for the Windows ADK**, the boot image is located at `C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us\winpe.wim`.
|
||||
|
||||
- For the default 64-bit boot image that is generated by **Microsoft Configuration Manager**, the boot image is located at `<ConfigMgr_Install_Directory>\OSD\boot\x64\boot.wim`. However, for **Microsoft Configuration Manager** it's recommended to modify the boot image included with the **Windows PE add-on for the Windows ADK**. For more information, see [Microsoft Configuration Manager considerations](#microsoft-configuration-manager-considerations).
|
||||
- For the default 64-bit boot image that is generated by **Microsoft Configuration Manager**, the boot image is located at `<ConfigMgr_Install_Directory>\OSD\boot\x64\boot.wim`. However, for **Microsoft Configuration Manager** it's recommended to modify the `winpe.wim` boot image included with the **Windows PE add-on for the Windows ADK**. For more information, see [Microsoft Configuration Manager considerations](#microsoft-configuration-manager-considerations).
|
||||
|
||||
- For the default 64-bit boot image that is generated by the **Microsoft Deployment Toolkit (MDT)**, the boot image is located at `<Deployment_Share>\Boot\LiteTouchPE_x64.wim`. However, for **Microsoft Deployment Toolkit (MDT)** it's recommended to modify the boot image included with the **Windows PE add-on for the Windows ADK**. For more information, see [Microsoft Deployment Toolkit (MDT) considerations](#microsoft-deployment-toolkit-mdt-considerations).
|
||||
- For the default 64-bit boot image that is generated by the **Microsoft Deployment Toolkit (MDT)**, the boot image is located at `<Deployment_Share>\Boot\LiteTouchPE_x64.wim`. However, for **Microsoft Deployment Toolkit (MDT)** it's recommended to modify the `winpe.wim` boot image included with the **Windows PE add-on for the Windows ADK**. For more information, see [Microsoft Deployment Toolkit (MDT) considerations](#microsoft-deployment-toolkit-mdt-considerations).
|
||||
|
||||
- For 64-bit boot images in **Windows Deployment Services (WDS)**, the boot images are located at `<RemoteInstall>\Boot\x64\Images`.
|
||||
|
||||
@ -215,20 +215,17 @@ For more information, see [Add and Remove Driver packages to an offline Windows
|
||||
|
||||
---
|
||||
|
||||
For a list of all available WinPE optional components including descriptions for each component, see [WinPE Optional Components](/windows-hardware/manufacture/desktop/winpe-add-packages--optional-components-reference?view=windows-11#winpe-optional-components).
|
||||
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> For Microsoft Configuration Manager boot images, make sure to add any desired optional components manually using the above command lines instead of adding them through Configuration Manager via the **Optional Components** tab in the **Properties** of the boot image. This is because the cumulative update being applied at the next step will also update any optional components as needed. If the optional components are instead added through Configuration Manager, then the optional components will not be updated with the cumulative update. This could lead to unexpected behaviors and problems.
|
||||
>
|
||||
> For this reason, make sure to add the following required optional components need by Configuration Manager:
|
||||
>
|
||||
> - Scripting (WinPE-Scripting)
|
||||
> - Startup (WinPE-SecureStartup)
|
||||
> - Network (WinPE-WDS-Tools)
|
||||
> - WMI (WinPE-WMI)
|
||||
>
|
||||
> Once any optional components has been manually added to a boot image, Configuration Manager will detect that the optional component has already been added. It will not try to add the optional component again whenever it is updating the boot image.
|
||||
> When adding optional components, make sure to install optional components that are prerequisites of other optional components. Additionally, make sure that the prerequisite is installed firts. For more information on adding optional components, see [WinPE Optional Components (OC) Reference: How to add Optional Components](/windows-hardware/manufacture/desktop/winpe-add-packages--optional-components-reference?view=windows-11#how-to-add-optional-components).
|
||||
|
||||
### List of optional components
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> Both **Microsoft Configuration Manager** and **Microsoft Deployment Toolkit (MDT)** boot images require certain optional components to work properly. Make sure to add these required components when using either **Microsoft Configuration Manager** and **Microsoft Deployment Toolkit (MDT)**
|
||||
>
|
||||
> Additionally, when adding any optional component for either **Microsoft Configuration Manager** or **Microsoft Deployment Toolkit (MDT)** boot images, make sure to add the components manually using the above command lines instead of adding them through **Configuration Manager** or **MDT**. For more information, see [Microsoft Configuration Manager considerations](#microsoft-configuration-manager-considerations) or [Microsoft Deployment Toolkit (MDT) considerations](#microsoft-deployment-toolkit-mdt-considerations).
|
||||
|
||||
## Step 7: Add cumulative update (CU) to boot image
|
||||
|
||||
@ -399,8 +396,47 @@ For more information, see [Modify a Windows image using DISM: Unmounting an imag
|
||||
|
||||
## Microsoft Configuration Manager considerations
|
||||
|
||||
Microsoft Configuration Manager creates its own boot images by taking the `winpe.wim` from the Windows ADK, adding some optional components it requires to function correctly, and then saving the boot image as `boot.wim` in the directory `<ConfigMgr_Install_Directory>\OSD\boot\<architecture>\boot.wim`. This `boot.wim` boot image is considered the pristine authoritative copy of the boot image by Configuration Manager and is almost never touched, modified, or updated by Configuration Manager. Instead, when changes such as:
|
||||
|
||||
- Adding drivers
|
||||
- Adding additional optional components
|
||||
- Enabling the command prompt
|
||||
|
||||
are done in the properties of the boot image in Configuration Manager, Configuration Manager makes a copy of `boot.wim`, applies the changes to the copy, and then saves the new boot image as `boot.<package_id>.wim`. If any additional changes are done to the boot image, Configuration Manager discards the previously created `boot.<package_id>.wim` boot image, makes a copy of `boot.wim`, applies the changes to the copy, and then saves the new boot image as `boot.<package_id>.wim`. In other words, `boot.wim` is never touched. Any time any changes are made to a boot image, both the new changes and any changes done in the past are reapplied to a new copy of `boot.wim`. The new changes are not applyed the existing copy of `boot.<package_id>.wim`.
|
||||
|
||||
This process makes has the following advantages:
|
||||
|
||||
1. Keeps `boot.wim` pristine.
|
||||
1. Makes sure that when changes are made to a boot image, they are being done to a copy of a pristine version of the boot image that hasn't had been modified in the past. This helps avoid corruption and/or corrects issues with existing boot images.
|
||||
1. Helps manage components in the boot image. The process doesn't need to know what components it might need to remove from the boot image each time the boot image is rebuilt. Instead, it just needs to know what components to add to the boot image.
|
||||
1. Reduces the size of the boot image that can occur when components are removed from the boot image.
|
||||
|
||||
There are two scenarios when the `boot.wim` boot image is updated by Configuration Manager:
|
||||
|
||||
1. When updating between versions of Configuration Manager or when applying hotfix roll ups (HFRUs) to Configuration Manager, `boot.wim` may be updated as part of the update process.
|
||||
1. When selecting the option **Reload this boot image with the current Windows PE version from the Windows ADK** in the **Update Distribution Points Wizard**.
|
||||
|
||||
In theses scenarios, the `boot.wim` boot image is updated using the `winpe.wim` boot image from the Windows ADK as described earlier in this section. This process creates a new pristine copy of the `boot.wim` boot image using the current version of the `winpe.wim` boot image that is part of the Windows ADK.
|
||||
|
||||
### Microsoft Configuration Manager boot image required components
|
||||
|
||||
The following components are required by Microsoft Configuration Manager in the boot image for Configuration Manager to function correctly:
|
||||
|
||||
- Scripting/WinPE-Scripting (WinPE-Scripting)
|
||||
- Startup/WinPE-SecureStartup (WinPE-SecureStartup)
|
||||
- Network/WinPE-WDS-Tools (WinPE-WDS-Tools)
|
||||
- Scripting/WinPE-WMI (WinPE-WMI)
|
||||
|
||||
Once any optional components has been manually added to a boot image, Configuration Manager will detect that the optional component has already been added. It will not try to add the optional component again whenever it is updating the boot image.
|
||||
|
||||
### Adding optional components manually vs. adding optional components through Configuration Manager
|
||||
|
||||
For Microsoft Configuration Manager boot images, make sure to add any desired optional components manually using the above command lines instead of adding them through Configuration Manager via the **Optional Components** tab in the **Properties** of the boot image. This is because the cumulative update being applied at the next step will also update any optional components as needed. If the optional components are instead added through Configuration Manager, then the optional components will not be updated with the cumulative update. This could lead to unexpected behaviors and problems.
|
||||
|
||||
## Microsoft Deployment Toolkit (MDT) considerations
|
||||
|
||||
Copy boot files
|
||||
|
||||
## Windows Deployment Services (WDS) considerations
|
||||
|
||||
The **boot.wim** that is part of Windows installation media isn't supported for deploying Windows 11 with Windows Deployment Services (WDS). Additionally, the **boot.wim** from Windows 11 installation media isn't supported for deploying any version of Windows with Windows Deployment Services (WDS). For more information, see [Windows Deployment Services (WDS) boot.wim support](wds-boot-support.md)
|
||||
|
||||
Reference in New Issue
Block a user