trying to load win7 on this machine, but as win7 doesn't support usb3 the keyboard and mouse stop working immediately. I thought there was a switch in the latest bios do do that, but I cannot locate one. Any suggestions?

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.

Hi, I hope somebody can help, this is driving me nuts.

Native resolution for the HP LP3065 is 2560 x 1600 @ 60Hz but the Iris 650 only allows 1280 x 800. The Graphics Control panel "info" display does show the native resolution but it is not displayed as an option in display settings.

All drivers for the NUC 7i7BNH have been updated, all firmware also updated.

Connected to the NUC's HDMI port and through a dual-link DVI adapter to the display.

Setting custom resolution just states that the required resolution exceeds bandwidth, even using reduced blanking in the advanced section.

Regards

Russ

Hi!

I have found two bugs in Intel NUC NUC6CAYH with BIOS version AYAPLCEL.86A.0041.2017.0825.1152:

1. When You select legacy boot and disable UEFI boot in BIOS, then booting from Samsung SSD 850 EVO fails with "A bootable device has not been detected" or "No bootable device found". When You press F10 and select hard drive from menu, then it is able to boot just fine with legacy boot. To solve this issue, You have to also enable UEFI boot - then legacy boot works automatically.
2. If You lower AGP aperture size to minimum possible value in BIOS, then NUC will not boot at all if You disconnect monitor from HDMI port. If You want to run NUC in headless mode, without monitor, raise AGP aperture size.

Posting here just in case someone would need it.

For models NUC6i7KYK2 and BOXNUC7i7BNH what minimum and maximum memory may be use as video-memory?

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.

I have two NUC7i3BNK that both have the same issue of the ITECIR Infrared Receiver not being detected after startup. It seems to only happen when the units are started by turning on their HDMI monitor or by pressing the power button on a RC6 IR remote. If I press the power button on the unit to turn it on or select restart in windows the ITECIR Infrared Receiver shows up in device manager and a IR remote works normally. When the IR decides not to work, scanning for new devices in device manager makes no difference and the ITECIR Infrared Receiver does not show up under HID. Both units are running windows 10 and didn't have the issue when initially installed.

Hi All,

I am experiencing flickering when trying to set my display to 3440x1440.
In summary, I believe it is a HDCP issue or some statically configured expectation within the driver of how a HDMI 2.0 port should behave when communicating with it.
Below are the troubleshooting steps I have performed along with the hardware specs.

Intel NUC Hardware
Model: NUC7I5BNH
OS: Win 10 Home x64
Memory: Single Kingston ValueRAM (Part Number: KVR21S15S8/4, 4GB Module, DDR4 2133MHz, Non-ECC, CL15, 1.2V, Unbuffered, SODIMM)
HDD: WD M.2 Blue 250GB (WDS250G1B0B, 250GB, SATA III, 6Gbs, M.2 2280)
Firmware and Drivers: The latest drivers and BIOS Update listed in the 'Drivers and Downloads' page for this product, have been installed for each component in the NUC, up to the date of this post (including the HDMI 2.0 Firmware Update).

TV's:
Sony KDL-65X95000B (4K 60Hz TV, 4:2:0 8-bit, Not HDR compatible)
Sony KDL-46Z4500 (1080p 50Hz)

HDMI Cables:
Hi-Speed cables 2K/4K V2.0 from EzyHD - https://www.ezyhd.com.au/
XBox One S provided HDMI cable

Thunderbolt to HDMI Adapter:
Moshi USB-C to HDMI Adapter - https://www.moshi.com/usb-c-to-hdmi-adapter
NOTE: I understand the compatibility only states MAC products, but it works, and exhibits the same behaviour as the HDMI port, however I'm not really concerned with this (it's HDMI that concerns me)

Desktop PC:
OS: Win 10 Pro x64
Graphics Card: NVidia GTX 1080 TI

Monitor: Acer X34 Predator (DisplayPort 1.2a, HDMI 1.4)

Troubleshooting:
Sony KDL-65X95000B
1) My desktop PC has NO issues displaying the TV at 3440x1440 resolution - No flickering
2) My XBox One S has NO issues detecting the TV as 4K capable, and has no issues displaying the TV at 3440x1440 resolution
3) My FetchTV box has NO issues detecting the TV as 4K capable, and has no issues displaying the TV at 3440x1440 resolution
4) My Surface Pro 2 has NO issues displaying the TV at 3440x1440 resolution - No flickering
5) The NUC shows that the recommended display settings for the TV is 1920x1080 (even though it is a 4K TV). I have no flickering at this resolution.
6) As soon as I  set the Display settings to 3440x1440, I get the message saying that this is not the recommended display settings for this device, and I begin to get flickering. It is stable at 1920x1080.
7) I have also tried various refresh rates, 30Hz, 59Hz, 60Hz etc....but still get flickering.
8) Various power cycle methods on the TV and NUC including - Rebooting, Sleep, Shutdown, Removing power sources, changing inputs, powering up the devices in specific sequences etc..., sometimes provide stability at the 3440x1440 resolution (I have more stability using the Thunderbolt to HDMI Adapter), however even when its stable, i can verify its still not working poperly when trying to watch 'Foxtel Go', where I get no picture (see further down regarding Foxtel Go)
9) All HDMI ports on the TV have been tried
10) CEC has been tried ON and OFF on the TV
11) All display and sound modes have been tried on the TV
12) I have tried the TV's supplied HDMI splitter which produces the same reults
13) When using other HDMI inputs that aren't HDMI input number 1, it sometimes switches the TV's inputs to HDMI 1 (may have been more prominent before I disabled CEC)

Foxtel Go
1) I cannot watch any channels in Foxtel Go when using it through the Sony KDL-65X95000B using HDMI at 1920x1080 resolution (Thunderbolt to HDMI Adapter doesn't work either, however this is expected behaviour so it's not a consideration)
2) I have tried all of Foxtel Go's troubleshooting steps for this particular issue, however I have verified it is not an application issue - see the next 2 points
3) When I plug the NUC in to my Desktop PC monitor, Foxtel Go works
4) When I cast my desktop on the NUC to a chromecast, which is also connected to my Sony KDL-65X95000B TV, I cannot watch any channels. However, as soon as I unplug the HDMI connection from my NUC to the TV, and still casting to the chromecast, I can watch channels
5) Its clear that there is an issue with the HDMI 2.0 here

Sony KDL-46Z4500
1) When using HDMI, I just get a black screen - doesn't work at all at 1920x1080
2) When using the Thunderbolt to HDMI Adapter, it works at 1920x1080 (Foxtel Go doesn't work as expected as we are using the Thunderbolt to HDMI Adapter).

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/

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 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.

Hi all, I am running a NUC6 machine and wanted to see what options are available for setting up IR function with a remote. I have a simple Roku-style remote that I originally used with Flirc. The goal is to be able to map the IR buttons to specific key presses, which subsequently are captured by another program to trigger functions. I looked at the thread linked below, but it's not working for me. Is this no longer possible to do in a gen 6 NUC? Thank you.

pro-tip: if you're having trouble reprogramming the nuvotron IR receiver in the NUC to work with Eventghost

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 tried to reset my newly bought NUC, Chose remove all files (full clean) and I have an SSD in and chose to remove for both drives (the SSD does not have anything so it should be fine), When it got to 3%, it said "there was a problem resetting your PC. Nothing was changed"

I removed the SSD and tried it again, was able to see 66% and then it went back to "there was a problem resetting your PC"

How do i install the windows 10 back to this NUC?

For models NUC6i7KYK2 and BOXNUC7i7BNH what minimum and maximum memory may be use as video-memory?

are there any labs that support Nuc's in Israel?

(i have a D54250WYK  and its fan is malfunctioning)

Die Intel-Treiberaktualisierungs-Software findet neue Treiber, obwohl diese schon installiert sind. Beispiel: LAN-Treiber LAN_WIN10_64_22.6.exe. Auch eine Deinstallation und Neuinstallation des Treibers und der Software brachte keine Hilfe.

NUC7i3BNH

BIOS v052

Intel-Treiberaktualisierungs-Software 2.8.2.2

Windows 10 x64 Home Premium

Alle Microsoft Patches sind eingespielt. Die AV-Software ist ausgeschaltet.

Wer weiß Rat?

Hey Everyone,

This seems to be a fairly common issue, but I'm experiencing a huge amount of fan noise on my NUC6i7KYK.

I've tried:

• Updating all software/drivers and restarting
• Clearing out the fan with compressed air
• Unscrewing the blower, lifting it gently, and ensuring that no cables are hitting the fan

This began to occur around the same time as I updated the bios, but I'm not certain how soon after the bios upgrade this issue first presented.

I've attached a picture of the board, along with a noise sample taken from the device.

Any advice or suggestions on how to fix this would be wonderful

NUC6i7KYK experiencing the symptom of when the display goes to sleep, all my windows shrink to about 1024x768 and, upon waking, are all bunched-up in the upper left corner of the screen.  Here's what I've done to try to troubleshoot:

1. Install latest Intel graphics driver from here:  https://downloadcenter.intel.com/product/89187/Intel-NUC-Kit-NUC6i7KYK - done.  At the time, the latest version was version 15.40.23.4444.  Problem persists.
2. Search the internet for similar problems - found this:  http://www.tomshardware.com/forum/id-2459135/u28d590d-nvidia980-displayport-powersave-shrinking-windows.html - this involves editing the registry and forcing d70 (hex for 3440) and 5a0 (hex for 1440) values into PrimSurfSize.cx and PrimSurfSize.cy categories.  Seemed to work until Intel driver was updated to latest version (15.40.24.4454) then problem returned.
3. In frustration, did a complete re-install of Windows 10 Pro (including all patches and SW stack) using only latest drivers installed via Microsoft.  Problem GONE, but graphics were a bit "glitchy" - forced to install Intel Graphics driver to resolve those problems.
4. Installed latest Intel graphics driver (15.40.24.4454) and problem returned!  I did notice that, post install and reboot, the Intel graphics driver pops up a calibration window that appears to set some variable to...1024X768.  But, I cannot find where to change this, despite looking for several hours.
5. Found this post on this forum (https://communities.intel.com/thread/63548) where NUC5I5RYH owners experienced the exact same thing, which was cured by an update to the Intel graphics driver.

System Configuration:

• Samsung 512GB 950 Pro (running latest firmware)
• 2X16GB G.Skill 2800 MHz DDR4 (running @ 2400 MHz for now)
• Windows 10 Pro, Version 1511, Build 10586.318 (fully updated and patched as of this AM)
• Monitor LG 34UC97S (Ultrawide) attached via DP 1.2 (tried 2 different cables, both verified good on another system)
• Graphics Driver:  Intel 20.19.15.4454 (most current as of this AM)

In addition, under Advanced Display Settings -> Display Adapter Properties -> Monitor, my monitor shows up as "Generic PnP Monitor".  This is interesting because, while running just Windows 10, it properly showed up here as an LG 34UC97.  I just tried to re-install LG's monitor driver (which claimed success) and rebooted, but the monitor still shows up as Generic PnP Monitor.  Why this is interesting is Intel's HD Graphics Control Panel reports (correctly) that the selected display is a "Digital Display LG Ultrawide".  Thus, I've got conflicting information.

Please help - this is making me crazy, is a sinkhole for time, and forcing the display to remain awake is not especially power-efficient...