Hi Swati Arora,
Moving to the 26100 ADK requires you to generate a brand-new WinPE image because servicing an existing Windows 10-based boot.wim with Windows 11-based binaries often leads to versioning conflicts in the registry and the component store. By using the fresh winpe.wim found in the %ProgramFiles(x86)%\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment path, you ensure that all underlying binaries are natively signed with the Microsoft UEFI CA 2023. This is vital because the new boot image will include both the 2011 and 2023 signatures, allowing it to remain bootable after the 2011 certificate is eventually revoked at the firmware level.
You can't skip the Windows PE Add-on installation even if your workflow focuses on WinRE. The base ADK installation only provides the deployment tools and command-line utilities, while the actual bootable environment source files reside exclusively within the Add-on. Without this component, you will lack the necessary files to create or modify any recovery or deployment media. Since version 26100 is based on the Windows 11 architecture, you must also account for the fact that x86 (32-bit) WinPE is no longer supported; you will be working strictly with x64 environments.
Regarding the certificate transition, while the new ADK handles the software side, your primary manual action is ensuring your BIOS updates successfully apply the updated Secure Boot Forbidden Signature Database (DBX) to your hardware fleet. If the BIOS upgrade does not correctly update the Revocation List, your devices might still be vulnerable or fail to validate the new signatures correctly. Additionally, ensure any custom drivers you inject into the new WinPE are compatible with the latest UEFI requirements to prevent "Digital Signature" error codes during the boot sequence.
Hope this answer brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.
VP