i've just bought this nuc to reuse my ssd from my dead laptop.

the only problem is that it boots window 10 only if the chipset SATA option is set to AHCI, if i set to Intel Optane it looks for other media but doesn't see my hard drive nor boots windows.

With this problem i can't neither install the optane memory software.

is there a way to set the correct SATA option and boot on my windows hard drive without reinstalling the os?

High Dynamic Range (HDR) displays have much higher contrast (the difference between bright highlights and dark areas) than standard displays.  Most HDR displays also support wide color spectrum, which brings a greater amount and variety of color. These advancements bring lifelike color and clarity, providing an immersive display experience. Please see below for details on Intel’s HDR support:

• Ultra-HD Blu-ray™ HDR is available today on 8th Generation Intel® Core™ products with Intel® UHD Graphics 620 or better.

o   7th Gen Intel Core systems with Intel HD Graphics 620 or better are also supported. (must have HDCP2.2 support – please check your manufacturer’s tech specs for support details)o   For UltraHD Blu-ray disc playback on these Intel-powered PCs, the requirements include:

• Operating System: Windows® 10 (any revision)
• Intel Integrated Graphics (not a discrete card)
• An UltraHD BluRay optical drive
• HDR-capable TV or monitor, preferably with UltraHD™ Premium certification
• Connectivity:
  • For HDMI: an LSPCON based motherboard (i.e. a board with HDMI 2.0a, a list of supported motherboards can be found here.)
  • For DisplayPort: a DisplayPort based HDCP2.2 monitor(1), and motherboard with DisplayPort output
• A supported UHD-BD player application.
  • Currently, the only supported and certified UHD-BD player is Cyberlink PowerDVD* (See here for detailed requirements).
  • More supported software expected soon.
• Software Requirements:
  • The latest version of Intel Management Engine, available at the Intel Download Center, here. (Although this link is designated for NUC users, it also applies to all manufacturers and supports 7th Generation Intel Core and newer platforms)
  • Intel SGX Platform Software (installed through PowerDVD*, please ensure SGX is turned on in the BIOS settings)

• Windows-based HDR is expected to be rolled out through Microsoft Windows® 10 Fall Creators Update.  Support for Windows® HDR usages, like HDR streaming content, will be available on 7th Gen Intel Core systems or newer with Intel HD Graphics 620 or better. (must have HDCP2.2 support – please check your manufacturer’s tech specs for support details)

In-depth information on Intel’s HDR support coming soon and will be posted to our Intel Support Web site within a month.*Other names and brands may be claimed as the property of others.(1)List of DP HDR-10 monitors with HDCP2.2 and with Local Dimming:

• Dell UP2718Q (with firmware update)

  List of DP HDR-10 monitors with HDCP2.2:

• Acer H277HK – HDR10  (latest version, look for the HDR sticker on the box)
• BenQ SW320 – HDR10
• LG 32MU99-W – HDR10

The 7th Gen Intel NUC series is included in the above.

From all my reading on Kodi Forums and AVS seems like there are issues on Kaby Lake CPUs with 3D playback on the HDMI 2.0 port.  Has this been looked into or addressed?  I have preordered an i7 NUC to replace my 5th Gen NUC and this would be an issue for me.

I have all my 3D movies stored on my server as ISO files.  I play them back via Kodi and PowerDVD 16 right now.

My Intel NUC NUC7i5BNH frequently has bluescreens and apps (Chrome, Opera, Adobe Lightroom, iTunes, MMC/EventViewer...) are crashing suddenly or report errors in application log (ZeroConfigService.exe [Version: 19.60.0.0])

The lastest minidumps (from today) are attached

HW: 1x Samsung SSD 850 EVO (500GB), 2x Cruical CT8G4SFD8213 RAM (2x, 8GB, DDR4-2133, SO-DIMM 260 pin)

BIOS Version 0049

Windows Edition: 10 Pro 64-Bit Version 1703

Regards

Holger

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/

This is lengthy but for those who read it and for Intel, trying to avoid any unnecessary questions.  Been working in this for a long time.  I think eventually I get somewhere, but still not solved.

I am having trouble with my infrared port on my NUC.  Problem I've read others are having as well.  My problem is specifically around turning the unit on from sleep.  Other buttons seem to work including powering it off.  To start, my setup:

• Intel BOXNUC7I3BNK NUC Kit
• Corsair Force MP500 Series M.2 SSD 120GB Internal Drive (CSSD-F120GBMP500)
• Ballistix Sport LT 8GB Kit (4GBx2) DDR4 2400 MT/s (PC4-19200) SODIMM 260-Pin - BLS2K4G4S240FSD (Gray)
• Windows 10 Pro all updates
• ITECIR and eHome Infared transceivers both show under HID in Device Manager
• Connected to a Panasonic Plasma with HDMI cable, no CEC.

For drivers:

• All Windows updates
• BIOS at latest 0051 version
• Have all drivers as of today on this site: https://downloadcenter.intel.com/search?keyword=NUC7I3BNK

Only software on this system is KODI.  And frequently on my many Windows re-installs didn't bothering even with KODI.  The reason I bought the NUC was it would run Windows, and came integrated with infrared.  Infrared doesn't work?  No value.

Bios Settings of relevance:

• Enhanced Consumer IR checked
• Unchecked HDMI CEC Control due to other forums with people troubleshooting IR that sounded like this may tie to loosing the IR all together.
• S3 and S4/S5 set to allow wake on CIR
• Power set to Max Performance

What's happening:

I have a number of remotes, all of them 95% of the buttons work, including putting the device to sleep/off, only 1 (Harmony) can actually bring the device out of sleep and online again but not the remote I want to use.  The remotes I'm testing with:

• Harmony 880 programmed as a Microsoft Digital Media Remote.  This remote has zero ability to turn on/off my XBox 360, however it's discrete on and off, as well as it's power toggle button will turn the NUC on and off.  All other functions work as well on the NUC.

• Microsoft XBox 360 newer media remote.  All functions work on this remote except power on (pressing the XBOX button on top right).  This will turn on and off an XBox 360 though.  I mention this because there seems to be a difference between how/what signals the buttons are sending.  The Harmony can't control the XBox but can the NUC.  This remote can control the XBox power on and off and all functions except power on for the NUC .

• Also have the older XBox 360 media remote.  This one functions the same as the newer XBox 360 media remote above.

According to Intel's ecosystem list, the last two remotes above are supposed to be compatible:

Things I've tried without any change in intended results to get the power on working.  Each was done with a refresh of the OS so no overlaps:

• Windows 10 out of the box.
• Windows 8 with as many drivers as I could get ot work.  The IR drivers did install and show the CIR and eHome drivers.
• Tried the MCE remote mapper tool but that seemed to have no impact.  Tried setting the X button to wake but nothing. 
• Tried going in registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{745a17a0-74d3-11d0-b6fe-00a0c90f57da}\Four-digit_number and setting ForceHCResetOnResume to 1.
• Tried going in registry Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57da and changed CodeSetNum0 to 0.  Also tried with just that change and deleting CodeSetNum1 - 3
• Tried going in registry Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57da and changed CodeSetNum0 to 8 as some say.  Also tried with just that change and deleting CodeSetNum1 - 3
• Tried in regedit  going to key "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57da"  and in "ReportMappingTable"  change the line "0c,00,00,00,03,82,00," to "0c,00,00,00,03,81,00,".  Sounded more for shutdown but tried it.
• On the eHome Receiver in Device Manager I have it set to not allow the computer to turn off the device to save power.  The open to allow to wake is grayed out.
• I decide well why is everyone saying to go to the RC6 only registry entry I go to the RC6 XBox 360 area instead at Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57df.  I change the "0c,00,00,00,03,82,00," to "0c,00,00,00,03,81,00,".  After rebooting remote doesn't work to send to sleep.  OK that's something that it effected the remote.
• Sticking with this, I try Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57df.  I change the "0c,00,00,00,03,82,00," to "0c,00,00,00,03,83,00,".  This time it shuts down the computer completely.  No ability to turn it back on again from remote as usual.
• Then tried Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57df.  I change the "0c,00,00,00,03,82,00," to "0c,00,00,00,04,04,3D,".  This time Windows asked if I wanted to shutdown.  When i clicked enter it shutdown but couldn't power on still with the remote.

This was supposed to be a simple project for my father who is in a home to watch movies and enhance his life.  It's turned into a two month nightmare for me.  I know there are many threads out here with similar problems.  Can someone please help?  And the point of my effort in documenting this is I have all the drivers, bios update, HDMI 2.0 update, etc.  No stone left unturned that I know of.  Any help?  I can no longer return this to Amazon as my time has expired to do so.  Thinking the trick is in the XBOX360 RC6 branch of the registry "maybe?" but can't figure it out.  Still scratching my head why my Harmony remote turns it on and off with the power toggle or the power on and power off discrete commands.

Note since I've already spent a lot of money on remotes that don't work and actually have another NUC on it's way to test it, glad to physically send Intel whatever they want to test.  The NUC, the remotes, whatever.  This would eliminate Intel "not being able to reproduce this problem" that I see lots of people having in various ways.

Thoughts?

Thanks.

Steve

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

I have a kiosk system I setup and due to the NUC's inability to come out of sleep from my remotes I'm trying ready mode.  Problem is even if I disable password on startup, password to resume from sleep or hibernation, when coming out of ready mode it requires me to login again.  How do I stop this?

Thanks.

Steve

I just bought an i5 NUC 2 days ago, 8Gb ram.  Tested normal HDD at the shop and everything ok.

At home, updated to latest BIOS (WYLPT10H.86A), I tried with my SATA OWC Extreme Pro 6G 240GB SSD, and it is not detected.  Tried again with other SATA SSD, here is the result:-

1) OWC Extreme Pro 6G 240GB = not detected

2) Intel 520 480GB = not detected

3) Crucial M550 1TB = detected after 10 sec delay at POST

4) Crucial M500 960GB = detected immediately, fast and furious.

5) Samsung 840 Evo 1TB (mSATA) = detected immediately, fast and furious.

Out of 4pcs 2.5" SSD, only Crucial M500 is working flawlessly. The rest is having problem of slow detection or no detection at all.

This is annoying, and after trying around, i found the real problem of this SSD issue on all intel NUC, which later i found out many people is also facing:-

The short SATA cable in the NUC is NON_STANDARD type.  The connector is standard, but the pin arrangement is not.  Try this, take out that short NUC SATA cable and install it on a normal PC - NONE WILL WORK.  Next test, replace the short NUC SATA cable with a normal SATA cable - again NONE WILL WORK.  Intel has changed the cable standard, and then use the female SATA connector in the NUC to revert it back to "normal".  By logic this should work; but in reality, many SSD suffer from this.

However, a good news is that the mainboard of the NUC has no problem, i try remove the NUC hdd caddy, replace with normal SATA data cable and an external SATA power cable to power the the SSDs.  Guess what, ALL SSDs are detected and running perfectly !!

So the problem here is very clearly, not at the mainboard, but starts from the non-standard SATA cable until the female SATA slot connecting to the SSD.  I don't know how intel is going to do about this, even their own 520 SSD is not detected.  BIOS update may help, but intel has to test all SSD in the world to guarantee the compatibility.

From our consumer part who is tired of the SSD issue, besides waiting for the mercy of intel, the immediate way to overcome this is to remove the default cables + hdd caddy and replace with normal SATA data + power cable.  normal SATA data cable is easy, but the power cable may not, you need to find both end female slot power cable, which is almost non-existent.  One possible solution is to get the 1 male to 2x female sata power cable splitter and just use the 2x female end. Best if you can get someone to custom made for you a short female - female cable.

I am running my NUC with BIOS .050 and want to downgrade it to .047

No matter how I try to downgrade, it seems impossible for some reason, even using the jumper method.

I was on BIOS 51, tried to downgrade to 47, as it has the previous UEFI graphics, but the BIOS says that it's incompatible BIOS (despite it still has the same ME version).

Tried to downgrade to 50 - worked.

Tried from 50 to 49, incompatible.

Tried the F4 method - getting blank screen when booting, doesn't do anything  (tested on 4k TV or 1080P monitor).

Tried removing the security jumper (following the exact instructions here)  - getting blank screen when booting, doesn't do anything  (tested on 4k TV or 1080P monitor).

I have asked other members in the NUC forum and they have the same results.

Is there any way to downgrade to .047?

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.

Hello,

I have an Intel NUC5PPYH and I cannot have a flawless duplex printing. I am currently running Win 10 Pro 64 bit built 1703. Whenever I try to print a 2-page document, created on MS Office 2010 Word, I end up with a sheet of paper where the front page print does not 100% overlap the print on the back page. Lets say that the front page has 32 lines of words typed and the back has also 32 lines of words typed. In an ideal situation, the front print (i.e the first 32 lines) should overlap the next 32 lines. In my case, printing of the front page starts lower than usual (4 lines lower to be precise) whereas the back page printing starts normally on the top of the page, thus I am having a sheet of paper where if you place it under any light, you could see that the 2 printings (front & back) do not overlap. Sorry for my english, this is the best way I can describe the problem, treat the document in question as an x-ray and place it under normal everyday lighting. Every paper has some degree of transparency.

I am using the default settings in MS Word, margins, spaces etc are used as is.

I was facing the same problem when running Win 10 Pro 64 bit built 1607. I updated to built 1703 hoping for a fix. My printer was an HP DeskJet Ink Advantage 4535 AiO, which had automatic 2-sided printing and was connected to my NUC through usb cable. I had to return it to the store. I have also used a Samsung Multifunction Printer Xpress M2885FW which also had automatic 2-sided printing, connect it through usb, the problem still persists.

Moved my NUC to a place where another HP printer which also had automatic 2-sided printing, unfortunately, problem persists.

I have also converted the aforementioned 2-sided file to a PDF, still facing duplex error.

I have also uninstalled Win 10 Pro and installed Win 7 Ultimate 64 bit. I didn't solved the problem.

While running built 1607 (Win 10 Pro 64 bit) I also used MS Office 2007 and 2016 Pro, faulty duplex printing continued. I am currently on built 1703 with MS Office 2016 Pro.

Purchased heavier paper (120gr instead of 80gr), thinking that it may be a roller issue (or whatever mechanism is used to grab the paper), didn't solved it either.

I have also installed Libre Office and used it for printing only documents that were created in MS Office and magically the problem was solved! Used Libre to open other files created under MS Office, and printing was fine.

Lastly I have also emailed the above document to a couple of friends that I knew they had printers with automatic 2-sided printing, asked them to not change any Office parameter and print it. 2-sided printing was fine.

Looking forward to a solution.

Thank you.

I am having issues with my NUC7i7BNH where the screen most of the times is not coming back out of sleep mode (sometimes it does work as how it should be).

The keyboard seems still to be responsive (numlock light is still going on and off), but the monitor does not come back. I installed the latest version (4678) of the Intel Graphic drivers and all other drivers are the latest as well.

I am running Windows 10 Pro version 1703. I have seen that there are quite some users of the NUC7i7BNH that reports on crashes of their NUC. Maybe mine issue is the same, but I don't know. The only thing I can think of is long pressing the power button to restart the NUC, but I think the NUC is not crashed, but I can't tell for sure as the screen remains blank.

One other thing that I find particular is that the Intel Driver Update Utility (V2.8.0.7) shows an unknown version number for the following two drivers:

- Thunderbolt Bus Driver for Intel NUC Kit NUC7i5BN and NUC7i7BN

- Intel HD Graphics Driver for Windows 10 for Intel NUC7i3BN, NUC7i5BN and NUC7i7BN

Hope someone can inform me what I can do to resolve the issue that my screen does not come back when in sleep.

I have a nuc syh 6i5 windows 10 with a whea uncorrectable error, I upgrade the bios to the last one, I control the two 8 gb of ram, I test the hard disk, I upgrade the driver, I control the  registry. But every time after at last 2 minute after the restart the whea problem return. What I can try to correct the problem, some other person have the same issue?

i've just bought this nuc to reuse my ssd from my dead laptop.

the only problem is that it boots window 10 only if the chipset SATA option is set to AHCI, if i set to Intel Optane it looks for other media but doesn't see my hard drive nor boots windows.

With this problem i can't neither install the optane memory software.

is there a way to set the correct SATA option and boot on my windows hard drive without reinstalling the os?

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?

hello, on my new NUC the mouse is lagging, i tested several mouses usb, tested bluetooth

mouse, updatetd drivers so far it works, no positiv result.

Please help, my motherlanguage is german

Thanks a lot best regards

I am experiencing problems using the AMT SOL feature on a NUC5i5MYHE. Here's the symptom:

• Windows 7 just hangs when using the port (e.g., using PowerShell). If I configure a timeout, I just get the timeout, but no serial output.
• Linux experiences a long delay after printing the characters, but it also complains about unexpected interrupts. Using the "irqpoll" cmdline option, it works fine.
• A baremetal kernel works fine without interrupts, and even the interrupt-driven configuration works if you find the correct interrupt to use.

Interestingly, the interrupt that both Linux and Windows report (17) does not match the actual one that can be observed (19). Furthermore, IRQ 19 is also the SATA interrupt, which makes me wonder if 17 is actually the correct one, but for some reason it is not being used.

This happens on several machines of this model, and I have tried multiple BIOS versions, including the most recent one (86A.0038).

Has anyone else seen this? I would really appreciate some help

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

Hi there,

Working with Device Guard on NUC5i5MYBE´s and having a problem clearing UEFI and Secure Boot data after some tests with UEFI lock and signed policies...

The problem is that the NUC is not able to boot from UEFI devices with Secure Boot enabled in the BIOS/Firmware, if I disable Secure Boot everything works in legacy mode (Before the UEFI Lock, everything worked with UEFI and Secure Boot from DVD, USB and PXE boot in UEFI mode.

To reset to NUC i did a BIOS Recovery by the Security Jumper and a USB device with the latest BIOS currently 038, and even after this it seems like there is some information left in the BIOS

In did reproduced this on another NUC with same result, so now I have 2 NUC´s that cannot boot using UEFI Secure Boot

So, any input on how to clear the UEFI, Secure Boot?

Kind Regards

Jesper Hanno