From 89a9f1bba2489fc5701dcdfb5f025b88909b0c7b Mon Sep 17 00:00:00 2001
From: Frank Rojas <45807133+frankroj@users.noreply.github.com>
Date: Mon, 7 Aug 2023 12:25:46 -0400
Subject: [PATCH] Update Boot Image with CU Article 53

---
 windows/deployment/update-boot-image.md | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/windows/deployment/update-boot-image.md b/windows/deployment/update-boot-image.md
index 2826d0a60b..0c305025f3 100644
--- a/windows/deployment/update-boot-image.md
+++ b/windows/deployment/update-boot-image.md
@@ -207,6 +207,8 @@ or
 Add-WindowsDriver -Path "C:\Mount" -Driver "C:\Drivers" -Recurse
 ```
 
+For more information, see [Add-WindowsDriver](/powershell/module/dism/add-windowsdriver).
+
 ### [:::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 commands to add drivers to the boot image:
@@ -320,6 +322,8 @@ The cumulative update installed later in this walkthrough doesn't affect drivers
 
     These examples assume a 64-bit boot image. If a different architecture is being used, then adjust the paths accordingly.
 
+    For more information, see [Add-WindowsPackage](/powershell/module/dism/add-windowspackage).
+
     ### [:::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 the following command to add the language components for the optional components to the boot image:
@@ -338,6 +342,8 @@ The cumulative update installed later in this walkthrough doesn't affect drivers
 
     You can add as many desired optional components as needed on a single DISM.exe command line.
 
+    For more information, see [Add or Remove Packages Offline Using DISM](/windows-hardware/manufacture/desktop/add-or-remove-packages-offline-using-dism) and [DISM Operating System Package (.cab or .msu) Servicing Command-Line Options: /Add-Package](/windows-hardware/manufacture/desktop/dism-operating-system-package-servicing-command-line-options#add-package).
+
     ---
 
 > [!IMPORTANT]
@@ -603,6 +609,8 @@ Copy-Item "C:\Mount\Windows\Boot\EFI\bootmgfw.efi" "C:\Program Files (x86)\Windo
 
 To overwrite the bootmgr boot files and any backed up bootmgr boot file without confirmation, for example in a script, add the `-Force` parameter to the end of the command lines.
 
+For more information, see [Copy-Item](/powershell/module/microsoft.powershell.management/copy-item).
+
 ### [:::image type="icon" source="images/icons/command-line-18.svg"::: **Command Line**](#tab/command-line)
 
 From an elevated command prompt, run the following command to copy the updated bootmgr boot files from the mounted boot image to the ADK installation path. These commands also back up any existing bootmgr boot files its finds. When applicable, the commands need confirmation to overwrite any existing files:
@@ -631,6 +639,9 @@ copy "C:\Mount\Windows\Boot\EFI\bootmgfw.efi" "C:\Program Files (x86)\Windows Ki
 
 To overwrite the bootmgr boot files and any backed up bootmgr boot file without confirmation, for example in a script, add the `/Y` parameter to the end of the command lines.
 
+
+For more information, see [copy](/windows-server/administration/windows-commands/copy).
+
 ---
 
 This step doesn't update or change the boot image. However, it makes sure that the latest bootmgr boot files are available to the Windows ADK when creating bootable media via the Windows ADK. When these files are updated in the Windows ADK, products that use the Windows ADK to create bootable media also have access to the updated bootmgr boot files.