Cannot complete installation as drivers are missing.

[Bordonbert]

Hi. I'm trying to set up an old Dell e6220 laptop for Win7 64bit use. The reason I have gone so old is to exclusively host auto diagnostic software which requires an older OS. I have finally managed, after two days of fighting with USB sticks, to install Win7 and it runs fine - sort of. However, there are a good few devices which are missing drivers. Included in these are the network and wifi controllers. I have the drivers from Dell's support website and can transfer them to the laptop but they do not run for installation, they give a "System32.dll - no entry point" error.

So I need to install Win7 updates as a starting point but in short, I can't get online or even onto my own home network to correct anything which seems to be exclusively the advice that everything in Windows tells me to do. Can anyone advise on this?

Devices missing drivers are: Broadcom USH; DW5550; Ethernet Controller; Mass Storage Controller; Network Controller, PCI Simple Communications Controller; SM Bus Controller. All show in Device Manager with the yellow pling and drivers not installed and none of them can identify themselves with more info than that. They are just listed with those names and as Unknown Device in their Properties.

As I said above, I have tried running the driver packages downloaded from Dell to install them but that System32.dll entry point error stops all of them running.

 

[torchwood]

for starters run sfc /scannow
then from the ms catalogue kb947821

 

[Bordonbert]

Thanks for the heads up Torchwood. I've run sfc /scannow but it comes back with 100% verification. However, what I find odd is that I can't find system32.dll anywhere in the installation. I started looking in the usual Windows/System32 folder but it is nowhere else I can see either. And it doesn't show up in the installation media either. (That's on a USB external HDD formatted and set up by Rufus specifically for the job as I had no end of troubles with memory sticks.) That may not be unusual of course as it may still be packed inside some container.

I've also looked into the registry at HKEY_LOCAL_MACHINE/Software/Microsoft/CurrentVersion/SharedDLLs and it isn't listed. However, it isn't listed there in my Win10 normal working installation either. I've downloaded Microsoft's Listdlls64.exe and I'm going to run that on the Win7 laptop and see what comes up.

Any other thoughts would be welcome.

- - - Updated - - -

Well I've loaded up and run Listdlls.exe and Listdlls64.exe and they don't really help me. They report on the dlls currently loaded by running processes and cannot seem to just list all registered dlls. System32.dll is not amongst the listed ones of course. I'm now planning a repair or reinstall from a different .iso (X17-459465.iso which says it includes SP1) despite the sfc result of 100% correct.

- - - Updated - - -

Just for the record, that X17-459465.iso only installs Windows 7 Ultimate. At no time are you asked which version of Win7 you want to install. If you have a product key as I do it will not register in the setup if it is for a different version. Back to my original Win7_64_bit.iso.

- - - Updated - - -

Thought this latest set of issues would warrant a new post in the thread.

I've reinstalled Win7 Pro from my original .iso and it is now back in place. The product key is recognised and accepted this time round. I've also dredged through Dell's support area for updates and drivers. My support code number found on the Dell tag on the laptop case is not recognised as it is now a legacy product so it has to be identified by its model number. There are a shed load of downloads available and I have no idea as to which apply. I've seen the Dell article on installing in the correct order now so I tried to address this logically. First off they say "Dell System Utilities". That offers 3 downloads so I took the 2 which were marked "Recommended" and transferred them to the new install.

"Dell Command | Power Manager" reports the error "The procedure entry point AddDllDirectory could not be located in the dynamic link library Kernel32.dll". "Dell System Software Utility DSS_UTIL_WIN_R282538.EXE" bombs out with "This installation package is not supported by this processor type" error. This looks as though these installer/updater files are not compatible with my version of Windows at all. If such baseline files as Kernel32.dll and System32.dll don't relate in terms of entry points then something is wrong somewhere.

Has anyone out there any knowledge of what is happening here?

- - - Updated - - -

Incidentally, Dell support won't let me in to get help as my legitimate Service Number which is on the original tag on the machine is not recognised now!

 

[dg1261]

There are a shed load of downloads available and I have no idea as to which apply. I've seen the Dell article on installing in the correct order now so I tried to address this logically. First off they say "Dell System Utilities".

Some people like to install every available driver, while others prefer to install only the minimum required. I certainly won't quibble with the opinions of others, but I fall into the latter camp. I never install "Dell System Utilities" nor "Power Manager" as they're not required and don't really serve a need for most users.

That means on the E6220 drivers page I would only look at the categories: Chipset, Audio, Video, Ethernet (Network/Ethernet/Wireless), and Touchpad and Card Reader (Mouse/Keyboard/Input).

You're also going to need a driver for your wifi card, but laptops were shipped with so many different choices it may be difficult to sort out which driver you need. Don't just install them all because it just messes up your nice, clean system with superfluous junk.

If it helps, note you can also download a single archive of all drivers here. Scroll down to the E6220 ("E3 Latitude Family"), and download the A02 file. It's in .cab format, but a utility like 7-Zip should be able to extract it while preserving the structure of nested folders. It will extract to a set of nested folders around 1.5 GB in size. (Do NOT extract with Windows Explorer -- that will dump everything into a single folder and won't preserve the folder structure!)

When you come across a device in Device Manager that you can't identify, just tell Device Manager to search your computer for an updated driver, and point it at the folders extracted from the .cab archive. Device Manager should then find what it needs somewhere in that mass.

Note you must install the Chipset drivers manually -- preferably, first. That's because there are some devices that Device Manager won't even see until the Chipset drivers reveal them.

 

[SIW2]

I have never heard of system32.dll it is not on my system

at the minimum you want media that already includes SP1

then preferably update it
Update your Win 7 installation media

Intel(R) 82579LM Gigabit Network Connection
Operating Systems: Windows 7 x64
Device ID: PCI\VEN_8086&DEV_1502&SUBSYS_04A91028&REV_04
File *.inf: E1C62x64.inf
Category: Intel.NTamd64.6.1.1
:ar: https://dl.driverpack.io/driverpack...el-FORCED-7x64-PRO1000-Dell_12.17.8.7-drp.zip

DW1530 Wireless-N WLAN Half-Mini Card
Operating Systems: Windows 7 x64
Device ID: PCI\VEN_14E4&DEV_4359&SUBSYS_00111028&REV_00
File *.inf: bcmwl6.inf
Category: BROADCOM.NTamd64.6.1
:ar: https://dl.driverpack.io/driverpack...om-FORCED-7x64-BCM43_6.30.223.215_sub-drp.zip


Drivers can also be obtained using SDI. If you have internet connection you just need the small package . If no internet connection you could download the very big package via torrent client on another machine and transfer it to the e6220 via usb stick
Snappy Driver Installer Origin – Glenn's Page

dell has a .cab with the drivers for that machine
https://dl.dell.com/FOLDER01449232M/1/E6220-win7-A08-0VK93.CAB

https://www.dell.com/support/home/en-uk/drivers/driversdetails?driverid=0vk93

 

[Bordonbert]

Well! Things have moved on - a lot. The major problem was an odd one. With all of these difficulties in finding so many driver systems I rechecked my installation. Despite downloading a 64 bit .iso I had a 32 bit installation. From my work in programming I'm used to generally working with software so I am well aware of how to get this right so I rechecked. The same .iso I downloaded was definitely labelled as a 64 bit version. I have no idea how to account for that but it surely must be down to user error in some way. Anyway, with a successful procedure now mapped out reinstalling was quick and clean, and it included SP1. It produced the same problem of the same clutch of missing drivers.

Thanks to Torchwood for kickstarting the assistance, and with the advice from DG1261 and SIW2 I got my hands on the correct .cab when I couldn't seem to locate that directly from Dell's site. Downloading it to my working PC was fine and quick, extraction took an age to complete and I mean hours. However, complete it did and I transferred it to the laptop. Well whaddya know? The devices all installed with the exception of the wireless card which started but bombed out saying it couldn't find a file. Another restart fixed that and everything eventually went through as it should.

The oddities are obvious but curious. How did I install the wrong version of Win7? (Why the Hell didn't I check after the install? It was very very late by then and I was falling asleep but no excuse.) I can't imagine where I went wrong with that, I was sure to select the 64 bit .iso and there were no version options offered during the install. Why are both my support numbers not recognised by Dell? They are there clearly printed on the correct tag on the laptop case along with the Windows 7 Pro key. Do they simply run out when the machine is no longer supported? I would have thought that simpler legacy issues like this one would still be open to a little simple courteous assistance with no obligation to solve every problem and the support code is the way to identify and automate what is needed.

A tip for others who may come across this and have similar problems. My first mistake was in using non-top flight USB memory sticks for the initial Win7 install. I tried 4 basic ones and could not get any of them to work reliably with this task. All were big enough and all work for other simpler tasks. They scanned error free but even using Rufus to create the bootable versions was flaky and often faulted. I ended up using a small external USB HDD purloined from my old TV box that I reformatted! I had no more creation or transfer problems after that and the install became totally reliable, (I did it enough times to be able to say that). If you have similar issues look at your USB memory device!

Anyway, I can't thank all of you who responded with such great advice enough. You really pulled my proverbial plums out of the proverbial fire. I'm off to install the diagnostic software I wanted the machine to host. Those issues will be a different kettle of fish. Also, apologies for my writing long posts in plain English which often irritates those who seem to live by the second. I know a short simple couple of sentences with no punctuation and hosts of slang is usual on internet forums nowadays. I always think that giving more info than you feel is needed and being polite and friendly is better than calling everyone "like dood" and giving a one line uninformative description so anyone who does respond has to drag information out of the poster a piece at a time is not the easiest way to help someone. It also helps future readers looking for their own answers to get data within threads more quickly.

So thanks again and good luck to others with similar issues.