deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-20 21:03:42 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Update Boot Image with CU Article 36

Browse Source
This commit is contained in:
Frank Rojas
2023-08-01 16:45:33 -04:00
parent 45be907e26
commit ddbe00600b
1 changed files with 12 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
windows/deployment/update-boot-image.md
View File

@ -139,6 +139,11 @@ From an elevated **PowerShell** command prompt, run the following command to add
```powershell
Add-WindowsDriver -Path "<Mount_folder_path>" -Driver "<Driver_INF_source_path>\<driver>.inf"
Example:
Add-WindowsDriver -Path "C:\Mount" -Driver "C:\Drivers\driver.inf"
```
or
@ -147,6 +152,11 @@ or
Add-WindowsDriver -Path "<Mount_folder_path>" -Driver "<Drivers_source_path>" -Recurse
```
**Example**:
Add-WindowsDriver -Path "C:\Mount" -Driver "C:\Drivers\" -Recurse
### [:::image type="icon" source="images/icons/command-line-18.svg"::: **Command Line**](#tab/command-line)
From an elevated **Deployment and Imaging Tools Environment** command prompt, run one of the following command to add drivers to the boot image:
@ -423,7 +433,7 @@ For more information, see [Modify a Windows image using DISM: Unmounting an imag
### How Microsoft Configuration Manager creates boot images
Microsoft Configuration Manager creates its own boot images by taking the `winpe.wim` from the Windows ADK, adding some [optional components it requires](#microsoft-configuration-manager-boot-image-required-components) 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 never touched, modified, or updated by Configuration Manager except in some very specific scenarios. Instead, when changes such as:
Microsoft Configuration Manager creates its own boot images by taking the `winpe.wim` from the Windows ADK, adding some [optional components it requires](#configuration-manager-boot-image-required-components) 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 never touched, modified, or updated by Configuration Manager except in some very specific scenarios. Instead, when changes such as:
- Adding drivers
- Adding optional components
@ -479,7 +489,7 @@ When using Configuration Manager, the `winpe.wim` boot image from the Windows AD
By updating `winpe.wim` from the Windows ADK, this will ensure that the cumulative update will stay applied regardless of what changes are made to the boot image via Configuration Manager.
### Boot image required components
### Configuration Manager boot image required components
The following components are required by Microsoft Configuration Manager boot images for Configuration Manager to function correctly: