Looks when you are using the -overide command you mainly have to reinstall the third party driver, if you're using such Intel Rapid Storage Technology.

-OVERALL = Updates ALL INF drivers on all available devices even if third party drivers are currently installed. This flag works in Interactive Mode only.

-OVERIDE = Updates the storage drivers even if a third party storage driver is currently installed. This flag works in Interactive Mode only.

Also looks this -OVERIDE command doesn't exist anymore on v10.0.xx.xxxx Intel Chipset Utility Driver, might be because of their new installer. It's also a matter how they do speak on to, and on v10.0 they do call it "Overwrites all drivers" !!!

@ FernandoHey guy I have a question for you. A while back I was visiting some forum that I don't remember now and you did replay someone in regard to how to extract and install those drive to the chipset manually.If I'm not mistaking you mention to download the chipset driver then get 7Zip and extract the file, then go to update driver tab in system property and search manually for the driver in WHAT FOLDER thats the step that I don't remember could help me out and refresh my memory, Thanks.

Zitat von Camp Anaconda im Beitrag #18If I'm not mistaking you mention to download the chipset driver then get 7Zip and extract the file, then go to update driver tab in system property and search manually for the driver in WHAT FOLDER thats the step that I don't remember could help me out and refresh my memory,

It depends on the OS you are running.If it is Windows XP, it's the folder named "All", if it is Vista, Win7 or Win8, it is the folder named "Win7", where to search for the suitable INF files.

I,m using Windows 8.1 Pro, and I had follow your guide like I said before were was posted in another forum and it did work like a charm. That setup I have to secure erase the drive to star from scratch I bought a new version of Windows 8.1 Pro with the SP1 or the update pack whatever they call it, but anyways guy is Windows 8.1.

Zitat von Camp Anaconda im Beitrag #20I,m using Windows 8.1 Pro, and I had follow your guide like I said before were was posted in another forum and it did work like a charm.

For users with an Intel 7-Series Chipset desktop system I recommend to concentrate their interest on INF files, whose names are starting with "pant". The newest Intel Chipset Device INF and CAT files for Z77 mainboards running Win7/Win8 are attached.

Zitat von Camp Anaconda im Beitrag #20I,m using Windows 8.1 Pro, and I had follow your guide like I said before were was posted in another forum and it did work like a charm.

For users with an Intel 7-Series Chipset desktop system I recommend to concentrate their interest on INF files, whose names are starting with "pant". The newest Intel Chipset Device INF and CAT files for Z77 mainboards running Win7/Win8 are attached.

Very sorry Fernando excuse me that one and the next, thats a saying of us where I from when we do mistakes, But I have to update my Profile signature, my new board is ASUS X99 Deluxe with the i7 5960X Cpu, sorry. Now guide from this specs. TIA

I did update my Profile Signature but is not showing I guess till my next post

For Intel 9-Series Chipsets you cannot use the old Intel Chipset Device Software v9.x.x.xxxx series, you have to take one of the new v10.0.xx packages.According to my knowledge only the Intel SMBus Controller will need an INF file (to tell him, that no driver is needed).The Intel 9-Series SMBus INF file is attached.

Zitat von odiebugs im Beitrag #9can you please extract the INF files from the 10.0.22 Intel chipset setup and upload them. I have tried a thousand times with CMD and so sick and tired of trying.

I cannot extract the INF files either. Even the tool named "Resource Hacker" doesn't find any of them within the SetupChipset.exe.The only thing I can do for you is to attach the INF file I got within my Windows\Inf directory after having executed the SetupChipset.exe. Furthermore I have added a chipset.cat file I found within my system drive.

And here is my general note about the INF drivers. Recently I installed Windows 7 x64 Ultimate on a new ASRock Z97E-ITX/ac mobo. During the installation my usb mouse, connected to one of the rear usb 2.0 ports, was without any function. When, at the end of the win7 installation, the INF driver was installed, the mouse finally was recognized. So, installing the INF drivers is not just the cosmetics of removing a yellow exclamation mark inside device manager, but telling the OS which of it's build-in sys-drivers to use for a certain device (like in this case a standard USB 2.0 controller) and thus making it work.

ZitatRecently I installed Windows 7 x64 Ultimate on a new ASRock Z97E-ITX/ac mobo. During the installation my usb mouse, connected to one of the rear usb 2.0 ports, was without any function. When, at the end of the win7 installation, the INF driver was installed, the mouse finally was recognized. So, installing the INF drivers is not just the cosmetics of removing a yellow exclamation mark inside device manager, but telling the OS which of it's build-in sys-drivers to use for a certain device (like in this case a standard USB 2.0 controller) and thus making it work.

The "old" Win7 Setup doesn't know the secrets of an Intel Z97 chipset mainboard, which was developed much later than the OS. That is why you will get after the Win7 installation a yellow mark within the Device Manager regarding a "missing SMBus driver". So it really makes sense in this case to run the SetupChipset.exe file of the latest "Intel(R) Chipset Device Software" or let the OS search for the suitable INF files after the extraction of the package.

Since hcwuschel gave me the tip how to get the INF files extracted from the Intel Chipset Device Software packages v10.0.xx, I have executed the related command and got (besides the common .CAT file with the digital signature) the following INF files:

Chipset_SMBus.inf

Chipset_System.inf

Chipset_Thermal.inf

Chipset_USB.inf

Chipset_Win78only.inf

To make it easy for you to get them, I have attached the content of the already extracted latest Intel Chipset Device Set v10.0.0.22. Note: These INF files are only suitable with Intel 9-Series Chipsets.

Just wanted to point out that the latest v10 utilities seem to contain very little .inf files so for most people it's best to install the older v9 versions. I remember coming to that conclusion some months back after using the -extract command myself. Keep in mind that unfortunately this command does not exist on modern packages from Intel anymore. An example would be the ME drivers and other stuff from Intel. There is always the manual way of course, run the installer and before clicking Next go to %temp% and grab any files you want directly from the extracted folder.

Zitat von plutomaniac im Beitrag #27Just wanted to point out that the latest v10 utilities seem to contain very little .inf files so for most people it's best to install the older v9 versions.

It is not as easy as you think:

The latest Intel Chipset Device Software v10 just contains 5 INF files, because the Set is only usable for Intel 8-/9-Series Chipsets. The big amount of INF files within the v9 INF Update Utilities is caused by the variety of Intel Chipsets, which has to be supported by them. Each Chipset doesn't require more than 5-6 Chipset specific INF files.

The "old" Intel Chipset Device Software v9 Series doesn't contain any suitable INF file for Intel's newest Chipsets (from 8-Series up). Vice versa the "new" Intel Chipset Device Software v10 Series is not suitable for Intel Chipsets up to the 7-Series.So there are not so many users, who will have the choice between both Intel Chipset Device Software Series (v9 and v10).

@ all:For users with an older Intel Chipset up to 7-Series I have attached the extracted INF files, which are within the Win7 folder of the Intel Chipset Device Software v9.4.4.1006 dated 04/09/2014, which seems to be the latest complete Set.So you can search yourself for the 5-6 INF files, which are suitable for your Intel Chipset. The first 4 letters of the INF file name means the special chipset, which needs them (examples: "coug" files are for Intel 6-Series, "pant" ones for 7-Series Chipsets). Notes:1. All included files are dated 08/01/2014, but that does not mean, that the INF files themselves have been created by Intel at that date. Many of them are much older.2. These INF files do only support the recent Windows Operating Systems from Vista/Win7 (32/64bit) up.

Yes I know that the v10 is mostly for 8/9 series and assuming that a lot of people still have 7-series & older then v9 would the better choice. Basically what I meant to say is that if you have an older system do not install v10 but the latest v9.

Thing is that I'm not sure that v10 is not for older systems. Intel hasn't placed a restriction on whether the latest packages should be installed on older platforms. The latest v10 package does not extract properly unless you actually install it. If you check %temp% before installing it extracts something like 5 inf files which are definitely not enough for the devices that get "updated" at Device Manager after it's installation. It's been some months since I dealt with this utility so I don't remember much but what I said above is what I noticed.

Also, the v9 packages (maybe v10, don't remember) have a special command to extract only the relevant-to-the-system INF files so users don't really have to search themselves on what to install when choosing the Have Disk Method way of updating them. Check the included Readme or run -? command and a special little window will show the supported commands of each version.

Zitat von plutomaniac im Beitrag #29Thing is that I'm not sure that v10 is not for older systems. Intel hasn't placed a restriction on whether the latest packages should be installed on older platforms.

You are right regarding this point.The INF files of the v10 package do support much more than just 8- and 9-Series Chipsets. On the other hand I remember, that I often have tried to run the SetupChipset.exe of the v10 Series package with 6- and 7-Series Chipset Systems and nothing had been installed.Maybe it will work, if the user tries to install the INF files manually from within the Device Manager.

And how many INF files did it extract? Something like 5-6 if I remember properly. The v9 tools would extract 100 (maybe exaggeration, random number) INFs with the same command. Maybe that's because it's only for 8/9 series. Sure. But, at my Z77 system I used in the past v10 with the -overall command and I remember actually installing v10 "drivers". That's why I said it doesn't extract everything unless the installation process actually begins (unlike v9).