SOLVED Boot Images are not working with ADK 10.1.26100.2454

[rjm2884]

I’ve recently upgraded Configuration Manager from 2309 to 2409, and now to 2530. After the upgrade, I realized my boot images were outdated, so I installed the latest Windows ADK 10.1.26100.2454 along with the matching WinPE add-on to support Windows 11 24H2 deployments.

However, I’m running into constant issues. Reloading the boot images using the new ADK fails every time. I’ve also tried using copype to create a fresh boot image and attempted to import the generated boot.wim into SCCM, but that fails too.

So far, I’ve:

• Uninstalled both ADK and WinPE
• Redownloaded and reinstalled them
• Rebooted the server
• Cleaned up old Installed Roots registry entries from previous ADK versions
• Verified all folder paths and permissions

Despite all this, I’m still unable to reload or import a boot image using ADK 10.1.26100.2454. I need to begin deploying Windows 11 24H2 in my environment, and being stuck with outdated boot images is becoming a blocker.

Has anyone successfully gotten 26100.2454 working with ConfigMgr 2530? Any advice or ideas would be appreciated. Thanks in advance!

 

[Stanley Road]

I can test this in my lab. What is the error you are seeing?

 

[Stanley Road]

I can test this in my lab. What is the error you are seeing?

I’ve recently upgraded Configuration Manager from 2309 to 2409, and now to 2530. After the upgrade, I realized my boot images were outdated, so I installed the latest Windows ADK 10.1.26100.2454 along with the matching WinPE add-on to support Windows 11 24H2 deployments.

However, I’m running into constant issues. Reloading the boot images using the new ADK fails every time. I’ve also tried using copype to create a fresh boot image and attempted to import the generated boot.wim into SCCM, but that fails too.

So far, I’ve:

• Uninstalled both ADK and WinPE
• Redownloaded and reinstalled them
• Rebooted the server
• Cleaned up old Installed Roots registry entries from previous ADK versions
• Verified all folder paths and permissions

Despite all this, I’m still unable to reload or import a boot image using ADK 10.1.26100.2454. I need to begin deploying Windows 11 24H2 in my environment, and being stuck with outdated boot images is becoming a blocker.

Has anyone successfully gotten 26100.2454 working with ConfigMgr 2530? Any advice or ideas would be appreciated. Thanks in advance!

I was able to reproduce it in my lab. The fix was this https://www.linkedin.com/pulse/mdt-...on-configmgr-2403-caused-console-essam-td6lf/. When you remove and then re-add the mdt plugins you have to change these files to https each time

 

[Nilantha]

I'm still using CM 2403 (KB28204160) branch since still use Windows 10 imaging with MDT. I'm afraid to update to latest 2409 and 2503 hence it might brake Windows 10 imaging with MDT.

But I am able to install latest ADK 10.1.26100.2454 (removed old version) and Add Windows 11 24h2 boot image 10.0.26100. Also I can see that boot image pick Image ID for Windows 11 24h2 boot image but not proceeding to MDT Wizard for Windows 10 TS after downloading boot image (.wim) from PXE boot. I can see startup WinPE , move to next page, reboot without asking password for PXE.

If I delete Windows 11 24h2 boot image, it works again with existing Windows 10 boot image without any issue.

Have I done any wrong coifig? please share some thoughts. thank you!

 

[Stanley Road]

I'm still using CM 2403 (KB28204160) branch since still use Windows 10 imaging with MDT. I'm afraid to update to latest 2409 and 2503 hence it might brake Windows 10 imaging with MDT.

But I am able to install latest ADK 10.1.26100.2454 (removed old version) and Add Windows 11 24h2 boot image 10.0.26100. Also I can see that boot image pick Image ID for Windows 11 24h2 boot image but not proceeding to MDT Wizard for Windows 10 TS after downloading boot image (.wim) from PXE boot. I can see startup WinPE , move to next page, reboot without asking password for PXE.

If I delete Windows 11 24h2 boot image, it works again with existing Windows 10 boot image without any issue.

Have I done any wrong coifig? please share some thoughts. thank you!

This probably requires it's own thread?