Graphics
Intel® graphics drivers and software, compatibility, troubleshooting, performance, and optimization
Announcements
For support on Altera products please visit the Altera Community Forums.
23272 Discussions

Inject latest Intel AHCI into WinPE fails

idata
Employee
2,722 Views

Hi

I have a problem when I try to inject Intel AHCI driver with version 10.1.0.1008 into a WinPE boot image via SCCM console.

Receive following error message:

Error: Boot image to update:

 

Microsoft Windows PE (x86)

Error: Actions to perform:

 

Add ConfigMgr binaries

 

Disable Windows PE command line support

 

Add drivers

Success: Drivers that will be included:

 

Intel(R) ESB2 SATA RAID Controller

Error: Failed to import the following drivers:

 

Intel(R) ESB2 SATA AHCI Controller - Failed to inject a ConfigMgr driver into the mounted WIM file

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

 

Failed to inject a ConfigMgr driver into the mounted WIM file

 

Failed to inject a ConfigMgr driver into the mounted WIM file

 

Failed to inject a ConfigMgr driver into the mounted WIM file

 

Failed to inject a ConfigMgr driver into the mounted WIM file

 

Failed to inject a ConfigMgr driver into the mounted WIM file

 

Failed to inject a ConfigMgr driver into the mounted WIM file

 

Failed to inject a ConfigMgr driver into the mounted WIM file

 

Failed to inject a ConfigMgr driver into the mounted WIM file

 

Failed to inject a ConfigMgr driver into the mounted WIM file

 

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

 

instance of SMS_ExtendedStatus

 

{

 

Description = "Failed to insert OSD binaries into the WIM file";

 

ErrorCode = 2152205056;

 

File = "c:\\qfe\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";

 

Line = 4262;

 

ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";

 

Operation = "ExecMethod";

 

ParameterInfo = "SMS_BootImagePackage.PackageID=\"HBG0007B\"";

 

ProviderName = "WinMgmt";

 

StatusCode = 2147749889;

 

};

Anyone encountered this problem before, and might have a workaround?

Best regards

US

0 Kudos
0 Replies
Reply