CM2012 SP1 – No default boot images available / "Only finalized boot images are supported"

January 14, 2013 at 7:57 am in adk, CM12, ConfigMgr, ConfigMgr 2012, ConfigMgr 2012 SP1, mcaffee, SCCM 2012, SCCM 2012 SP1, WAIK by Kenny Buntinx [MVP]


Issue : When you do a fresh install or you do an upgrade from Configmgr 2012 RTM to SP1 , you will see your install/upgrade failing with “No default boot images available” or "Only finalized boot images are supported" . The Configmgr setup log file will confirm that the migration/creation of boot images did not succeed.

Adding the boot images manual isn’t working neither. You will see the following error message :



Reason :  You have the following components running in your environment :

  • McAfee VirusScan Enterprise (VSE) 8.8 Patch 2
  • Microsoft Windows Assessment and Installation Kit (WAIK)
  • ADK (Assessment and Deployment Kit)
  • Microsoft Deployment Toolkit (MDT) 2012 / SP1
  • Microsoft Configuration Manager 2012 RTM / SP1

Solution :

Issue during upgrade from RTM to SP1 : If you find yourself in this situation where boot images didn’t get updated during site upgrade, you can manually update the boot images using the following instructions:

    1. Rename the boot.wim and the default boot wims in each architecture folder of the <smsinstall>OSD\boot\ folder – both the i386 and x64 to <wim>.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 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 <smsinstall>OSD\boot\i386 folder. Rename it to boot.wim.
    3. 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
    4. Update default boot image.
    5. Click “Execute Method” -> input object path as SMS_BootImagePackage.PackageID="<Image ID you see in the Console e.g. POL00001>" -> UpdateDefaultImage
    6. You will need to do this for the x64 folder as well. Do not do this for any custom boot images – this is just to update the default boot wims installed during setup of the site.

Before full install or upgrade :

Folders to exclude from AV scanning:

· Temporary folder for these cases is C:\Windows\TEMP\BootImages\{GUID}.  Exclude C:\Windows\TEMP\BootImages and subfolders.

· Temporary folder for offline servicing is <X:>\ConfigMgr_OfflineImageServicing and several subfolders used for different purposes – staging files, mounting OS, etc. – where <X:> is the StagingDrive value from the Offline Servicing Manager section of the site control file.  If this value is missing, we use the drive where the site is installed.  Exclude <X:>\ConfigMgr_OfflineImageServicing and subfolders.

Information from Mcaffee : KB:

Product team Blog :

Hope it Helps ,

Kenny Buntinx

MVP System Center Configuration Manager 2012

Tweet about this on TwitterShare on FacebookShare on Google+Share on LinkedInPin on Pinterest