PENDING Failed to inject OSD binaries into mounted WIM file

[Stefan_19911]

Dear community

I am working here with SCCM 2006 on Server 2016 (update to newer SCCM version is planned) Windows ADK 10.1.19041.1 and Windows PE 10.1.19041.1). I inserted new drivers a few month ago and that worked fine, now i have these problems. I did not update the SCCM version or any other software i just installed the monthly windows updates.

I tried to update my boot image with a new driver because we got a new desktop model from HP that is missing a network driver to successfully run an OS deployment task from SCCM. I import the new driver with the driver tab and choose the driver that i imported into sccm. This driver is signed.
When i then try to update the distribution points afterwards i got this error at the step "Mount the source wim file to the staging directory. (there is enough drive space)

Error: Update boot image:
• Microsoft Windows PE (x64)

Error: Windows ADK reload actions:
• Reload using Windows PE from the ADK version 10.0.19041.0

Error: Update actions:
• Add ConfigMgr binaries using Production Client version 5.00.9012.1056
• Add custom background
• Set scratch space
• Enable Windows PE command line support
• Add drivers

Error: Failed to import the following drivers:
• Intel(R) Wireless-AC 9560 160MHz
• Realtek(R) USB FE Family Controller
• Realtek(R) USB FE Family Controller
• Intel RST VMD Controller 9A0B
• Intel RST VMD Controller 9A0B
• Intel(R) Dual Band Wireless-AC 7265
• Realtek 8822BE Wireless LAN 802.11ac PCI-E NIC
• Realtek RTL8723BE Wireless LAN 802.11n PCI-E NIC
• Realtek 8852AE Wireless LAN WiFi 6 PCI-E NIC
• Realtek 8852BE Wireless LAN WiFi 6 PCI-E NIC
• Intel(R) Ethernet Connection I217-LM
• Intel(R) I350 Gigabit Network Connection
• Intel(R) Ethernet Controller I225-LM
• Thunderbolt(TM) Networking

Optional components:
• Scripting (WinPE-Scripting)
• Startup (WinPE-SecureStartup)
• Network (WinPE-WDS-Tools)
• Scripting (WinPE-WMI)

Error: The wizard detected the following problems when updating the boot image.
• 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:reRefreshPkgSrcHook";
• Operation = "ExecMethod";
• ParameterInfo = "SMS_BootImagePackage.PackageID=\"BUC00160\"";
• ProviderName = "WinMgmt";
• StatusCode = 2147749889;

> i see no unsigned drivers when i check the driver tab

------------------------------------------------------------------------------------------------------

When i try to use the function "Add boot image" and try to create a new image i got this error (i copied manually the original winpe.wim file from path "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us"This is the original install path from the Windows Deployment Kit

I created a new folder in the path "D:\SCCM\OSD\Boot" and copied manually the winpe.wim file in that directory. Then i chooses this winpe.wim file when i have to choose a .wim file for the new boot image. The wizard ends with this error message:



Error: Data Source Information
• Source location: \\v-server-226\OSD\Boot\tes\winpe.wim
• Boot Image: 1 - Microsoft Windows PE (x64)
Error: Package Information
• Name: winpe
Error: Errors
• The specified file can not be imported. Make sure the file is not read only and you have read and write access to it.


i also checked that the copied winpe.wim file is not "read-only".
there is also enough free space on any drive.


------------------------------------------------------------------------------------------------------

When i try to use the function "create boot image using mdt" i get this error (i never used this function before)
Started processing.
Creating boot image.
Copying WIM file.
Mounting WIM file.
WIM file mounted.
Setting Windows PE system root.
Set Windows PE system root.
Set Windows PE scratch space.
Adding standard components.
Adding component: winpe-mdac
Adding extra content from: C:\Users\adminbubu\AppData\Local\Temp\4\414nd5ec.niu
Unmounting WIM.
Copying WIM to the package source directory.
Creating boot image package.
Error while importing Microsoft Deployment Toolkit Task Sequence.

Failed to insert OSD binaries into the WIM file

Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException: The SMS Provider reported an error. ---> System.Management.ManagementException: Generic failure
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.Put(PutOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
--- End of inner exception stack trace ---
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put()

i am really lost now, i also renamed the c:\windows\temp\bootimages folder like i wrote i an other answer. That did not solve the problem.

thank you very much for all your help

 

[AhmedLS]

i had this issue a while ago and made me crazy as i didnt know what to look for. at last i had to build a new boot image and injuct the drivers one model at a time. i found out that one model didnt have the drivers on SCCM store which triggered the error cannot inject the binarys. the drivers where showing on SCCM but they were missing for some reason. i had to delete the package and create a new driver package for that model. hope this will help you somehow.
when creating a new boot image dont use the old one coz the old one has the missing drivers and will trigger the cannot inject binaries error. use the ADK boot wim

 

[Stefan_19911]

Hi Ahmed

Thank you for your reply.
I also had problems to create new boot images and the reason was the stupid Windows Defender.
My colleague activated the Defender on several serves and also on my SCCM. He used a GPO and put in the best practice behavior IDs from Microsoft. ID Matrix for Defender

If you use this ID 9e6c4e1f-7d60-472f-ba1a-a39ef669e4b2 then the Defender will block C:\Windows\System32\wimserv.exe which is used somehow in creating new pxe images.

The problem with adding drivers is crazy.
I had a driver two times an older and a newer version, adding the newer version triggered that error, adding the older version worked fine.

Have you ever tried to inject the drivers with DISM manually in an existing empty boot image and then exchange the .wim file in the folder and then just use the function "distribute content" instead of "update distribution point" ?

Lets imagine you need to inject a storage or network driver for a new computer model and this driver will always trigger that error - how would you update your driver package then ?

Thank you for all your feedback and help.

 

[AhmedLS]

Hi Ahmed

Thank you for your reply.
I also had problems to create new boot images and the reason was the stupid Windows Defender.
My colleague activated the Defender on several serves and also on my SCCM. He used a GPO and put in the best practice behavior IDs from Microsoft. ID Matrix for Defender

If you use this ID 9e6c4e1f-7d60-472f-ba1a-a39ef669e4b2 then the Defender will block C:\Windows\System32\wimserv.exe which is used somehow in creating new pxe images.

The problem with adding drivers is crazy.
I had a driver two times an older and a newer version, adding the newer version triggered that error, adding the older version worked fine.

Have you ever tried to inject the drivers with DISM manually in an existing empty boot image and then exchange the .wim file in the folder and then just use the function "distribute content" instead of "update distribution point" ?

Lets imagine you need to inject a storage or network driver for a new computer model and this driver will always trigger that error - how would you update your driver package then ?

Thank you for all your feedback and help.

I use DISM all the time with MDT boot WIM and it works like charm. for SCCM i just create WInPE packages for the drivers and use those to inject into the CM boot image. i never update those drivers just add to them new one as those are not used only to get the system booting and then windows will take over.