The Intel chipset drivers are just the INF part of the driver that allows Windows to correctly identify the majority of the unknown Intel drivers, and for them to show in device manager. They are 'important' to install if Windows hasn't correctly identified the device (in that the device information isn't part of the Windows driver set) so Windows can use the correct generic drivers or system resources for it. There are some devices where INF's are available, but where you should use the actual Intel driver for best performance (AHCI drivers for example). If you look at the actual extracted install files, you will find there are no actual driver files. Inside the INF's, you will see the hardware ID's near the top, the hardware names down the bottom, and if a driver (Microsoft generic) is required, you will see something like this: If you look at machine.inf, you will see much the same thing on a much grander scale! The hardware ID's at the top, and the names further down. You will see in the names that some cover the same devices (in the situation where -overall was required), and only really the newest devices aren't covered. The Intel chipset drivers are really just addendums to the Microsoft driver, adding more information as newer devices come out past the date of the original 'Microsoft' driver (Intel etc do play a part in the generic files I believe). So, the newer the OS is, the less likely you will require these inf drivers if you have hardware that has been around a while. So, in answer to your question, it seems highly unlikely that any change to the device INF installations will provide any difference whatsoever, as effectively you are just reinstalling the same driver, with the exact same features, but with different information showing in device manager. So, if there was a difference in performance then something had been awry with the existing installation, but that again is unlikely. The ONLY times you will see a difference in performance is if you force install the INF USB 3.0 drivers on Windows 7 for example, or force install the AHCI drivers. On Windows 7, for full USB 3.0 support you need an actual driver (it's built in for Windows 8), force installing the INF will mean you can use the device, but you won't get the full benefit of it with USB 3.0 devices. Therefore, force installing the INF is bad! Then of course, is the AHCI drivers. Really you only want to install the driver part, not the full RST (you can do this easily). This allows for the performance AHCI drivers to be utilised. If you use the -overall command, the proper AHCI driver will be replaced with the INF name and the generic Microsoft AHCI driver, which again would limit performance potential.