I would like to use them for Cortana, but I don't see them as a recording device in WIndows 10.

I downloaded the realtec drivers but this is for the jack, not for the built in mic,,,

any idea?

Hi,

I have been using my NUC7i7BNH for a while, running Win 10 Pro 1703 connected to reciver and TV with HDMI.

Yesterday I got a new harddrive (Samsung 960 EVO 256GB NVME) and did a clean install with a Win 10 Pro 1709 (Creators Update Fall) ISO.

After installation a few minutes went by, the screen flickers and then goes black. Try to restart but the TV just says “display resolution not supported”. Perform restore to an earlier system restore point (probably before the update/driver was installed). The display works again and everything is OK. But after a few minutes the same thing happens again. Unplug my Ethernet cable and do yet another restore. This time the machine is running considerably longer. Download the Intel drivers from my laptop and install them on the NUC from a USB-drive. When I get do the display driver (Intel® HD Graphics Driver for Windows® 10 for Intel® NUC Kit NUC7i3BN, NUC7i5BN, and NUC7i7BN Version: 15.46.05.4771 (Latest) Date: 9/11/2017 ) the same thing happens again – no display.

Then tries to connect the NUC to my PC monitor and it works perfectly. Do a few restarts, wait a while etc… Everything works. Then connect it to the TV again – no picture – “display resolution not supported”. (Note: I have tried to connect the NUC directly to the TV without passing the receiver, but it didn´t help).

Gave up and switched back to my old hard drive with 1703 and that of course worked. Is the Intel display driver not fully compatible with 1709 Creators update?

Here's a story about "specifications" (and "change of specifications") that I believe it's worth reading. If you purchased an Intel NUC in the last couple of years you may find it pretty interesting. And, whether you are aware or not, it may also apply to you. Of course, some kind of comment from someone @Intel would be very appropriate.

I got my first NUC in the spring of 2014. It was a DN2820FYKH which I used exclusively to stream HiRes audio to my Onkyo receiver via Foobar 2000 (directly through the HDMI output via WASAPI). Never had a glitch, which, after all, is pretty obvious: all the NUC had to do was to decompress FLAC audio into a PCM bitstream and send it to the amplifier, which took care of everything else. Easy. So, since 2014, my library of HiDef music increased steadily, including plenty of 192kHz/24bit audio.

Given the satisfaction with the above, in the spring 2016 I decided it was about time to consider a similar approach for movies and videos as well. So, given the CPU limitations of the DN2820FYKH, I decided to purchase a NUC6i3SYH which, ON PAPER, had all the capabilities of my earlier NUC, plus enough processing power to cope with most video sources (after all, if DTS-HD, Dolby TrueHD, and whatever else are simply "passed-through" to a capable receiver/amp, you just need a CPU powerful enough to take care of video decoding... right?).

While such assumption concerning video was right (and, after setting the appropriate audio pass-through, video works indeed smoothly), I soon realized that my brand new "Skylake" NUC wasn't capable of playing any of my 192kHz/24bit audio files. What?!?

Useless to say, as such audio files played perfectly with my old DN2820FYKH, my disappointment was huge... but as the NUC6i3SYH had just been released, I optimistically assumed that such an obvious issue would have been fixed pretty soon by some Intel update. And, please note, I perfectly remember that at that time I double checked the original "Technical Product Specification" (which I still have): and that TPS clearly stated that "LPCM, 192 kHz/24 bit, 8 channel" was supported (and both through HDMI and Mini DisplayPort). So I felt sure that, one way or the other, sooner or later, I would have been able to play such files using the new NUC.

Hence, from time to time, I simply checked the Intel site to see if a new "HD Graphic Driver" (which includes the so called "Intel Display Audio") had been released, installed it, crossed my finger, and tried again.
No way.

Until last Sunday, after installing yet another driver version released on June 15 2017 (with no benefit whatsoever: just another waste of time), I decided that it was enough, and it was about time to post something on this forum. As I had browsed this forum in the past (and I was familiar with the typical follow-ups of "try changing the HDMI cable" or "maybe your receiver doesn't support that format"), I started gathering documentation and screenshots to show that everything was fine with my receiver and HDMI cables, and that 192kHz/24bit audio could be streamed perfectly not only from my old DN2820FYKH NUC but even through any other kind of PC I have (even an old i7-2600 with a Radeon HD 6450 can perfectly stream 192kHz/24bit to my amp, and both via the Intel® HD Graphics 2000 HDMI or via the Radeon HDMI!).

Then, when I was just about ready to create a new thread on this forum with all such evidence, I thought that it would have been a good idea to start such a post with a "cut-out" from the "Technical Product Specification", showing what Intel had announced/promised in terms of PCM audio support via HDMI and NEVER DELIVERED... This time though, rather then refer to the original PDF that I downloaded over a year ago (when I purchased the NUC), I decided to check the latest available document on the Intel site... And, guess what?

At the very beginning, on page "iv", under "Specification Changes or Clarifications", among a bunch of other things that are mostly meaningless and have no impacts whatsoever, it states:

"August 2016 Spec Change • Page 23 Table 7 from 192 kHz / 24 bit to 192 kHz 16 bit"

Huh?

They fixed the 192kHz/24bit problem by simply and silently downgrading the specs...!
How cool is that?

Now, does this apply only to the NUC6i3xxx series?
Or, in other words, would I have been in a better position if I had bought a NUC6i5xxx or better?

No: I would have simply spent more money for the same kind of rip-off!

Because such an "August 2016 Spec Change" also applies to the whole NUC6i5xxx series and even the NUC6i7KYK (which is not exactly cheap, right?).

And what about the latest NUCs?

Oh well, you won't find a "change of specifications" history in their TPS (yet), and they all promise "192kHz/24bit" exactly as last year Skylake NUCs did... but I wonder why I should ever trust Intel again on such promises: maybe by August 2017 those specs will also be "downgraded" to "192kHz/16bit", huh? Or something else that worked fine on previous NUCs won't work any longer...

So, here's my 2 cents about this story:

1) Intel knows very well that lots of NUCs are used as "media players" in entertainment systems, or they wouldn't be providing CIR support in every one of them.

2) Yet, in their designs/implementations (and testing!) they seem to frequently overlook and disregard basic standards and assumptions (192kHz/24bit audio via HDMI was already supported by platforms that are now 6 or 7 years old, not to speak of all NUCs before Skylake).

3) I find it quite amazing to think that, while still at the design stage, people at Intel may have screwed up a simple computation such as:

192000 (hz) x 24 (bits) x 8 (channels)

and not realize that their design didn't provide enough bandwidth to PASSTHROUGH such a bitrate (which, by the way, is far from huge by today standards: just 36,864 kbps, huh?).

4) And it's even more disconcerting to think that nobody at Intel ever took care of thoroughly testing their PCM implementation through HDMI before the launch of all their Skylake NUCs (otherwise, they would have easily spotted the problem with 192kHz/24bit PCM audio and done something about it).

5) It's pretty clear that we (the users) are not treated by Intel's NUC division as customers, but rather as "guinea pigs". If you have the patience to do some searching/browsing on this forum, you will find plenty of people (mostly using the NUC6i7KYK) complaining that 192kHz/24bit audio through HDMI (or whatever else) was not available, and no Intel representative ever took the pain to confirm/address the problem. They just suggested to update the bios, drivers, try a better HDMI cable, or even told them that it was probably the fault of their amp/receiver. And of course all such suggestions turned out to be a waste of time (because the problem was Intel's own design/implementation).

6) It took about ONE FULL YEAR for Intel to recognize the problem with their HDMI/PCM implementation on their Skylake NUCs (6i5xxx were launched in Q3/2015, the spec revision occurred in August 2016), and, after one year, how did Intel address the problem? They just simply (and silently) "downgraded" the specs.

7) I was not born yesterday, and I am well aware of all the fine prints and "specifications subject to change" stuff, but that's meant to give manufacturers freedom to update specs and features for future revisions of their product, not to downgrade the specs of something that has already been sold on false promises. If you sell me a car saying it has 4 wheels, and deliver a product that has only 3, changing the specs one year later (and downgrading the description to "3 wheels") doesn't do the trick: I'm entitled to a refund, even more so if, for nearly a year, you mislead me suggesting a should get a new pair of glasses (or in our case get a different HDMI cable or even a new amp/receiver) to see and enjoy the "fourth wheel"... And/or implicitly lead me to believe, given the obvious nature of the issue, that some kind of fix was surely going to come (and wasting my time in multiple useless updates of BIOS, drivers, and whatever).

8) All in all, it seems that the whole "customer care" concept appears to be unknown to the Intel NUC division. Because once you recognize your error (as they eventually did), at least you should do whatever possible to alleviate the problem for your customers. Or not?
In this case, once you realize you have not enough bandwidth to passthrough 8 PCM channels @ 192kHz/24bit via HDMI (as they originally stated in their TPS), at least provide support for 2 channels (stereo!) or 5.1 (six channels). But they didn't, and simply removed 24bit audio entirely from their specs.

9) Please note that the kind of fix-up I just suggested above (supporting at least stereo and maybe 5.1) doesn't imply write tons of code. They already support PCM passthrough streaming (via HDMI and whatever) at different frequencies and bit depths, so all that's needed is to allow the PASSTHROUGH of any 192kHz/24bit bitstream that, because of the limited number of channels, still fits the available bandwidth, so that applications can at least stream 192kHz/24bit stereo. But it seems that for Intel NUC division their customers don't deserve not even such a partial solution to the problem. Too much work, huh? Let's simply remove any hint to 24bit audio all together from the specs: who cares... And not even an apology.

10) As I already mentioned, though Intel knows very well that lots of NUCs are used in entertainment systems, they clearly don't seem to have a clue of what people assume and expect to be "standard feature" nowadays. 16bit audio is 30 years old stuff (compact disc). And all subsequent advancements in digital audio implied higher bit depths (DVDs, DVD-Audio, BluRay, etc. all assume bit depths > 16) for the very simple reason that higher bit depths provide better dynamic range and accuracy. So seeing a "change of specs" in which Intel in August 2016 tells us that its HDMI implementation supports 16bit PCM is simply laughable. And that's exactly what they have done. Period.

11) Here's how the PCM support/implementation for HDMI and DigiPort is now described after the change of spec:

"LPCM, 192 kHz/16 bit, 8 channel"

Nothing else.
Honestly, who cares about 16bit PCM nowadays?

Dear Intel/NUC guys, 24bit audio has been around for years, and, guess what, we expect your specs to tell us something about that: what do you support in terms of 24bit audio through HDMI, DigiPort or whatever? Up to what frequency, and how many channels?
Instead, after the screw-up, it seems that Intel/NUC guys prefer to stay clear of any further reference or commitment on the 24bit audio front, and thus they just don't write/specify anything at all...

We just have to find out by ourselves, huh? Wow!

12) So, guess what: before writing all this I spent some time experimenting with different audio files and programs and came to the conclusion that, at least on my NUC6i3SYH (and latest driver), 24bit audio is supported up to 176kHz (multichannel). So, if such conclusion is correct, there's plenty of bandwidth to support at least 192kHz/24bit stereo and even 5.1 passthrough. If only Intel cared, of course. But they don't: the fact that in their revised specs there's not even a single hint to 24bit audio through HDMI tells it all.

-------------------------

Now, I'm sure someone (maybe even from Intel) will tell me that the difference between 192kHz/24bit and 96kHz/24bit is not that discernible, so I should just feel lucky and be happy that the latter works and just stick with it. Yes, indeed. Even the difference between FULL HD and 4k and is not that discernible unless you are sitting pretty near to the screen... so what?

I have an amp that accepts 192kHz/24bit and that worked perfectly with my old NUC. So I purchesed a lot of audio files in that format and I don't see why I should have any trouble playing them with a platform that "promised" to support that (as just about every single PCs does!). That's all.
Am I wrong?

Indeed, I can play those files at a lower frequencies on the NUC6i3SYH. For instance, while Foobar simply gives an error on any such files (saying that 192kHz/24bit is not supported), if I try with Kodi such files gets played anyway... But guess what: if I check what my amp receives it's a 176kHz/24bit bitstream. In other words, Kodi resamples the audio at the highest supported frequency for 24bit. This resampling, of course, doesn't certainly do any good, and performing such resampling each and every time I play the same file it's just a waste of CPU. Right?

Sure, I could spend days (maybe even weeks!) performing such resampling offline, once and for all, on all my library files. Yet I would need additional storage, because I don't want to throw away the original Hi-Res files, so each and every audio file in my library would end up being duplicated in different formats (and we are speaking of Hi-Res audio: files much larger than CD). And, of course, I would also need to reorganize my entire audio library accordingly. Given I was sold a NUC that promised 192kHz/24bit support out of the box (exactly as earlier products did), and after more than a year of useless driver and bios upgrades, I'm not that happy having to waste more time like this (not speaking of adding more storage, reorganizing the library, etc.).

Of course, I could put the old NUC DN2820FYKH back into use (though I now use it for different purposes in a different room). In other words, as ridiculous as it sounds, I could use the old DN2820FYKH just for audio, and the NUC6i3SYH just for video. But, guess what, all 7 HDMI inputs on my amp are already in use. And anyway it would probably be a mess having those two NUCs sitting side by side and operated by the same remote control. Right?

Lastly, I could buy a new NUC... But why in the world, after this experience, should I trust anything written on an Intel NUC TPS anymore... huh?

You tell me.

Kindest regards,
A very disappointed "Guinea Pig"

Hi

Does anybody know for sure which I2C speed mode is used for the Synopsys DesignWare I2C bus on the custom solution header?

I'm using Debian Stretch. The bus is working, but I need to connect a device which can only be used in standard mode, so 100kHz.

Fast mode with 400kHz would be too fast.

If the NUC uses 400kHz by default, how can I change that in an easy way?

Tech Spec doesn't say anything about it and even Google didn't help.

Cheers, Martin

Now it sure: the new driver 4771 with new win 10 upgrade to 1709 generate big problem for those who use NUC as HPTC.
In my case all the old setting of graphic card and Kodi 17 give flickering image. There is no way to solve problem; also if you put fix FPS your TV will be flichering:

After many hours of attempts I found a solution enough to wait for INTEL to solve the problem and hope it will be soon.
Obviously I do not guarantee this solution works for everyone.
I did configured video  to work with a 60p FPS (using INTEL utility) and I configured Kodi (v 17.4) so I did not change FPS, I also disabled in Kodi dvxa2 acceleration (otherwise i will have stairs of pixel when decode H265) .
This way, you get a fresh result, hoping how I said, that INTEL resolves soon:

I repeat that I cannot stand the INTEL & MICROSOFT pair anymore, the more trouble I have over this NUC than the pleasant times of use.

regards Antonino

PS:
i did tried to downgrade the video driver but seems that with win 10 1709 the old driver are not certificated anymore. So wuold be necessary to downgrade also windows 10 to 1703. I prefer wait for Intel's solution

The internet speeds to my house are 50 Mbps down/up. I'm getting only around 25-30 Mbps down to my NUC Skull. The upload speeds are in the high 40s as expected. (This is all via WiFi.)

Any ideas what would cause the slower download speeds?

I saw another thread with a similar issue. I've followed some trouble shooting steps advised there:

• I've added the iwlwifi-8000-ucode-25.30.13.0 firmware (even though I have newer drivers).
• I tried updating the BIOS by downloading the KY0050.bio file and following the instructions but the USB drive doesn't show in the BIOS Flash Update tool, only the boot drive.
• The Intel® System Support Utility output is attached.

Model: NUC Skull Canyon NUC6i7KYK
Operating System: Ubuntu 17.04

I have an intel NUC7i7BNH with 16gb of memory.  Which is connected to an LG HDR tv (I can get HRD contect via the smart TV apps and the 4k player)

I have done some research online and found out that the HDMI port on the NUC is hdcp2.2 compliant

http://www.intel.com/content/dam/support/us/en/documents/boardsandkits/NUC7i5BN_NUC7i7BN_TechProdSpec.pdf

(page 25)

From my research online I can confirm that:

1. I am running windows 10 with all of the latest updates installed
2. I am using the latest graphics drivers from intel
3. I have the netflix UHD package (again I have checked via just the app on the tv and it streams in UHD)
4. I have set Netfix it via the options to use the best possible picture.
5. I am using MS edge as the browser when connecting to netfilx

I just don’t seem to be able to get it to stream in UHD on the PC.

Has anyone managed to get this to work? 

D

I have downloaded and installed the latest Windows 10 driver  for the Intel Dual Band Wireless-AC 3168 https://downloadcenter.intel.com/it/download/26436/NUCs-Intel-Wireless-basato-sulla-tecnologia-Driver-per-Windows-10-per-i-Kit-Intel-NUC-NUC6CAYS-e-NUC6CAYH?product=95062

But both Control Panel and Intel Driver & Support Assistant keep telling me that  I have installed version 19.51.7.2...I am a little confused, could anybody help me to clarify this issue?

After installing the Windows 10 Fall Update my NUC7I5BNH won't power off unless I press and hold the power button until it turns off (hard off).

If I shutdown via Windows it just immediately starts Windows back up. I don't even get to the BIOS/UEFI splash screen.

If I press the power button on the front of the NUC the same behavior happens.

Video: Intel NUC NUC7I5BNH won't power off - YouTube

When connected through HDMI ports on NUC and Monitor ( both HDMI 2.0's), when the Monitor goes to sleep it can not be reawaken and the speakers start chirping as if you just connected some other device and they do not stop.

The only way to wake the monitor is to switch to another input and revert back to the original HDMI1 or HDMI2 on the monitor.

On the Display ports it seems to work fine.

All Drivers are up to date !!!!

Configuration is

NUC6i7kyk

  32Gb of RAM

  M.2 - 512 Gb - SSD 960 Pro

Latest Drivers are:

  BIOS  Version 050

  Iris Pro 580 - Driver version (Win 10-64 - 15.46.05.4771 KY  download)  22.20.16.4771

  LG - LG ultra HD (HDMI)

  HDMI 2.0 Firmware  version 0x07 0x20

  Realtek High Definition Audio - Ver 6.0.1.7982

Is anyone out there having a similar problem.  Or is there any suggestions on how to fix this annoying problem.

Thank you

I had my NUC connected to my AV Receiver since the day I purchased it and the receiver connected to a Samsung Plasma TV. Everything worked fine until I upgraded to the latest BIOS (version 0052)

Since the upgrade I cannot see an HDMI picture through my Onkyo TX-NR709 AV receiver, instead I see a jittery and totally garbled image (as if there is a frequency mismatch).

I tried the connecting my other PC to the receiver and it worked just fine. I also tried connecting the NUC directly to the TV HDMI port and that worked fine as well.

The interesting thing is that when I reboot the NUC it displays the Intel logo and the prompts to enter BIOS just fine, however the minute it moves to the operating System (Windows 10 64-bit Fall Creators Update) I lose the HDMI signal to garbage. The same does not happen with other Windows PCs that I have at home so this is for sure something to do with the NUC.

I found a reference to a HDMI 2.0 Firmware update for the NUC however I am not sure that will do any damage to my NUC and also not sure if it will make any difference since my receiver is HDMI 1.4 and not 2.0.

Any suggestions welcome.

Regards,

Tareq

Coming from Intel NUC DN2820 I was able to play 3D MVC with Kodi with new Intel Media SDK, I just purchased Intel NUC NUC7i3BNK and 3D playback doesn't work.

On the Intel NUC DN2820, the resolution was set 1920X1080p 3D and everything works great

On the Intel NUC NUC7i3BNK either I set the 1920X1080p 3D or  3820X2160p 3D doesn't work

The Intel Media SDK was supposed to allow 3D MVC to work, I did some testing and found the HDMI 2.0 connection is the one causing the issue and any NUC with HDMI 2.0 doesn't work/

Dear All

I have found some NON Understandable Power Saving problems in my NUC 7i5BNK.

1:  The displayed windows will shrink and will be moved to top left conner after monitor resumed from power saving.

This problem is totally non understandable to me.   I am using a 4k monitor, and normally will open about 10 windows at the same time.  I will carefully arange these windows to deferent size and locations for my working efficency.   I was totally astound when i first time see all of my opened windows were shrinked and moved to top left conner and piled up togather.  I have to move and resize all of them to work again.  So, each time when i resume nuc, i will demn it.

2:  The NUC will not goes to sleep

Since the monitor can goes to power saving, i think windows time counter is working.  but no matter how long time passed, the NUC will persisted working hard, and not goes to sleep.   This is also give me another curiosity.  though the NUC can not sleep by time, but it can sleep by POWER BOTTON or by windows commands.

3:  Keyboard and mouse lose responses when power saving.

Sometimes after enough time monitor power saved,  the keyboard and mouse will lose response.  and then the monitor will not resume from power saving buy keyboard/mouse.  I have find  a method by use Power Botton to make the NUC realy goes to sleep, and then i can use keyboard/mouse to resume it !  but sometime:

4:  NUC crushed in POWER BOTTON press

there are about 1/3 or less,  when i press power botton to make the NUC gose to sleep,  but NUC will crushed from windows, and will reboot.  at this point, all of my unsaved work will be lost...

5:  The NUC is not a ACPI computer if Intel Graphic Driver not installed.

I have tested this with windows 10 1703 and 1709.  with only Microsoft Basic Graphic Driver, this NUC will be not a ACPI computer.  Only black screen useable, the sleep time will dispearl.  Black screen power saving will be display full vacant black screen signal, and the monitor will not gose standby.

If anyone have similar experiences, do please let Intel knows!

Regards

William Wang

I'm running a skull canyon NUC with Ubuntu 16.04 connected via HDMI 2.0 to a Samsung TV.

I recently setup 5.1 speakers on the TV, it was working fine with a 2.0 setup but the extra speakers and sub don't seem to work at all. The speakers themselves are working with the TV and other devices just not the the NUC.

I've tried using https://01.org/linuxgraphics/downloads/intel-graphics-update-tool-linux-os-v2.0.4 to update tool to see if that fixes the issue but no joy so far.

I found this post with a firmware update that you can only run on windows to resolve this issue... is there any way with linux to get the same fixes? NUC6I7KYK (Skull Canyon NUC): No 5.1 over HDMI

New NUC7i7BNH system with 32Gb Optane Memory, 16Gb RAM, 1,5Tb HDD.

I am trying to connect system to Sony Bravia TV via HDMI cable/port.

For first week of using the system I had no problem connecting to TV.

Late last week, following either a Win10 update and/or Intel BIOS update, I have not been able to connect to TV.  Now, after POST,  I get a black screen with error display - 'Unsupported signal. Check device output.'

I am presuming it is a problem with BIOS as computer doesn't even get to point of loading operating system.

Do I need to roll back to previous BIOS or is their a new BIOS fix?

Thanks,

David Sanderson

Can I use Samsung 850 EVO 250GB M.2 2280 SATA III in this NUC?

Thank you!

I would like to use them for Cortana, but I don't see them as a recording device in WIndows 10.

I downloaded the realtec drivers but this is for the jack, not for the built in mic,,,

any idea?

Hi all,

We are aware of this issue and a bug was opened a couple weeks ago.  The developers/engineers are working on finding a solution and I will post any updates and/or solutions here.

Thank you for your patience.

Hi,

I have two issues which I was hoping the community could help with:

1) Playback from a PLEX media server stutters with 4K and FHD content. Internet connection is more than adequate: wired, 100mb.

2) Playback of 4k content (stored on my NUC - 1TB SSD) using VLC player stutters. Unusually, there is no stuttering when playing the same 4K content using the native Windows player.

Any help or guidance on these issues would be appreciated..... hopefully it's a simple fix  :-)

Hamid

I have almost the same problem with my NUC Kit NUC5i5RYK.

When I run https://www.intel.com/content/www/us/en/support/intel-driver-support-assistant.htm it shows there are 2 updates:

Although I ran the updates several times en rebooted , the new drivers will not install. I do not get any faults when the installers are running.  Version 12.15.25.6 is never removed. I'm really stuck here.