Thank you for taking the time to respond.
Fortunately, I know how to install a video driver. Unfortunately, that is not the issue. The issue is twofold:
- The Intel Driver Support Assistant is NOT WORKING CORRECTLY, it is identifying and attempting to install the wrong video driver.
- This is not the first instance of the Intel Driver Support Assistant attempting to install the wrong driver.
How do I know it is the wrong driver?
Intel.com / Support / Downloads and Drivers / Product or Keyword Search / Nuc8i7beh / Intel HD Graphics Driver for Windows® 10 for Intel® NUC
Totally different driver than recommended by the Intel Support Assistant.
Hopefully this issue will be identified and quickly resolved.
I must not be making myself clear. The problem is with the Intel Driver Support Assistant. This problem has existed for nearly a month now and has not been fixed!
What is the issue? The Support Assistant cannot install a video driver even on a brand new Nuc8i7beh with the latest version of Windows 10 (1809).
This morning, I installed Windows 10 1809 on a brand new Nuc8i7beh I was setting up for a friend. Ran Windows update and installed all updates until every update had been installed. Rebooted the Nuc8i7beh. Opened up Microsoft Edge, typed in Intel.com pressed enter. Clicked on Support, Downloads and Drivers, Automatically Find drivers and Software, Downloaded the Intel Driver Support Assistant and ran it.
Here is what I received on a brand New Nuc8i7beh:
Plainly the Intel Driver Update is not working properly. This needs to be fixed.
I can confirm the issue after doing a fresh install on my NUC8i7BEH (first time, just got it) -- the same issue with the intel DSA. I was able to get around it by downloading the driver manually "GFX_WIN10_64_22.214.171.12444" and updating the driver in Device Manager by pointing to the extracted folder. The driver was detected and once it loaded that way, I was able to run the installer as normal and it is now working correctly and DSA shows correct now too.
kind of a weird issue... I wonder if the MS updater is causing it?