Hi, I've recently purchased a few i3 and i5 NUCs (NUC5i3RYK & NUC5i5RYK) for the office and have encountered an issue that seems similar to some common issues on the forum on internet in general, however I can't find any answers.
The issue is with powering on the NUC from a USB keyboard or mouse from S5 state. I noticed when I first set up a few NUCs the power on from USB seemed to work, but it has since stopped. I have not changed any settings. Most other discussions seem to be around powering on from USB remotes and on older models.
Details around my setup:
I have installed Windows 7 Pro (with SP1) in legacy mode, and installed all Windows update. I have downloaded and installed all the latest drivers and BIOS from this month on the Intel NUC download page. I have supported Kingston memory (4GB - KVR16LS11/4)) and Crucial (M550 M.2 128GB) SSD installed. I have checked in Windows Device Manager that the checkbox for 'Allow this device to wake the computer' is checked for both the keyboard (Microsoft Wired Keyboard 600) and mouse (Microsoft Comfort Mouse 4500). In the BIOS I have 'USB S4/S5 Power' checked, as well as 'Wake on USB from S5'.
I have also found that in some cases the keyboard/mouse will not even wake the NUCs from S3 state. I have to press the physical power button on the computer.
I have the i5 NUC at home running Windows 8.1 which for while the power on from USB was working fine, even with a wireless keyboard, however that too has since stopped working and I have tested with a wired keyboard which made no difference.
I'd like to roll these out across the business as our standard desktop as I think they're cool little devices that are more than sufficient for Office applications and web browsing (95% of staff), however as we plan to VESA mount them to the back of the monitors this issue will make them very impractical. I can't ask users to start moving their screens every time they want to power on their computers, not least because something is likely to get broken!
Any suggestions or ideas would be greatly appreciated. I have already opened a case with Intel support, but thought it's worth asking here too.