Did you install the Intel NUC Drivers Bundle? That is what I did originally. I have the NUC7i7BNH Model and downloaded over 900MB of zip file. I unzipped and installed in the order show in the readme file.
I just wondered if you did anything different? I am still toying with a complete re-install ....
After that the "Check MiniTioune Drivers and Filters" application ran correctly and I was able to see the F6DZP testcard and the rotating BATC logo. I then re-plugged the USB-C to HDMI adapter in (I left my primary monitor on the NUC's HDMI) and it still works fine. I have yet to try the Minitioune application itself as I will need to get my Portsdown plugged in again but I have no doubt that it will now work!
What a palaver! I an very glad it is fixed though and it was only because you also have the NUC that I persevered with it this morning!
Thanks and very 73 and (change of subject) maybe see you on 5.6GHz as well!
Great news that it now appears to be working; onward and upward.
There was one problem with mine which is now resolved, luckily it was common enough to find a solution on YouTube.
I could see all the devices on my network except the NAS and therefore all my stored files. Word on the net says it's due to the latest Windows 10 update, some functions in the PC administration have been turned off by default. An awful rumour suggests the software writers would prefer you use their cloud than a home based server.
Yes 5.6GHz, not too good looking SE from my location (IO91RV). There's a big hill in the path with Luton Airport on it.
What portable locations are you near?
Great question ... I did some tests and it appears to be the latter! If I run the test application on the monitor attached to the built-in HDMI it works fine BUT if I run it on either of the other two (which are connected by a dual USB-C to HDMI adapter (and I bought the one from Pluggable because it was certified by Intel to work with the NUC) then the video window remains black. It is using the DisplayLink drivers. I will now research updated drivers for that device ...
Later ... I have updated to the latest DisplayLink drivers dated August 2020 and the problem is still the same so I think it is DisplayLink related ... What an interesting and very difficult problem to solve!!
I will need to research high spots ... Probably somewhere over towards West Kent on the Downs!!