Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

Updequest

1 Rookie

 • 

48 Posts

421202

April 11th, 2011 08:00

Problem with E6420 and Dell Driver Pack .cab

I have downloaded the Dell Driver pack ver A00 for the E6420, extracted the contents and created a Windows 7 x64 driver package for SCCM OSD. When I deploy the driver pack in the task sequence I have issues with two drivers.
1. Nvidia NVS 4200M does not pnp and does not exist in the windows 7 file repository. If I try and point the device to the source inf folder, it fails to install. Seems like this driver may have some issues in the .cab file. I can get this device installed by downloading the driver individually, extracting it, and pointing it to the extracted inf file. I am importing this one into my driver pack to see if it will work.
2. The HECI drivers will not install at all. The device will show as a PCI Simple Communications Controller. If you try and point it to the inf, it will give the error "Windows found the driver for your device but encountered an error trying to install it".

Any ideas on the HECI driver?

DELL-Warren B

1.1K Posts

July 15th, 2011 13:00

The problem still exists and Nvidia is onsite this week working on the issue. Hope to have it resolved soon.

ChrisClemson

1 Message

July 29th, 2011 06:00

"Called up support and after a couple hours we found a solution. We had to go to the Intel site and download the latest chipset drivers to resolve the issue on all noted platforms: http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=20018&keyword=%22series+6+chipset%22&lang=eng"
Thanks for your link ScubDubba.
I had exactly the same problem with an HP 8200 desktop and an HP 8460p laptop.
The drivers linked from HP are build 1015, yours are 1030.

Chris

orgwizard

12 Posts

July 29th, 2011 08:00

so we're about to enter August.
did anything come of the NVIDIA visit?

DELL-Warren B

1.1K Posts

July 29th, 2011 14:00

yes, they made some headway but final validation has not been complete. I'll post here, when a new driver has been validated and is being scheduled for release.

NickolajA

8 Posts

August 1st, 2011 08:00

We're experincing the same problem with our E6420 not installing the Nvidia NVS 4200M driver.

orgwizard

12 Posts

August 1st, 2011 12:00

yet another issue...though on the same topic.
I wrote a program that creates drivers packs for offline use, so we can do OS builds without a network connection. Usually works out fine, but looks like the Intel chipset driver in this thread is stumbling.
while the solution works to just add the newer chipset driver from intel, to the driver store, when my program looks at it, it's getting confused.
Apparnetly, while the new intel chipset driver is 9.2.0.1030, if you actually look in the cougme.inf file, it actually has a version number of 1.2.0.1030. so my app acutally things this is an older driver than the bad one referenced in this thread, and therefore skips it.
wonder if this was intentional on Intel's part or on purpose...but looks like a mistake given Intel is advertising this as 9.2.0.1030. If Dell's go their ear, might want to bring this up.

NickolajA

8 Posts

August 2nd, 2011 07:00

"We're experincing the same problem with our E6420 not installing the Nvidia NVS 4200M driver."
I solved my problem by createing a package with drivers from nvidia.com, version 275.33 and then running a "Run command line" step with the following command line "setup.exe /s /n /noeula /nofinish". Remember to add a success code of "1" under the Options tab in the field called Success Codes. In the end of my task sequence, I added a "Run command line" step with the following command line "winsat.exe dwm" to enable Aero etc. I also added a WMI Query condtion to only target the specific systems needed. This query looks like "SELECT * FROM Win32_ComputerSystem WHERE Model Like '%E6420%'".

Thanks to some of the guys here for helping me resolving my issue. I hope that this helps somebody.

DELL-Warren B

1.1K Posts

August 29th, 2011 23:00

wallends

1 Message

September 12th, 2011 09:00

"I got the HECI device to install by changing the following line in the HECI.inf. It breaks the signing of the driver, but it gets past the error I was getting which indicated that a service with the same name was already installed.

I added the "AMT" to the service name.

HECI_SvcDesc = "Intel(R) AMT Management Engine Interface"

Give that a try and I'll report it to the driver team.

Thanks,

Warren"
I was working on a Dell 990 installing drivers for WinXP and ran into the same issue. Simple Communication Controller had an exclamation mark. I followed Warren Byle's notes and added AMT to the HECI service name and reinstalled the driver, but that did not make the exclamation mark go away in Device Manager.

So I added AMT to another line and that fixed it. Under Service section of the HECI.inf file:
DisplayName = %HECI_AMT_SvcDeSc%

Not sure if doing this actually renders the driver useless? But it installs fine now.

DELL-Warren B

1.1K Posts

September 12th, 2011 11:00

You can double check to see if the service was renamed.

checks7

1 Message

October 5th, 2011 09:00

Has anyone found a fix for the issue with HECI.inf where does not get installed during PnP and OS presents a device error 'PCI Simple Communications Controller' device driver not installed. If you follow the recommendation in posting #9 by changing the service name, the device installs correctly, be it you get an error message basically saying the driver signing is broken.
Is there an updated HECI.inf available either by Dell or Intel that corrects this issue?
Regards

orgwizard

12 Posts

October 5th, 2011 10:00

out quick solution for that one was what one of the other posters recommended...get the latest driver version from intel.

DELL-Warren B

1.1K Posts

October 5th, 2011 11:00

I believe the updated Intel chipset driver addresses it. It should be included in the recently released version of the CABs.

kubasa

22 Posts

February 23rd, 2012 08:00

While looking for a solution for my OptiPlex 390, I stumbled across this today and the Intel download solved it for me.  Thanks!

HumbleSage

1 Rookie

 • 

14 Posts

April 17th, 2013 13:00

Just in case anyone else is still having this problem, I encountered the same issue installing drivers straight from the support site for 2 Dell Latitude E5510.

I used a standard Windows 7 x64 corporate build I made and after the install was left with 3 devices that needed drivers. They were the Free Fall Sensor, The Wireless Card (Intel), and this PCI Controller problem you are discussing here. Editing the HECI.inf as described by Updequest resolved my issue with this HECI component after it changed to "unknown device" after installing the Intel ME drivers.

Windows thinks the driver is unsigned but that's a given since we  manually edit the inf and it fails verification.

Thanks for this fix. (Feel free to move this post or copy if necessary)

- Rob

Was this post helpful?

View All

No Events found!

Top