I am trying to use the Sonnet eGFX thunderbult with the NUC7i5BNH.  When i have it plugged in I am not getting video.  Has anyone gotten a external video to work on the new NUCs?  I am running Windows 10 build 1703 which should fall when in specs.

Hi, I am new to this community and new to NUC's.

I have the NUC5CPYH and I am running Ubuntu on it.

I would like to use a 4G/LTE dongle.

I have searched the www for information on this but I have not found anything useful, I am hoping that this community can help me.

Question: are there any USB 4G/LTE dongles, in the USA, compatible with this configuration, and if there are more than 1, which one would you recommend?

Please let me know what other information I can provide.

Many thanks.

NUC6i3SYK Windows10 install NG

OK : BIOS Update [SYSKLi35.86A]
OK : Intel® Chipset Device Software for Intel® NUC Kit NUC6i3SY, NUC6i5SY, NUC5CPYH, and NUC5PPYH
OK : Realtek* High Definition Audio Driver for Intel NUC Kits
OK : Intel® HD Graphics Driver for Windows® 10 for Intel NUC Kit NUC6i[x]SY
OK : Intel® Management Engine Consumer Driver for Intel NUC Kit NUC6i3SY, NUC6i5SY, NUC6i7KYK
OK : Intel® Serial IO Driver for Intel® NUC Kit NUC6i3SY, NUC6i5SY
OK : Intel® Wireless Technology-Based Driver for Intel® NUC Kit NUC6i3SY, NUC6i5SY, and NUC6i7KYK
OK : Intel® Bluetooth Technology-Based Driver for Windows® 10 64-Bit for Intel NUC Products
NG : Intel® Gigabit Ethernet Network Connection Driver for Intel NUC Kit
---

Intel(r) Ethernet Connection I219-V
can not install the driver
There is no Intel Adapter on this computer

I have a new NUC7i7BNHX1. When I try to install Win 10 using Microsoft USB, I get an error 0x80070570. It says "Windows cannot install requested files. File may be corrupt or missing."

The MS USB thumb drive is straight from MS. Is this a bad USB drive, a USB port problem, or ?

Looking for help.

Hi guys,

I have a DN2820FYKH with the cpu 'upgraded' (N2830) and I want to know how better is a NUC6CAYH over my old one NUC. I know is more powerful but does it worth the change?

I have a nuc7i5bnh with windows 10 professional. All games with steam don't have hdmi audio: audio output is only by headphones. All other programs works well and have audio output by hdmi. I have all most recent firmware and drivers. What I can do? I test some cable and ports of my amplifier and my tv, I have always the same result.

I have one of the more annoying issues ever which would simply won't go away.

Some background first:

I'm using a Windows 10 x64 PC with BitLocker encryption backed by TPM.

In every 3-4 COLD boots at the beginning of the day i would get a message from windows at boot time that the TPM is unavailable, and because of that windows could not automatically DE-crypt my drive, and i should use the recovery key instead.

At this point more often than not, i cannot even do that because my keyboard isn't working until i disconnect the usb hub cable, and reconnect it.

At this point there is a simple work-around, to simply press CTRL-ALT-DELETE and perform a warm boot. The next boot ALWAYS work using the TPM which is available at this point. Notice i cannot reproduce the issue using warm boots.

In addition do note that i usually leave the machine completely unplugged for several hours / days to save power.

Sometimes the problem escalates to the point the BCD data is corrupted, and a manual repair is needed. But this is far more rare.

My boot settings are: Fastboot disabled , secureboot enabled, and TPM is active and used for BitLocker.

I'm using the latest available BIOS (49)

Hello.

I am looking for a way to upgrade NUCs we use for an appliance with some timestamp-supplying tamper-evident technology. Is there maybe some easy way to do it with an intel NUC? It's simply for opening the case.

so, I just installed 16299.15 and now I have no audio just a red cross on the speaker icon.

Im connected with hdmi to receiver and it does not look like a handshake issue.

Also no sound from audio jack, any advice?

I have a NUC7i7bnh configured with Windows 10X64 and the latest drivers and bios packages from Intel.

I have the NUC plugged in with 4K HDMI cable directly to a Marantz receiver that supports 4k.  The Marantz then outputs to the TV over 4K HDMI.

For some reason whenever the NUC is left idle and we turn the TV and equipment off and come back to use it again the HDMI signal is gone.  The NUC is running, I can remote in to it and it is working fine but it is no longer outputting HDMI and it doesn't detect the Marantz as a video display.   If I unplug the 4K HDMI cable from the back of the Marantz and plug back in that will sometimes reset the connection but most of the time not.  The NUC is configured to never go to sleep and it is not going to sleep.

I cannot begin to describe how awfully disappointing this product is and how it can't even keep a video signal alive....  We basically have to power off the NUC and power it back and then the NUC will appear on the screen again even though the marantz is set to the correct source the entire time.

There is just no excuse for having HDMI video stop working and having to shut down and power on.  By the way a restart does not fix the issue. You have to actually power off the nuc before it will reinitialize the display.

The issue is not my marantz or my TV.  Every other component is working perfectly with 4K going through the Marantz.

Please help me with a resolution on this NUC is basically a brick and I will start RMAing it until they give me a refund for wasting me time with a non working product.

leaving the Marantz 7703 turned on and set to the NUC source does not fix the issue either.  The NUC clearly stops outputting after a period of time and does not start outputting again until a shut down and power up.

NUC7i7BNH 4K

MARANTZ AVR7703 4K

SONY XBR940D 4K

Hi,

Am planning to use Intel NUC Kits for server programming with Virtualization/Containers.

Here are my requirements :

• NUC Kit (1 or 2)
• i5/i7 Processor should support virtualization (vt-d or vt-x), good enough for a mini-data center(not so pricey)
• 32GB RAM
• 500GB SSD
• Ubuntu latest stable release , for linux distro install
• Windows install - dualboot , if possible
• 2 network ports
• containers(docker) to be used
• Virtualization / Virtual machines
• Container orchestration (Kubernetes) to be used
• Out of the Box Kits are welcome, instead of custom build
• Personal use, server and virtualization programming

Optionally, will add more kits of same spec, once the first NUC kit is successful.

Please throw in your suggestions, Thanks!

Hey there,

I slightly modded my NUC and I'd like to know, whether You can issue an update, which would allow cpu core multiplier and dynamic voltage offset of vCore on CPU? I have a massive temperature headroom, but no way to use it.

Thank You

Kind regards

Bryan

I have  NUC 55ppyh.  I cannot access the bios.

The bios is set to legacy mode, but no F2 is seen on the screen at boot , you cannot go into windows and say let me access the bios on next reboot because windows is installed in none uefi mode.

The bios reset by removing the jumper  and placing the bio file on usb key. This does not load, the key does not even flash( tried format in fat32 and ntfs and tried usb 2 and usb 3 keys), you can hear the fan run for 2 seconds and stops and keeps doing that but never loads a file.

If you put the jumper on 1 &2  nothing happens does not show any screen or boot.

Place jumper on 2 & 3 and the machine boots up into windows in legacy bios mode and runs fine but cannont get to bios.

I have tried to use widows bios update and its say it works , but must not default the bios to defaults so still cannot get in.

Tried boot windows 10 recovery key and that does not see uefi so cannot access it either.

The power button menu as never been seen either.....

I have been trying for 2 weeks now and i am about to put the unit in the bin   HELP  Please its doing me head in !

Forgot to say i have tried VGA monitors and hdmi monitors.

Message was edited by: Davron Cater

Just wondering if anyone ever got this working as a remote: Xbox One Media Remote | Xbox

Thanks.

I recently got a NUC5PGYH and am setting it up as a NAS for myself. The first thing I did was update the BIOS to the newest version, just to get that out of the way. I then proceeded to install Arch Linux in BIOS mode and haven't had any significant problems since then. Overall, the system runs very well.

The trouble began when I attached two external USB 3.0 hard drives and started copying some large files. I only got a write speed of about 32 MB/s. Naturally I proceeded to doing some benchmarks and indeed the write speeds for both drives were between 48 and 50 MB/s only, which smells like USB 2.0. To rule out any problems with the drives themselves or USB 3.0 support in the newest Linux kernel, I attached them to my desktop computer, where I also have Arch Linux installed with the same kernel and ran some more tests. I got a sustained write speed of 100 to 120 MB/s, which is what I would have expected in the first place, because that's what I usually get with them in Windows. So neither the drives, nor USB 3.0 support in Linux should be at fault. Back at the NUC, I made sure that the drives were really recognized as USB 3.0 using lsusb.

Bus 002 Device 003: ID 0bc2:3321 Seagate RSS LLC
Bus 002 Device 002: ID 1058:25ee Western Digital Technologies, Inc.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:0a2a Intel Corp.
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

As you can probably see more clearly in the tree view, both hard drives are on the USB 3.0 bus using the correct xhci driver for USB 3.0.

/:  Bus 02.Port 1: Dev 1, class="root_hub", Driver=xhci_hcd/6p, 5000M    |__ Port 1: Dev 2, If 0, class="Mass" Storage, Driver=usb-storage, 5000M    |__ Port 4: Dev 3, If 0, class="Mass" Storage, Driver=uas, 5000M
/:  Bus 01.Port 1: Dev 1, class="root_hub", Driver=xhci_hcd/7p, 480M    |__ Port 5: Dev 2, If 0, class="Hub", Driver=hub/4p, 480M        |__ Port 1: Dev 3, If 0, class="Wireless", Driver=btusb, 12M        |__ Port 1: Dev 3, If 1, class="Wireless", Driver=btusb, 12M

A lot of searching on the forums turned up exactly nothing. Apparently it's possible in the BIOS of some NUCs to select the xHCI mode, but in my settings there is no such thing, only a USB legacy option. It doesn't do anything to my write speed. I also tried most of the probably unrelated settings concerning the power states and such. Of course I also thought of loading the defaults again and testing that, the result is always the same.

Considering that everything looks well from the operating system side and a very similar Linux installation got great write speeds on the same drives, I can't shake the feeling that maybe the BIOS on the NUC is responsible. I did install Arch Linux in BIOS (legacy) mode instead of UEFI, do you think that could have any effect at all?

Hi

No issue with DTS_MA (96/24) and with other encoded HD format but sound in case of PCM from and above 88.2/24 is broken more and more as quality is higher and higher.

It is same problem with Direct Sound and WASAPI, with foobar2k and Jriver and Kodi.

I tried latest three Intel Audio Drivers but problem is same.

win64_154518.4664.exe

GFX_WIN10_64_15.46.5.4771_BN.zip

GFX_WIN10_64_win64_154702.4815.zip

DAC is Pioneer Receiver SC-LX 59 which is working fine from other sources via HDMI too.

OS: Win10pro 1703

Update: I have tried over all HDMI port on the receiver. Surprisingly only 4K HDCP2.2 port were effected. I would emphasize that other sources can drive these ports too without issue.

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"

Folks,

I’m hoping someone can help. I’ve been struggling to get Windows 10 or Plex Embedded to output bitstream audio any high than Dolby Digital or DTS, via HDMI. I upgraded the HDMI 2.0 interface to firmware v1.66 successfully using the instructions on this support site but still no joy in either Windows 10 or Plex Embedded.

The following audio types types do not work:

Dolby Digital Plus (EAC3)

Dolby TrueHD

DTS-HD

DTS-HD Master Audio

They all either output nothing at all or flicker between PCM with no sound or nothing at all.

Any ideas folks?

For reference, the NUC is connected directly to a Pioneer VSX-930 AV receiver, which works perfectly in all sound formats with all my other equipment. Oh I should point out that I have Plex set to change display mode based on content, so that basically means the display mode will be 1920 x 1080 @ 24hz/fps.

Will NUC6CAYH get a Intel Graphics driver update to support HDR? In another thread someone from Intel posted that the HDR update will come exclusively to Kaby Lake and NUC6CAYH is technically not Kaby Lake...?

Hello all,

i have had this nuc for about 10 weeks. From the start i have had an issue with the signal to my tv.

My old nuc (from 2012) worked greate with my tv, a LG65uh664v. But my new nuc dosent give a signal out and the tv goes

to screensaver saying no video input. This happens all the times and i need to restart the nuc 5-6 times then it suddenly works.

i have disable hdmi-cec in bios, updateted to latest bios...

i have no more ides. Anyone seen this before?

BR // Daniel