The Nvidia driver is being worked on by Nvidia, no ETA yet. I haven't seen an issue with the NIC driver. Which Cab version or driver version (Rnumber) is problematic?

I am also having a difficult time with this (having the same problem) I am using the Dell Win-PE-Drivers-A05.cab. I am having an issue where the NIC card where it gets an ip address but does not engage correctly when the client tries to download content for imaging from the server. This results in a failed deployment with the error 0x8004005. If there are any recommended resolutions to this problem id like to know about them. My next step in troubleshooting will likely be to import the driver directly from Intel into the .wim file and see if my results get any better. The machine images perfectly fine if i PXE boot it but fails with that error code when using any kind of boot media with WAIK version 3.1

Are you injecting only the architecture specific (32-bit or 64-bit) drivers from the CAB into your WinPE boot media?

I also had the same issue in my SCCM Environment, here is what i did to fix it:

1) Remove all NIC/Storage Drivers from both x86 and x64 boot images and update your DPs
2) Import the Win PE Drivers and add to the Boot Images (As Warren pointed out, make sure you are not going cross-architecture as it will fail)
**Important: Make sure to also import all the Mass Storage Drivers from this package into your Boot Image as well, some of the new storage controllers are not part of the Default WinPE Driver set**
3) Update DPs then image

You should take a look at what systems are supported by the WinPE package to make sure the systems in your environment are listed. I'm lucky in that the systems i support are primarily Dell, only a couple one-off devices from other manufacturers.

To limit your variables, remove all drivers from your WinPE boot package and only add the NIC driver. It is the only driver required by WinPE to image the new Exx20 systems.

"Are you injecting only the architecture specific (32-bit or 64-bit) drivers from the CAB into your WinPE boot media? "

Yes I am injecting the architecture specific 64 bit driver's into my boot.wim

"I also had the same issue in my SCCM Environment, here is what i did to fix it:

1) Remove all NIC/Storage Drivers from both x86 and x64 boot images and update your DPs
2) Import the Win PE Drivers and add to the Boot Images (As Warren pointed out, make sure you are not going cross-architecture as it will fail)
**Important: Make sure to also import all the Mass Storage Drivers from this package into your Boot Image as well, some of the new storage controllers are not part of the Default WinPE Driver set**
3) Update DPs then image

You should take a look at what systems are supported by the WinPE package to make sure the systems in your environment are listed. I'm lucky in that the systems i support are primarily Dell, only a couple one-off devices from other manufacturers."

I removed the NIC and storage drivers from my x64 boot image 3.1 (We now only deploy x64) and updated DSP.
I imported all the drivers that come in the Dell Win-PE-Drivers-A05.cab for x64 architecture and updated DSP.
I was unable to locate any additional mass storage drivers for the E6420 or E6320 models to import as well that did not come in the WINPE cab. Can a missing mass storage driver cause this error?
All the systems I support are dell.

Still not sure where to go next with this and am still receiving the same error ( 0x8004005) after doing all of the above.

"To limit your variables, remove all drivers from your WinPE boot package and only add the NIC driver. It is the only driver required by WinPE to image the new Exx20 systems. "

Hi Warren,

This solution has worked for the Exx20 series laptop's. I also have the need to deploy 780 and 790 series desktops with the same WinPE boot image. If you could provide me the same information including what drivers are required to do this, I will just add those instead of importing the entire PE pack and risk breaking my boot media's ability to deploy Exx20 series laptops again. I only need the ability to deploy Windows 7 SP1 x64 and therefore only need a complete/working boot.wim for the x64 architecture.
Thanks

The 780 and 790 may use the same NIC driver as the Exx20 but I don't have that information in front of me. If not, just add the appropriate NIC driver for that platform.

"The 780 and 790 may use the same NIC driver as the Exx20 but I don't have that information in front of me. If not, just add the appropriate NIC driver for that platform."

The 780 does in fact use the same NIC driver. I don't have a 790 in yet to try it but there are a few on order. Thanks for all your help! This is now fully working for us.

I am having almost identical frustrating issues! I imported "Dell Client WinPE Boot Image (A04) x86" using the Dell Boot Image Wizard and I could no longer complete a Task Sequence. It looks like the WMI package is missing from the Boot Image. My Build and Capture works up to the WinXP setup final reboot. It reboots itself then fails to restart the SCCM Boot WinPE with the following Task Sequence error -



Loading the Task Sequencing Environment from "C:\_SMSTaskSequence\TSEnv.dat". OSDSetupHook 14/07/2011 12:41:09 1380 (0x0564)
Environment scope "Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}" successfully created OSDSetupHook 14/07/2011 12:41:09 1380 (0x0564)
Environment scope "Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}" successfully created OSDSetupHook 14/07/2011 12:41:09 1380 (0x0564)
CoCreateInstance(CLSID_WbemLocator, 0, CLSCTX_INPROC_SERVER, IID_IWbemLocator, (LPVOID *) &pIWBEMLocator), HRESULT=80040154 (e:\nts_sms_fre\sms\framework\osdmessaging\libmachineinfo.cpp,239) OSDSetupHook 14/07/2011 12:41:10 1380 (0x0564)
CCM::SMSMessaging::GetSmbiosID(sFileKey), HRESULT=80040154 (e:\nts_sms_fre\sms\framework\tscore\environmentlib.cpp,126) OSDSetupHook 14/07/2011 12:41:10 1380 (0x0564)
LoadFromFile(sEnvPath, shXml), HRESULT=80040154 (e:\nts_sms_fre\sms\framework\tscore\environmentlib.cpp,734) OSDSetupHook 14/07/2011 12:41:10 1380 (0x0564)
Failed to load environment from C:\_SMSTaskSequence\TSEnv.dat (80040154) OSDSetupHook 14/07/2011 12:41:10 1380 (0x0564)
SharedEnvironment.loadEnvironment( sTSEnvDataFile ), HRESULT=80040154 (e:\nts_sms_fre\sms\client\osdeployment\osdgina\basesetuphook.cpp,251) OSDSetupHook 14/07/2011 12:41:10 1380 (0x0564)
Failed to load the Task Sequencing Environment object from "C:\_SMSTaskSequence\TSEnv.dat". Code(0x80040154) OSDSetupHook 14/07/2011 12:41:10 1380 (0x0564)

Experienced a similiar issue with for the 82579LM driver but it was for a HP 2560p.. WIN PE does not like the "HP" drivers.. I had to goto Intel downloaded the prowin32(its a XP system)... You can actually extract the files using.... prowin32.exe /s /e /f . Once extracted, I injected them into a seperate boot image(I didnt want to break what is working already) If you need the 64 Bit drivers you can download the Prowin64.exe