Failed to update boot image after SCCM v2006 update : "File = "..\\sspbootimagepackage.cpp";"

Question

Got the new ADK and PE all installed.

Error in SMSPROV: Failed to copy file '\SCCM-Server\SMS_CSF\OSD\bin\x64\ccmcore.dll' to 'C:\WINDOWS\TEMP\BootImages{5A21EF4D-9AFE-493E-AD98-D60123456D54}\mount\sms\bin\x64\ccmcore.dll'

Full error:

Error: The wizard detected the following problems when updating the boot image.

• Failed to insert OSD binaries into the mounted WIM file

The SMS Provider reported an error.: ConfigMgr Error Object:

instance of SMS_ExtendedStatus

{

• Description = "Failed to inject OSD binaries into mounted WIM file (often happens if unsigned drivers are inserted into x64 boot image)";

• ErrorCode = 2152205056;

• File = "..\sspbootimagepackage.cpp";

• Line = 5482;

• ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";

• Operation = "ExecMethod";

• ParameterInfo = "SMS_BootImagePackage.PackageID=\"CSF00005\"";

• ProviderName = "WinMgmt";

• StatusCode = 2147749889;

Little help here cos I am googled out....

Thanks

Answer 1

@SenhorDolas

1. May we know that the versions of ADK and PE are the newest like version 2004？
2. For our"Failed to insert OSD binaries into the mounted WIM file":
   (1) Maybe we could try to delete the boot Images folders manually.
   (2) Use the dism to check if the mounted WIM's exist on the machine.
   (3) Run the Update Distribution Points and it should be completed successfully.
   Please refer to this article to get more details:
   failed to inject osd binaries into mounted WIM file ErrorCode = 2152205056
   Note:This article is not an official Microsoft article.

Hope this could help you.

---

If the response is helpful, please click "Accept Answer" and upvote it.

Answer 2

Few things to consider,

Ensure you have removed all extra Drivers before updating using the Reload box.

Also have you restarted the server since the upgrade of ADK / WinPE Add-on?

Answer 3

I was able to resolve my issue with error by deleting this folder C:\Windows\Temp\BootImages

Answer 4

Mine was only the MDT boot image, all others updated fine. I was able to fix it by creating a new boot image from the same MDT source file, then once the new one was created I tried updating the failing one and it was successful.

Answer 5

@SenhorDolas

Could we try to create a custom boot image by using MDT?

1. If the boot image could be created successfully,maybe we need to uninstall and reinstall our ADK.
2. If the boot image could not be created successfully,maybe our SCCM environment and then we could get the further step.
   Here are some useful article for you to refer to:
   create a custom windows pe boot image with configuration manager
   how to create boot image using mdt for sccm

Hope this could help you.

---

If the response is helpful, please click "Accept Answer" and upvote it.