ConfigMgr SCCM Boot Images are not Getting Updated After the Upgrade. Boot Images are not getting updated after the SCCM 2012 SP1 upgrade.
If your boot images weren’t updated during the site upgrade to SP1, you can manually update them using the following instructions. Clifton Hughes shared this information in his blog post.
This post provides all the details on what to do if ConfigMgr (SCCM) boot images do not update after an upgrade.
The guide addresses common issues and provides troubleshooting steps to ensure that your boot images reflect the latest updates and configurations.
Table of Contents
Fix? ConfigMgr SCCM Boot Images not Getting Updated After Upgrade
1. Rename the boot.wim and the default boot wims in each architecture folder of theOSD\boot\ folder – both the i386 and x64 to.bak
2. Starting with the i386 folder first…Find the install folder of the ADK, which should be here if you installed with the defaults: “C:\Program Files (x86)\Windows
3. Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us\winpe.wim”. You will need to copy the winpe.wim to the OSD\boot\i386 folder. Rename it to boot. wim.
4. You will also need to copy it again, but this time rename it so it matches the name of the default boot wim for the site – so it should look like boot.<packageid>.wim
Update the Default Boot Image |
---|
Click “Execute Method” -> input object path as SMS_BootImagePackage.PackageID=” |
6. You will also need to do this for the x64 folder. Do not do this for any custom boot images – this is just to update the default boot wims installed during the site’s setup.
- OSD Known Issues Troubleshooting Guide | SCCM | ConfigMgr
- SCCM Create Custom Windows PE Boot Image Using MDT with ConfigMgr
Resources
We are on WhatsApp now. To get the latest step-by-step guides, news, and updates, Join our Channel. Click here – HTMD WhatsApp.
Author
Anoop C Nair is Microsoft MVP from 2015 onwards for consecutive 10 years! He is a Workplace Solution Architect with more than 22+ years of experience in Workplace technologies. He is a Blogger, Speaker, and Local User Group Community leader. His main focus is on Device Management technologies like SCCM and Intune. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security, Career etc…
Hi, I have downloaded SCCM with SP1 after 25th January 2013. Setup a lab environment with AD,DNS and DHCP on one VM,SCCM and SQL server 2008 R2 SP1 with CU 6 on 2nd VM. WHen try to install SCCM SP1 for a standalone promary site needs prerequisite USMT,Windows Deployment TOOL KIT, Windows PReinstalltion environment on site server but when i downloaded ADK from microsoft and run it first it is taking a huge time and stuck at 13 % WIndows PE and error poping up that few cab files missing. Any advice how to make it faster and remove the error