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?

 

[mbaldwin]

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

Hi Stanley. I have the very same issue with by boot image not reflecting the install ADK version 10-1-26100-2454, it refuses tp update from 10-1-26100-1, even if I tick Reload this boot image.

I have explored your solution in Linked In but the path C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\XmlStorage\Extensions\Forms does not exist on my SCCM server.

I am too stuck with only being able to image clients with windows 11 23h2

do you have any more ideas I can try please

 

[mbaldwin]

Hi Stanley. I have the very same issue with by boot image not reflecting the install ADK version 10-1-26100-2454, it refuses tp update from 10-1-26100-1, even if I tick Reload this boot image.

I have explored your solution in Linked In but the path C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\XmlStorage\Extensions\Forms does not exist on my SCCM server.

I am too stuck with only being able to image clients with windows 11 23h2

do you have any more ideas I can try please

Sorry I meant to say the folder C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\XmlStorage\Extensions\Forms does exist but is empty and contains no xml files to edit

 

[Stanley Road]

Hi Stanley. I have the very same issue with by boot image not reflecting the install ADK version 10-1-26100-2454, it refuses tp update from 10-1-26100-1, even if I tick Reload this boot image.

I have explored your solution in Linked In but the path C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\XmlStorage\Extensions\Forms does not exist on my SCCM server.

I am too stuck with only being able to image clients with windows 11 23h2

do you have any more ideas I can try please

If you have already integrated MDT to sccm then UN-Integrate it, then integrate it again and the files should be created for you to edit.

 

[Stanley Road]

If you have already integrated MDT to sccm then UN-Integrate it, then integrate it again and the files should be created for you to edit.

Same solution above still applies

 

[mbaldwin]

If you have already integrated MDT to sccm then UN-Integrate it, then integrate it again and the files should be created for you to edit.

thank you for your reply. Do you have a process or link for this. When I google it, MDT referred to Microsoft Dev Toolkit within task sequences? Just want to make sure I'm heading down the right avenue

 

[Stanley Road]

thank you for your reply. Do you have a process or link for this. When I google it, MDT referred to Microsoft Dev Toolkit within task sequences? Just want to make sure I'm heading down the right avenue

Integrating Microsoft Deployment Toolkit with Configuration Manager

Integrating Microsoft Deployment Toolkit with Configuration Manager, Integrate MDT 2013 with Configuration Manager, integrate SCCM with MDT

www.prajwaldesai.com

 

[mbaldwin]

Integrating Microsoft Deployment Toolkit with Configuration Manager

Integrating Microsoft Deployment Toolkit with Configuration Manager, Integrate MDT 2013 with Configuration Manager, integrate SCCM with MDT

www.prajwaldesai.com

thank you

 

[mbaldwin]

thank you

I have just looked up a list of MDT tasks, it appears I am using them in all of my task sequences, of which i have many. This screen shot shows common tasks for each of my 25+ TSs. So will these get deleted when I remove MDT and will I have to manually add them back in again?

 

[mbaldwin]

thank you

ok, stumbling block, I do not appear to have the Microsoft Deployment Kit installed at all.

 

[Stanley Road]

I have just looked up a list of MDT tasks, it appears I am using them in all of my task sequences, of which i have many. This screen shot shows common tasks for each of my 25+ TSs. So will these get deleted when I remove MDT and will I have to manually add them back in again?
View attachment 7436

No you wont have to add them back manually. 25 TSs is impressive by the way, why so many?

 

[mbaldwin]

No you wont have to add them back manually. 25 TSs is impressive by the way, why so many?

Thanks for your reply Stanley. We do not appear to have the MDT installed at all, so I'm not sure that I should install it to gain access to the xml files as MDT appears to be depreciated now?

We have many TSs because they use different driver packages and some have additional software to deploy

 

[Stanley Road]

Thanks for your reply Stanley. We do not appear to have the MDT installed at all, so I'm not sure that I should install it to gain access to the xml files as MDT appears to be depreciated now?

We have many TSs because they use different driver packages and some have additional software to deploy

Well you can achieve all of those things in one TS using variables, you could use a UDI template for the apps or you could deploy the apps to departmental collections and just move the pc's to them

 

[mbaldwin]

Well you can achieve all of those things in one TS using variables, you could use a UDI template for the apps or you could deploy the apps to departmental collections and just move the pc's to them

good shout, I'll look up how to use variables and UDI.

do you have any more ideas on how to get the boot image OS version to match the installed version? Now I realize I don't have the MDT installed, unless I install it even though it's depreciated.

 

[RTatum]

good shout, I'll look up how to use variables and UDI.

do you have any more ideas on how to get the boot image OS version to match the installed version? Now I realize I don't have the MDT installed, unless I install it even though it's depreciated.

View attachment 7437

For what it's worth, I just went down this rabbit hole today and came across this thread.

We upgraded our Config Manager site to 2503 last night, as well as updating to the latest "10.0.26100.2454" ADK/WinPE. I too was seeing the older 10.0.26100.1 OS Version on boot images that were either updated with the current ADK (which showed 10.0.26100.0) or newly imported from the winpe.wim file that came with the latest 24H2 ADK/WinPE updated December 2024.

From what I've found so far, the ADK itself was updated last December but apparently the WinPE add-on that goes with it was not. It's still the exact same 24H2 WinPE originally released in May of 2024, which is why the build number doesn't show .2454 in the console.

 

[mbaldwin]

For what it's worth, I just went down this rabbit hole today and came across this thread.

We upgraded our Config Manager site to 2503 last night, as well as updating to the latest "10.0.26100.2454" ADK/WinPE. I too was seeing the older 10.0.26100.1 OS Version on boot images that were either updated with the current ADK (which showed 10.0.26100.0) or newly imported from the winpe.wim file that came with the latest 24H2 ADK/WinPE updated December 2024.

From what I've found so far, the ADK itself was updated last December but apparently the WinPE add-on that goes with it was not. It's still the exact same 24H2 WinPE originally released in May of 2024, which is why the build number doesn't show .2454 in the console.

Thanks for the reply. So currently I'm unable to image my machines with anything above 23H2. When I attempt to image machines with 24H2 or 25H2 OS, the task sequence just hangs after about 8 applications, every time without fail. I've put this down to the boot image in SCCM not updating to the latest ADK