Intel INF drivers, why do they not install correctly?

hyperst

hyperst

hyperst

Soldato
Joined
16 Dec 2008
Posts
4,086
Location
Lincolnshire
I remembered this problem before, well not so much a problem just an annoyance with the Intel INF drivers, in Windows 7, I thought I had installed them fine and everything worked fine, a bit of reading around and I see a post mentioning how to install them correctly, by using the Run command and pointing it to the driver package and adding ''-overall'' to the end of the run box (without the quotes) and it did load and install much more than before.

Well I have been using Windows 8 since release and forgot all about the above until last night when I remembered what I had done with 7, and guess what, same again, the drivers I thought I had installed correctly had not, I use the run box with that command at the end and it installs a load more:), check my WEI score and re-run it and my CPU is now 8.3 where as it was 8.1, so an improvement for very little hassle, but hassle I shouldn't have had, so just why is it that Intel INF drivers never install correctly?
 
The INFs only update the components that need updating, so a newer INF may only contain mostly older drivers with one or two components that have changed.... Intel just package them together in one package for those who haven't updated in a while.

Your command line just forces it to re-install drivers that were already installed.
 
But they wasn't installed, the drivers that was being used was Microsoft drivers from 2006, now I am using drivers labeled with a date of 2012 and manufacturer Intel.
 
Nearly all Intel s/w does this and have various switches to force it to use all the drivers in the package. For all of them do what you where doing above but put -? as the only switch at the end. It should then pop up a box showing all the switches for that installer.

Not sure how much difference it makes but as you say it does change them from the in box MS ones to the 'latest' Intel branded ones.

Even if it doesn't make any difference I always prefer to do it this way, probably just psychological but if I'm running the installer anyway it doesn't take that long to just add the switch and let it install the lot.

Put it this way, they shouldn't be older or worse than the MS ones. They are either the same but with a different date etc or they are newer.
 
oXz4gvDPCa.png


Some of the one's labelled Intel was not like that before for me, the LPC I think was a microsoft driver and some others, you should have seen it install a load more, if you had installed before and tried to install without adding -overall it would usually not show any installed, so I know it did install more for me.

I just find it odd that they don't install when running the package normal, as I said above my CPU score went from 8.1 to 8.3, so they must be doing something, I have a feeling it will improve transfer speeds from my camera as it is quite slow compared to Windows 7, just got to try it now.
 
Last edited:
ok, though so. This did come up before in another thread.
Try this in powershell before and after forcing the install with the switch, if you haven't already installed them that way.

Code: 
gwmi Win32_PnPSignedDriver | where {$_.DeviceName -like "*Intel*"} | select DeviceName,DriverVersion,DriverDate,DriverProviderName | sort DeviceName | ft -a

Might need to make the window wider to get all the output, or use the ISE. Then compare the two outputs, see if you see a difference.
 
I did that, but I have all ready installed it with the overall on the end of it:)
DeviceName DriverVersion DriverDate Driv
erPr
ovid
erNa
me
---------- ------------- ---------- ----
Intel Processor 6.2.9200.16451 20090421000000.******+*** M...
Intel Processor 6.2.9200.16451 20090421000000.******+*** M...
Intel Processor 6.2.9200.16451 20090421000000.******+*** M...
Intel Processor 6.2.9200.16451 20090421000000.******+*** M...
Intel Processor 6.2.9200.16451 20090421000000.******+*** M...
Intel Processor 6.2.9200.16451 20090421000000.******+*** M...
Intel Processor 6.2.9200.16451 20090421000000.******+*** M...
Intel Processor 6.2.9200.16451 20090421000000.******+*** M...
Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 1 - 1E10 9.3.0.1026 20120111000000.******+*** I...
Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 5 - 1E18 9.3.0.1026 20120111000000.******+*** I...
Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 8 - 1E1E 9.3.0.1026 20120111000000.******+*** I...
Intel(R) 7 Series/C216 Chipset Family SMBus Host Controller - 1E22 9.3.0.1025 20120510000000.******+*** I...
Intel(R) 7 Series/C216 Chipset Family USB Enhanced Host Controller - 1E26 9.3.0.1025 20120510000000.******+*** I...
Intel(R) 7 Series/C216 Chipset Family USB Enhanced Host Controller - 1E2D 9.3.0.1025 20120510000000.******+*** I...
Intel(R) 82579V Gigabit Network Connection 12.2.46.0 20121126000000.******+*** I...
Intel(R) 82802 Firmware Hub Device 6.2.9200.16384 20060621000000.******+*** M...
Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller 11.7.0.1013 20121119000000.******+*** I...
Intel(R) Management Engine Interface 8.1.10.1275 20121207000000.******+*** I...
Intel(R) Z77 Express Chipset LPC Controller - 1E44 9.3.0.1026 20120111000000.******+*** I...
 
I never run the setup. I always go into device manager and update manually.
Point the update to look in
C:\Users\Name\Downloads\INF_Win8-64_Win8_Win7-64_Win7_Vista64_Vista_XP64_XP(v9.3.0.1025)\INF(v9.3.0.1025)\All

It always update them for me this way.
 
You must log in or register to reply here.
Back
Top Bottom