This tool is full of bugs and, IMHO, cannot be trusted to do the right thing. I recommend that you manually download and install all of the latest drivers for your NUC and chosen O/S.
Here is a link to the main download page for your NUC: Downloads for Intel® NUC Kit NUC6i7KYK.
Hope this helps,
I've tried to install them manually first, but the scan with the tool shows the old versions, instead of the new ones.
For example, I've tried to manually install the Nuvoton CIR driver from the drivers page of the NUC, it appears to install (no error messages), I reboot and when I check the driver version I find the old one, not the version I tried to install. Then I've tried the update tool and it finds the same drivers for the nuc that are on the nuc drivers page, but it also cannot install them. They appear to install ok, but when checking the version, it is the previous one, not the one I tried to install.
Thank you, N. Scott Pearson for your recommendation.
cristi101, I would recommend following Scott's advice, also, you can download the driver bundle.
In the meantime, I would also uninstall the Intel® Driver Update Utility.
Please don't hesitate in contacting us back if you need further assistance.
That tool is handy as it lists all the versions of the drivers that are currently installed.
I tried to manually install the manually downloaded drivers, but it doesn't work.
For some reason the drivers installed by Microsoft are not replaced. Some install, but many don't.
Yes, this is true. In some cases (I think CIR is one of them), you must manually uninstall the existing driver, reboot and then immediately install the new one (...before Windows Update installs the old one again).
I think I cannot beat the speed of the nuc. It is faster than me at this.
cristi101, in this case, I recommend you the following:
- Download the driver first,
- Disconnect the device from Internet
- Uninstall the existing driver.
- Restart the device
- Install the new driver and then connect to the Internet again.
Hope this helps.
I will try this way, but it might not work.
I don't remember if I already tried it.
What I think it will happen is either the old driver will be installed because it is already downloaded or the new driver will not install because it no longer find the device (gone when uninstalling the previous driver).
The only reliable method seems to be the manually driver update method. But the drivers are not packaged for it so it cannot be used.
For the chipset and thunderbolt drivers I cannot even find a device in device manager to do the driver update.
For the chipset one, it is probably under "System Devices", the Thunderbolt shouldn't come up unless you connect a device.
There is a workaround that prevents Windows® 10 to update specific drivers:
To know the Windows® 10 version you are running please type "winver" in the search bar and press enter, then a window will pop-up with the information.
I have an almost identical problem, which suggests the problem does not lie with using Intel Driver Update Utility to install, nor with Windows 10...
I attempted (and was possibly successful?) to upgrade the chipset driver from version 10.1.1.18 to 10.1.1.42. I downloaded the new version manually, not using DUU. The SetupChipset.exe program appeared to complete successfully. But DUU v2.7.2 reported that nothing had happened. It reported still 10.1.1.18 , with latest still 10.1.1.42.
I do not believe that there was time for Windows Update to re-install the old driver. And certainly, there was no Windows downloading or updating or generally faffing around activity apparent.
I then read the release notes thoroughly, and took their advice to inspect the registry to confirm the version. The registry reports 10.1.1.42
So, do you reckon I should believe DUU (v. 10.1.1.18) or the registry entry (v. 10.1.1.42)?
Dear JC, For the avoidance of doubt, do you expect me to make the following assumptions from your post:
- As well as not updating reliably, the Intel DUU does not detect installed versions reliably either?
- The version I have installed IS the one indicated by the registry? (Your remark "In this case I would take" is ambiguous.)
P.S. I am most surprised that Intel DUU can fail in such a way as to report correctly the version of a previously-installed driver. Has a developer inadvertently written some code to record and substitute an earlier state, somehow?