Hi,

I'm unable to update only the x64 boot image. I don't import any drivers but when i try to update the content on the DP, I receive the following error:

  Error: Boot image to update: 
Microsoft Windows PE (x64)
 
  Error: Actions to perform: 
Add ConfigMgr binaries
Set scratch space
Enable Windows PE command line support
 
 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.
Failed to inject a ConfigMgr driver into the mounted WIM file
The SMS Provider reported an error.: ConfigMgr Error Object:
instance of SMS_ExtendedStatus
{
Description = "Failed to insert OSD binaries into the WIM file";
ErrorCode = 2152205056;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
Line = 4566;
ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
Operation = "ExecMethod";
ParameterInfo = "SMS_BootImagePackage.PackageID=\"PS100004\"";
ProviderName = "WinMgmt";
StatusCode = 2147749889;

And I'm using SCCM 2012 SP1 fresh install

• Edited by Jello07 Wednesday, March 20, 2013 8:39 PM

This is caused because the original driver source files that you added to the boot image no longer exist or have been moved. Driver injection for boot images happens every time you update the boot image and these drivers are pulled from the original import location and not the driver packages. Thus, you need to verify that the original driver location you imported drivers into ConfigMgr is still accessible and the driver files are still there.

I'll try to add the drivers again because I removed them..

I had similar Problems, when I upgraded an RTM to SP1. There was also some error Messages in the DISM Log file (c:\windows\logs\dism).

It was the McAfee OnAccess Scan, which I had to disable.

• Proposed as answer by Ronyran Thursday, April 24, 2014 10:54 AM

I've imported the drivers without adding them in the boot image and the issue is resolved.

Thanks even if I don't understand the logic behind this

Essentially, there are three locations for your drivers:

- The original location you imported them from

- The driver package source location you imported them into

- The contentlib

When you inject them into a boot image, the drivers are pulled from the original source location. This happens every time you update the boot image also.

They use the original source location because technically, you can import drivers without putting them into a driver package and thus this is the only location they are guaranteed to be at. Drivers imported in ConfigMgr are essentially just references to the files you originally imported them

Thanks Jason

I have this same problem and none of our drivers have moved from their original source location.   I have disabled McAfee and it still fails.  

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 make a copy of source WIM file due to error 2";

• ErrorCode = 2;

• File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";

• Line = 4673;

• ObjectInfo = "CSspBootImagePackageInst::PreRefreshPkgSourceHook";

• Operation = "ExecMethod";

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

• ProviderName = "WinMgmt";

• StatusCode = 2147749889;