Post SCCM 2012 SP1 – failure to update boot images

*** UPDATE *** This also works if you are unable to rebuild your boot images after upgrading to Windows 10 ADK (the final version)

I did a customer SP1 upgrade during the weekend, the process ran successfully according to the Setup UI, but when I later tried to update the boot images I received the following error:

Failed to insert OSD binaries into the WIM file

Another symptom of this problem is that when you open the properties for the boot images, the pane Optional components will show no items in either of the lists.


And finally you may also notice that the version number of the image is not 6.2.9200.16384 as it should be after the upgrade.

First I tried to simply create a new image, i.e. a MDT image. But I got the same error message.

Having read the reports of people having problems with building boot image, caused by McAfee AV. I started to look at the ForeFront setup on the server. I excluded the c:\windows\temp\bootimages and the osd\boot folders. I even tried excluding the dism.exe process. But all of this had no effect. So finally I uninstalled ForeFront completely.

And behold … suddenly I was able to build a new MDT boot image and it had the standard optional components. But I was still not able update the built-in boot images.

That was solved using a fix I got from Kent Agerlund, and it goes something like this:

  1. Rename the defect boot.wim file in the folder <sms install folder>\osd\boot\i386 to boot.bak
  2. Now copy the winpe.wim file from %ProgramFiles(x86)%\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us\ to <sms install folder>\osd\boot\i386 and rename it to boot.wim
  3. Repeat the copy for each boot.<packageid>.wim in the target folder
  4. Now run Update distribution points to test if the boot image is updatable again

Repeat the process for the x64 boot image.

This process was described by Clifton Hughes_MS on his blog, found here

By |2013-01-14T22:16:07+00:00January 14th, 2013|Configuration Manager (SCCM), OS Deployment|7 Comments

About the Author:

Ronnie Jakobsen
Twitter: @RonnieJakobsen


  1. Bill Y April 5, 2013 at 8:14 - Reply

    Thanks for this!

    I had created a test boot image for DaRT inclusion and everything seemed to go downhill fast. This let me replace the originals and get back in business.

  2. Chris Jones April 15, 2013 at 22:09 - Reply

    How do I repeat the process for Step 3 “3.Repeat the copy for each boot..wim in the target folder”.

    Do I just copy the same file from as in Step 2 and just add the name?

  3. Steve Orah May 30, 2013 at 13:04 - Reply

    The fix worked for me… I replaced both *.wim files and created both Boot.wim files and updated both and PXE Boot came back to life.

  4. Terence Martin May 26, 2016 at 14:30 - Reply

    I had an issue where i didnt actually have any boot files to begin with! Found that my AV had blocked some crucial files during install. How i resolved? Had to update DISM to begin to mount the boot images:

    Had to follow this but on import of images check the SMSProv.log – At each step there was an issue with a file being missing such as: Failed to copy file ‘\OURSERVERSMS_MANOSD\bini386TsRes.dll’ to ‘C:WindowsTEMPBootImages{12F9414A-D6F6-4C9D-BDD2-B47F1916FA02}mountsmsbini386TsRes.dll’ SMS Provider 26/05/2016 13:12:46 19072 (0x4A80)
    Solution was to copy all files and directores in the install media – osdbin over to the \OURSERVERSMS_MANOSD\bin

  5. Terence Martin May 26, 2016 at 14:53 - Reply
  6. Black Arrows March 13, 2018 at 21:53 - Reply

    This solved my problem as well, thanks!

Leave A Comment