Corsair K57 RGB Wireless keyboard review
AMD Ryzen 7 3800X review
PowerColor 5700 RED DEVIL review
MSI Radeon RX 5700 XT Evoke review
ASUS Radeon RX 5700 XT ROG STRIX review
ViewSonic Elite XG240R Monitor Review
Promo: URCDKey Summer Sale Windows 10 Pro for $11
X570 Aorus master review
Cooler Master Silencio S600 review
AMD Ryzen 5 3400G review
Intel Chipset Software Installation 10.1.2.8 WHQL Download
on: 07/21/2015 06:07 PM [ 9 comment(s) ]
Advertisement
Download the Intel Chipset Software Installation 10.1.2.8 WHQL driver. This this one actually updates a lot of things.
The Intel Chipset Software Installation Utility installs the Windows* INF files. The INF files inform the operating system how to properly configure the chipset for specific functionality, such as USB and core PCI.
- Extract setup.exe from .zip folder to a new folder on desktop
- Create a desktop shortcut to the .exe
- Add -overall to end of target line it should look something like this
| "C:\Users\**YOURPCNAME**\Desktop\New folder\SetupChipset.exe" -overall |
- Right click shortcut and select "Run As Administrator.
- Follow install instructions and reboot PC when installation finishes.
Intel® Atom/Celeron/Pentium Processor -Intel Core M processor family -5th Generation Intel Core™ processor family -4th Generation Intel Core processor family -3rd Generation Intel Core processor family -2nd Generation Intel Core processor family -Intel 9 series chipset -Wellsburg -Patsburg - Intel 6th Gen Intel Core and Intel 100 Series chipset
Run this easy to use Intel Driver Update Utility and it will automatically tell you if you need to update your chipset INF file, and if so, will prompt you to install and you are done. This will save you a lot of time not only on your chipset download but the most common files needed for your system.
Intel Chipset Device Software is the new name for the Intel Chipset Software Installation Utility; this name will be seen when running the installation package.
The Intel Chipset Device Software installs the Windows* INF files. An INF is a text file that provides the operating system with information about a piece of hardware on the system. In the case of the current Intel Chipset Device Software, that information is primarily the product name for the piece of hardware. This allows the operating system to show the correct name for that piece of hardware in Device Manager.
OS support:
- Microsoft Windows* Server 2008 x64
- Microsoft Windows* 7
- Microsoft Windows* 7 x64
- Microsoft Windows* Server 2008 R2 x64
- Microsoft Windows* 8
- Microsoft Windows* 8 x64
- Microsoft Windows* Server 2012 x64
- Microsoft Windows* 8.1
- Microsoft Windows* 8.1 x64
- Microsoft Windows* Server 2012 R2 x64
- Microsoft Windows* 10 x64
- Microsoft Windows* Server Threshold x64
Agent-A01
Senior Member
Posts: 11351
Joined: 2010-12-27
Senior Member
Posts: 11351
Joined: 2010-12-27
#5128043 Posted on: 07/24/2015 12:04 AM
This adds drivers to X99 platform, previously x99 didnt have any
This adds drivers to X99 platform, previously x99 didnt have any
thatguy91
Senior Member
Posts: 6648
Joined: 2010-08-27
Senior Member
Posts: 6648
Joined: 2010-08-27
#5128126 Posted on: 07/24/2015 03:36 AM
It all depends on the Windows version and what chipset you have. The newer the chipset, the more likely you will need it to correctly identify all Intel devices on Windows 8.1 and especially 7. Windows 10 should support most, if not all, current Intel chipsets and devices covered by the inf 's.
When the device is already properly identified this will simply change the device description, version, and date. They are null drivers, meaning no payload. Any apparent payload in device manager is because some of the included inf's act as an extension to the system machine.inf.
The 'real' Intel drivers are things like the performance AHCI driver (you don't need the application part) or the Management Engine Interface driver (again you only need the driver), both of these are separate downloads. There are one or two other proper Intel drivers depending on the OS and chipset.
What important things does it update? Most people seem to claim installing these is pretty useless. I personally always like to have the latest drivers even if they don't do much lol.
It all depends on the Windows version and what chipset you have. The newer the chipset, the more likely you will need it to correctly identify all Intel devices on Windows 8.1 and especially 7. Windows 10 should support most, if not all, current Intel chipsets and devices covered by the inf 's.
When the device is already properly identified this will simply change the device description, version, and date. They are null drivers, meaning no payload. Any apparent payload in device manager is because some of the included inf's act as an extension to the system machine.inf.
The 'real' Intel drivers are things like the performance AHCI driver (you don't need the application part) or the Management Engine Interface driver (again you only need the driver), both of these are separate downloads. There are one or two other proper Intel drivers depending on the OS and chipset.
Agent-A01
Senior Member
Posts: 11351
Joined: 2010-12-27
Senior Member
Posts: 11351
Joined: 2010-12-27
#5128140 Posted on: 07/24/2015 05:28 AM
It all depends on the Windows version and what chipset you have. The newer the chipset, the more likely you will need it to correctly identify all Intel devices on Windows 8.1 and especially 7. Windows 10 should support most, if not all, current Intel chipsets and devices covered by the inf 's.
When the device is already properly identified this will simply change the device description, version, and date. They are null drivers, meaning no payload. Any apparent payload in device manager is because some of the included inf's act as an extension to the system machine.inf.
The 'real' Intel drivers are things like the performance AHCI driver (you don't need the application part) or the Management Engine Interface driver (again you only need the driver), both of these are separate downloads. There are one or two other proper Intel drivers depending on the OS and chipset.
These are no longer null drivers
It all depends on the Windows version and what chipset you have. The newer the chipset, the more likely you will need it to correctly identify all Intel devices on Windows 8.1 and especially 7. Windows 10 should support most, if not all, current Intel chipsets and devices covered by the inf 's.
When the device is already properly identified this will simply change the device description, version, and date. They are null drivers, meaning no payload. Any apparent payload in device manager is because some of the included inf's act as an extension to the system machine.inf.
The 'real' Intel drivers are things like the performance AHCI driver (you don't need the application part) or the Management Engine Interface driver (again you only need the driver), both of these are separate downloads. There are one or two other proper Intel drivers depending on the OS and chipset.
These are no longer null drivers
thatguy91
Senior Member
Posts: 6648
Joined: 2010-08-27
Senior Member
Posts: 6648
Joined: 2010-08-27
#5128179 Posted on: 07/24/2015 08:27 AM
Yes they are
, check them out for yourself! They are all basically the same, but with different hardware ID's and devices.
Here is one for Ivy Bridge:
I want to draw your attention to the top, where Intel even claims they are null drivers for yellow bang removal in device manager, and brands Intel devices. The last one is the key statement as to why it changes the device in device manager, for branding.
Further down the list you will see it links to machine.inf, which is the Microsoft system device inf. So, in the device manager for
Every other inf in this 'driver' is the same principle, either linking to the existing machine files or are just descriptor files. This is why they are 'null' drivers. Even if it does remove the yellow bang from the device in device manager, this is simply because the device wasn't out when the last update to the system machine.inf occurred.
Non null drivers are the proper AHCI driver, the proper MEI driver, Intel network drivers, and under Windows 7 since it doesn't natively have support for them, the Intel USB 3.0 driver and the Intel Serial IO driver (not sure what this does, but there is a Windows 7 driver for it, the latest of which is for Skylake).
These are no longer null drivers
Yes they are
, check them out for yourself! They are all basically the same, but with different hardware ID's and devices.
Here is one for Ivy Bridge:
; ************************************************************
; ************************************************************
; ** Filename: IvyBridgeSystem.inf **
; ** Abstract: Assigns the null driver to devices **
; ** for yellow-bang removal and **
; ** brands Intel(R) devices **
; ************************************************************
; ************************************************************
Signature=$WINDOWS NT$
Class=System
ClassGUID={4D36E97D-E325-11CE-BFC1-08002BE10318}
Provider=%INTEL%
CatalogFile=IvyBridge.cat
DriverVer=07/01/2015, 10.1.2.8
ExcludeFromSelect=*
Name=Chipset
%INTEL%=INTEL,NT,NTamd64
%PCI\VEN_8086&DEV_0150Desc%=Needs_NO_DRV, ,PCI\VEN_8086&DEV_0150
%PCI\VEN_8086&DEV_0151Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_0151
%PCI\VEN_8086&DEV_0154Desc%=Needs_NO_DRV, ,PCI\VEN_8086&DEV_0154
%PCI\VEN_8086&DEV_0155Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_0155
%PCI\VEN_8086&DEV_0158Desc%=Needs_NO_DRV, ,PCI\VEN_8086&DEV_0158
%PCI\VEN_8086&DEV_0159Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_0159
%PCI\VEN_8086&DEV_015CDesc%=Needs_NO_DRV, ,PCI\VEN_8086&DEV_015C
%PCI\VEN_8086&DEV_015DDesc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_015D
%PCI\VEN_8086&DEV_0150Desc%=Needs_NO_DRV, ,PCI\VEN_8086&DEV_0150
%PCI\VEN_8086&DEV_0151Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_0151
%PCI\VEN_8086&DEV_0154Desc%=Needs_NO_DRV, ,PCI\VEN_8086&DEV_0154
%PCI\VEN_8086&DEV_0155Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_0155
%PCI\VEN_8086&DEV_0158Desc%=Needs_NO_DRV, ,PCI\VEN_8086&DEV_0158
%PCI\VEN_8086&DEV_0159Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_0159
%PCI\VEN_8086&DEV_015CDesc%=Needs_NO_DRV, ,PCI\VEN_8086&DEV_015C
%PCI\VEN_8086&DEV_015DDesc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_015D
Include=machine.inf
Needs=NO_DRV
Include=machine.inf
Needs=NO_DRV.Services
Include=machine.inf
Needs=PCI_DRV
Include=machine.inf
Needs=PCI_DRV.Services
Include=machine.inf
Needs=PCI_DRV.HW
INTEL="INTEL"
PCI\VEN_8086&DEV_0150Desc="Xeon(R) processor E3 - 1200 v2/3rd Gen Core processor DRAM Controller - 0150"
PCI\VEN_8086&DEV_0151Desc="Xeon(R) processor E3 - 1200 v2/3rd Gen Core processor PCI Express Root Port - 0151"
PCI\VEN_8086&DEV_0154Desc="3rd Gen Core processor DRAM Controller - 0154"
PCI\VEN_8086&DEV_0155Desc="Xeon(R) processor E3 - 1200 v2/3rd Gen Core processor PCI Express Root Port - 0155"
PCI\VEN_8086&DEV_0158Desc="Xeon(R) processor E3 - 1200 v2 DRAM Controller - 0158"
PCI\VEN_8086&DEV_0159Desc="Xeon(R) processor E3 - 1200 v2/3rd Gen Core processor PCI Express Root Port - 0159"
PCI\VEN_8086&DEV_015CDesc="Xeon(R) processor E3 - 1200 v2/3rd Gen Core processor DRAM Controller - 015C"
PCI\VEN_8086&DEV_015DDesc="Xeon(R) processor E3 - 1200 v2/3rd Gen Core processor PCI Express Root Port - 015D"
; Copyright (c) 2003-2015 Intel Corporation
;
; ********************************************************************************
; Intel is making no claims of usability, efficacy or warranty.
; ********************************************************************************
; Information in this document is provided in connection with Intel products. No
; license, express or implied, by estoppel or otherwise, to any intellectual
; property rights is granted by this document. Intel assumes no liability
; whatsoever, and Intel disclaims any express or implied warranty, relating to
; sale and/or use of Intel products including liability or warranties relating to
; fitness for a particular purpose, merchantability, or infringement of any
; patent, copyright or other intellectual property right. Intel products are not
; intended for use in medical, life saving, or life sustaining applications.
; ********************************************************************************
; Intel Corporation disclaims all warranties and liabilities for the use of this
; document and the information contained herein, and assumes no responsibility for
; any errors which may appear in this document, nor does Intel make a commitment
; to update the information contained herein. Intel reserves the right to make
; changes to this document at any time, without notice.
; ********************************************************************************
; ********************************************************************************
;
; * Third-party brands and names are the property of their respective owners.
; ************************************************************
; ** Filename: IvyBridgeSystem.inf **
; ** Abstract: Assigns the null driver to devices **
; ** for yellow-bang removal and **
; ** brands Intel(R) devices **
; ************************************************************
; ************************************************************
Signature=$WINDOWS NT$
Class=System
ClassGUID={4D36E97D-E325-11CE-BFC1-08002BE10318}
Provider=%INTEL%
CatalogFile=IvyBridge.cat
DriverVer=07/01/2015, 10.1.2.8
ExcludeFromSelect=*
Name=Chipset
%INTEL%=INTEL,NT,NTamd64
%PCI\VEN_8086&DEV_0150Desc%=Needs_NO_DRV, ,PCI\VEN_8086&DEV_0150
%PCI\VEN_8086&DEV_0151Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_0151
%PCI\VEN_8086&DEV_0154Desc%=Needs_NO_DRV, ,PCI\VEN_8086&DEV_0154
%PCI\VEN_8086&DEV_0155Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_0155
%PCI\VEN_8086&DEV_0158Desc%=Needs_NO_DRV, ,PCI\VEN_8086&DEV_0158
%PCI\VEN_8086&DEV_0159Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_0159
%PCI\VEN_8086&DEV_015CDesc%=Needs_NO_DRV, ,PCI\VEN_8086&DEV_015C
%PCI\VEN_8086&DEV_015DDesc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_015D
%PCI\VEN_8086&DEV_0150Desc%=Needs_NO_DRV, ,PCI\VEN_8086&DEV_0150
%PCI\VEN_8086&DEV_0151Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_0151
%PCI\VEN_8086&DEV_0154Desc%=Needs_NO_DRV, ,PCI\VEN_8086&DEV_0154
%PCI\VEN_8086&DEV_0155Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_0155
%PCI\VEN_8086&DEV_0158Desc%=Needs_NO_DRV, ,PCI\VEN_8086&DEV_0158
%PCI\VEN_8086&DEV_0159Desc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_0159
%PCI\VEN_8086&DEV_015CDesc%=Needs_NO_DRV, ,PCI\VEN_8086&DEV_015C
%PCI\VEN_8086&DEV_015DDesc%=Needs_PCI_DRV,PCI\VEN_8086&DEV_015D
Include=machine.inf
Needs=NO_DRV
Include=machine.inf
Needs=NO_DRV.Services
Include=machine.inf
Needs=PCI_DRV
Include=machine.inf
Needs=PCI_DRV.Services
Include=machine.inf
Needs=PCI_DRV.HW
INTEL="INTEL"
PCI\VEN_8086&DEV_0150Desc="Xeon(R) processor E3 - 1200 v2/3rd Gen Core processor DRAM Controller - 0150"
PCI\VEN_8086&DEV_0151Desc="Xeon(R) processor E3 - 1200 v2/3rd Gen Core processor PCI Express Root Port - 0151"
PCI\VEN_8086&DEV_0154Desc="3rd Gen Core processor DRAM Controller - 0154"
PCI\VEN_8086&DEV_0155Desc="Xeon(R) processor E3 - 1200 v2/3rd Gen Core processor PCI Express Root Port - 0155"
PCI\VEN_8086&DEV_0158Desc="Xeon(R) processor E3 - 1200 v2 DRAM Controller - 0158"
PCI\VEN_8086&DEV_0159Desc="Xeon(R) processor E3 - 1200 v2/3rd Gen Core processor PCI Express Root Port - 0159"
PCI\VEN_8086&DEV_015CDesc="Xeon(R) processor E3 - 1200 v2/3rd Gen Core processor DRAM Controller - 015C"
PCI\VEN_8086&DEV_015DDesc="Xeon(R) processor E3 - 1200 v2/3rd Gen Core processor PCI Express Root Port - 015D"
; Copyright (c) 2003-2015 Intel Corporation
;
; ********************************************************************************
; Intel is making no claims of usability, efficacy or warranty.
; ********************************************************************************
; Information in this document is provided in connection with Intel products. No
; license, express or implied, by estoppel or otherwise, to any intellectual
; property rights is granted by this document. Intel assumes no liability
; whatsoever, and Intel disclaims any express or implied warranty, relating to
; sale and/or use of Intel products including liability or warranties relating to
; fitness for a particular purpose, merchantability, or infringement of any
; patent, copyright or other intellectual property right. Intel products are not
; intended for use in medical, life saving, or life sustaining applications.
; ********************************************************************************
; Intel Corporation disclaims all warranties and liabilities for the use of this
; document and the information contained herein, and assumes no responsibility for
; any errors which may appear in this document, nor does Intel make a commitment
; to update the information contained herein. Intel reserves the right to make
; changes to this document at any time, without notice.
; ********************************************************************************
; ********************************************************************************
;
; * Third-party brands and names are the property of their respective owners.
I want to draw your attention to the top, where Intel even claims they are null drivers for yellow bang removal in device manager, and brands Intel devices. The last one is the key statement as to why it changes the device in device manager, for branding.
Further down the list you will see it links to machine.inf, which is the Microsoft system device inf. So, in the device manager for
Xeon(R) processor E3 - 1200 v2/3rd Gen Core processor PCI Express Root Port - 0151
it appears it loads a driver (pci.sys), but in fact it is just loading the pci.sys as defined in the machine.inf file. So, what the driver does is nothing more than change the system descriptor for the file to the Intel branded one.
Every other inf in this 'driver' is the same principle, either linking to the existing machine files or are just descriptor files. This is why they are 'null' drivers. Even if it does remove the yellow bang from the device in device manager, this is simply because the device wasn't out when the last update to the system machine.inf occurred.
Non null drivers are the proper AHCI driver, the proper MEI driver, Intel network drivers, and under Windows 7 since it doesn't natively have support for them, the Intel USB 3.0 driver and the Intel Serial IO driver (not sure what this does, but there is a Windows 7 driver for it, the latest of which is for Skylake).
snorge
Senior Member
Posts: 122
Joined: 2012-08-12
Senior Member
Posts: 122
Joined: 2012-08-12
#5128438 Posted on: 07/24/2015 06:00 PM
It all depends on the Windows version and what chipset you have. The newer the chipset, the more likely you will need it to correctly identify all Intel devices on Windows 8.1 and especially 7. Windows 10 should support most, if not all, current Intel chipsets and devices covered by the inf 's.
Well I have z97, I always see beta chipset drivers posted on station drivers but never know whether I should bother installing them. Since Windows 10 comes out next week I will probably wait until then and download the latest of everything at the same time.
It all depends on the Windows version and what chipset you have. The newer the chipset, the more likely you will need it to correctly identify all Intel devices on Windows 8.1 and especially 7. Windows 10 should support most, if not all, current Intel chipsets and devices covered by the inf 's.
Well I have z97, I always see beta chipset drivers posted on station drivers but never know whether I should bother installing them. Since Windows 10 comes out next week I will probably wait until then and download the latest of everything at the same time.
sfektsz
Member
Posts: 48
Joined: 2015-01-20
Member
Posts: 48
Joined: 2015-01-20
#5128504 Posted on: 07/24/2015 08:15 PM
OP; why do you recommend using -overall when installing it? I've seen many people advise against doing so. Example: http://www.win-raid.com/t895f42-Intel-Chipset-Device-quot-Drivers-quot-INF-files.html
OP; why do you recommend using -overall when installing it? I've seen many people advise against doing so. Example: http://www.win-raid.com/t895f42-Intel-Chipset-Device-quot-Drivers-quot-INF-files.html
xomniversex
Junior Member
Posts: 3
Joined: 2012-09-04
Junior Member
Posts: 3
Joined: 2012-09-04
#5136094 Posted on: 08/05/2015 12:26 AM
z68 user here on Windows 10.
Installed these and it caused a myriad of issues including my AMD GPU drivers no longer functioning - even when reinstalled - no 3D acceleration at all after installing.
Had to use system restore to undo them since there's no uninstaller.
Going to stick to WU driver updates only for chipset.
z68 user here on Windows 10.
Installed these and it caused a myriad of issues including my AMD GPU drivers no longer functioning - even when reinstalled - no 3D acceleration at all after installing.
Had to use system restore to undo them since there's no uninstaller.
Going to stick to WU driver updates only for chipset.
plopingo
Member
Posts: 61
Joined: 2011-08-07
Member
Posts: 61
Joined: 2011-08-07
#5136213 Posted on: 08/05/2015 05:01 AM
What -overall do for the installation ?
Thanks
What -overall do for the installation ?
Thanks
Post New Comment
Click here to post a comment for this file on the message forum.
Senior Member
Posts: 122
Joined: 2012-08-12
What important things does it update? Most people seem to claim installing these is pretty useless. I personally always like to have the latest drivers even if they don't do much lol.