There are  pops and ticks noise when the sound start (NUC7I7BNH, Windows 10 x64, Apple earpods). This noise is very annoying. Sometimes peaks of ticks deafen me.

I think the issue was about the audio card power management but I found nothing in the current Realtek driver Fix for Realtek sound popping and/or high pitched tone/squeal | NotebookReview

Intel, make something, quiclky, PLEASE

NUC 5i7RYH

Kingston G4 8GB USB created by Standard Ubuntu USB-utility with Ubuntu 17.04

The USB is found by BIOS but it won't boot from it.

I have tested several BIOS settings and updated BIOS Firmware too.

Any ideas?

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"

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 just setup a NUC7i5BNH with Windows 10.   Everything is working fine except the computer will not go to sleep.  Even if I go to the windows menu and choose sleep in the Shutdown/Restart menu.  The computer will proceed to go to sleep but then go back to the sign in screen within seconds.   Power and Sleep in the control panel have been set to 5 minutes and 15 minutes respectively.   The screen never turns off in addition to the computer never gong to sleep.   I have made another non-admin account but the computer will neither go to screen save or sleep in this account either.   I have played around with powercfg but never see anything particular useful but I might not be using it correctly.    

In device manager, I have set the wireless network adapter to never allow this device to wake the computer.   I still allow the computer to turn off the wireless to save power.  Even though I am using Wifi, I also turned off all the Wake on LAN options (Magic Packet, Pattern Match, Link Settings).

Not sure what else to do.   I have updated drivers from the intel website.  Although for some reason, I install the Ethernet Connection (4) I219-V driver seeming successfully but everytime I re-scan or go back to the website, its says that I still need to do the update.  Not sure if this is related.

Any suggestions?

Thanks

I've been using this Intel NUC for 2 years without any issues. This issue started 3 days ago.

The display suddenly goes blank. My monitor complains that there is no HDMI cable connected. The NUC's blue power button continues to stay on - I can hear the fan. The unit does not seem to be overheating. I cannot shut it down (by pressing the power button for a few seconds). I have to switch the power off manually. Once done, the NUC unit does not power back on for a few hours (over night).

Initially, I thought it was an issue with the memory, so I purchased a new one. However, I still have this issue after installing the new memory.

Few things off the top of my head.

1. The issue does not seem to be based on what application was being run when it happens.

2. The issue seems to happen after the computer is on for 8 to 10 hours. (It has always happened at night time)

3. After this happens, I am unable to restart the unit for quite a few hours. (It has always started up the next morning)

I've attached my system information based on the SSU.exe utility.  I'm happy to provide any other information if needed.

Thanks for your help.

Akash

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.

I am having issues with some audio, particularly in games, when my TV is set to 4k@60Hz resolution.  I mentioned this in the massive flickering thread and cvare told me to break it out, even though I think this is all related.

Setup: NUC7I5BNH, Vizio m55-C2 4k TV, Audio either through TV or using ARC to Sony XT:HT1 soundbar. 

Problem: When I have the resolution set to 4k@60Hz, ifI start a game in full screen mode that is at a different resolution than the desktop, I get no sound.  If Windows resolution is set to 1080p in the Intel Graphics Settings, the sound is fine (but I don't want to change settings and reboot every time I want to pay a game).  In one of the games, I can select windowed mode and the sound then works.  However, when my resolution is set to 4k, it only displays in 1/4 of the screen so there is obviously another problem there.  From looking around online, it sounds like others have experienced this before and it might be an HDMI handshake issue or some problem caused when trying to switch to a different resolution. 

Games: LEGO Star Wars: The Complete Saga

LEGO Star Wars III: The Clone Wars

LEGO Star Wars: The Force Awakens (this is the one that the audio works in windowed mode but the video is weird)

The LEGO Movie Videogame

So the symptoms are different than with the flickering issues, but it all seems related to HDMI/driver issues.  Is this a problem with the LSPCON chips in these NUCs?

Hi Intel-Team,

we have bought around 80x Intel NUC7i7BNH for our company, all with the same configuration and all with the same customized basic-installation of windows 10 Professional.

- Intel NUC7i7BNH

- 256GB m.2 SATA-SSD Samsung MZNLN256HMHQ PM871a

- 1x 16GB DDR4-2133 RAM Samsung M471A2K43BB1-CPB

- BIOS-Version 0052

We have problems with several freezing NUCs, some working fine (SSU Example: NUC_OK.zip) and some just freezing (SSU Example: NUC_fail.zip).

For more understanding, I mean a system that just stop working with a freezed screen, non functioning mouse and keyboard and no reaction on the power button unless I press it for 10 seconds to hard reset it.

- We installed the systems after updateing the BIOS to version 0048 and later to 0052.

- I "cross-changed" the peripheries (RAM, SSD, PSU) between my both testing machines the freezing was always on the same System

- I installed a Crucial MX200 m.2 SSD instead with the same freezing again

- we recognized that the systems only freezed, when the automatized McAfee-Antivirus fullscan of the system (McAfee Enterprise 8.8) was running and with that run the prozessor ist at 85-100% load, but ...

... 1. the "OK"-System have a lower workload with ~60-90% as mentioned don't freeze

... 2. without that active scan but with active On-Access-Scanner, with AIDA stresstest (CPU at 100%) the System is stable

... 3. without that active scan but with active On-Access-Scanner, with AIDA stresstest (CPU at 100%) AND several copyjobs the System is freezing after a short period

... 4. without that active scan but with DEACTIVATED On-Access-Scanner, with AIDA stresstest (CPU at 100%) AND several copyjobs the System is stable

... 5. now I deactivated Hyperthreading in BIOS and the freezings are gone

Now I am totally confused because it seems that it is no thermal problem, no SSD problem, no memory problem, no McAfee problem nor a combination of it, especially since the known hyperthreading-issue should be fixed with BIOS version 0047

I am not sure how much of our Systems are affected since not every user is reporting properly or sees that problem as the same because we have the BSOD-problem too when the System send the monito to sleep and do not wake it up again (except the energie-savings are deactivated).

btw. I obliterated the IP-Informations in the SSU-Files.

I appreciate some help and/or informations about that issue.

With kind regards DarkTapo

I have tried installing the Windows 10 Fall Creators Update (16299.15 and 16299.19) on a NUC5i7RYH both by using Microsoft's Windows 10 Installation Media Tool to create a USB stick and also by using the Windows 10 Update Assistant.

Both times after installing the Fall Creators Update, I have no internet connection.  Although Wi-Fi is switched on, it doesn't detect any Wi-Fi networks and just says 'No WiFi networks found' in Windows Action Centre.

The adapter settings in Control Panel > Network > Change Adapter Settings, shows a red cross next to Wi-Fi.

The Windows Network Diagnostics trouble-shooter is unable to fix the problem and just says "Problem with wireless adapter or access point - Not fixed".

In Device Manager > Properties > General Tab, it says "This device is working properly".

Wi-Fi details in Settings > Status > View Your Network Properties, show no MAC address and status as 'Not Operational':
Name: WiFi
Description: Intel(R) Dual Band Wireless-AC 7265
Physical address (MAC): 00:00:00:00:00:00
Status: Not operational
Maximum transmission unit: 1500
IPv4 address: 169.254.208.191/16
IPv6 address: fe80::<SNIPPED>/64
DNS servers: 192.168.1.1, 192.168.1.1
Connectivity (IPv4/IPv6): Disconnected

IPConfig from PowerShell shows 'Media disconnected':
Ethernet adapter Ethernet:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Wireless LAN adapter WiFi:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Wireless LAN adapter Local Area Connection* 10:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

The NUC5i7RYH has a Intel Dual Band Wireless-AC 7265 Wi-Fi card.  On Windows 10 15063.674 it was running driver version 19.51.5.3 (Windows Update version), but this doesn't work on Windows 10 16299.19.  I tried installing 'WiFi_20.0.2_PROSet64_Win10.exe' from the Intel Drivers section of the website (19.51.7.2), but that makes no difference and Wi-Fi still doesn't work on 16299.19.  At the moment I've had to restore 16299.19 back to 15063.674 so that I have internet access again.

I also went through all the steps HERE, but am unable to determine what's wrong.

As a side note, the Intel driver version and date HERE needs updating, as it still shows 19.70.0, 9/3/2017 as the latest driver, instead of 20.0.2, 10/17/2017.

Hello!

Is HDR support in windows 10 creators update supported for this model?

I cant find anything to activate it? In the HD control panel i cant change color depth and so on..

Do we need graphics driver with WDDM 2.2?

Kind reegards

Jake

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?

Hi everyone,

I've recently purchased a NUC7i3BNH and after installing memory and SSD I tried to connect to my Samsung UHD TV model UE55KU6400 and only got a black screen, no intel logo, nothing.

Then I tried to plug to my older Phillips TV and worked fine, installed Windows 10 and then tried to hot swap the cable to back the samsung and voila! Glorious 3840 x 2160 working just fine.

However, if I change source or turn off the TV and try to get back to Windows 10, I get a weird pink screen for a second and then a "No source" message from my Samsung. If i try to reboot the NUC, only blank screen again. The only way to get the screen back to the Samsung, is by doing the hot swap trick with the older phillips.

I'm no expert but I've spent the weekend learning about HDMI handshake issues and have tried updating all the drivers, the DEVCON trick and nothing works apart from hot swap. As that is not a practical solution I would like to ask if anyone can help.

Thanks!

Bonjour. Existe-t-il des modèles d'Intel NUC qui ne sont pas physiquement équipés d'une carte WiFi ?

I apologize if this is a repeat, I am new to your discussion group.

I have an NUC7i5bnh, which is running Centos 7 and I don't have any sound.

I sometimes get a short pop when I do one of the two speakers.

My NUC goes through an IOGear HDMI KVM switch to an Acer monitor and my speakers are plugged into the monitor.

When I switch to the other PC on the KVM, there is sound.

My next test is to switch the 2 PCs, in case the KVM is bad; but I wanted to get this question out there.

Jonathan

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"

So this issue has been bugging me for a while now but I have ignored it for the most part as I have always found another way to get my stuff going. However, now I have tried to pair about five different Bluetooth devices and I am convinced that my Nuc's BT is broken. My device is a Nuc 6i3SYH with all the latest drivers (re-)installed.

The Bluetooth problem is basically that its range is atrocious. For the Nuc to find the devices I want to pair, the have to be in DIRECT proximity of the computer. Even 10cm away is not working as the devices will not be found. Needless to say, should I manage to get the pairing done, once I take the respective device further away the connection is lost instantaneously. So far I have tried a BT mouse, a BT keyboard, a Dualshock 4, a BT remote and my Bose QC35. The Nuc works with none of them.

I am kind of pessimistic about finding a solution but if there is one, you are welcome to tell me about it. Help me Intel Community - you are my only hope.

Cheers!

Since 2014 I have a NUC54250WYKH1 with a 240GB Intel mSATA SSD and a Western Digital 1 TB hard drive in my NUC.

After a restart the hard drive doesn't show anymore in device manager. It is invisible in my system. Everything else is fine.

Any advice how to get my drive back, please?

I have the Skull Canyon NUC, Razer Core, GTX 1080 and just updated to the Windows 10 Fall Creators update.  As soon as I got back to the desktop after the update, I noticed as soon as I right clicked on the desktop, it sounded as if I had repeatedly connected and disconnected a USB device, as it kept making the connect/disconnect sound.  I initially thought it was a bad USB driver or something, so I disconnected everything but the Razer Core, but it still happened.  I then went to device manager, showed hidden devices and got rid of anything that wasn't being used and tried to re-install what I could, but still the same issue. 

I then tried to check the display settings and when I went in there, I will usually see two displays as I have the Razer Core, with GTX 1080 as my primary display connected to it's own monitor and the onboard Intel 580 graphics card with a headless HDMI connector attached.  The display settings show the two displays, but after the Windows 10 update and what I thought was USB issues because of the connect/disconnect sound, it seems that the Intel 580 would be the device that actually disappears as in the display settings screen, the two monitor setup would appear and disappear along with the device disconnect/reconnect sound from the OS.  I removed the headless HDMI connector from the Intel 580, but that did nothing. 

I then just disabled the Intel 580 graphics card in Device Manager and that seems to have solved the disconnect/reconnect issue, however, now I can't use my onboard graphics card, which has been an issue sometimes when the Razer Core has randomly disconnected for some reason. 

Has anyone else had an issue like this?  And is there any possible fix with drivers and/or firmware for the NUC to solve this?  I'm running the latest drivers/firmware currently. 

Any help is appreciated.

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.