Thank you for contacting the Intel community.
Please try the following:
- Open the Keyboard control panel item.
- Click the Hardware tab, and then click Properties.
- Click the Change Settings button.
- Click the Power Management tab and then verify that the “Allow this device to wake the computer” is enabled.
- Click OK, and then click OK again.
If that does not work, access the BIOS and once you are in the BIOS press F9 on your keyboard to set your BIOS to default settings and then press F10 to save all changes, see that works.
If the problem persists, try a BIOS update, you can download that latest version here:
Please see BIOS Update Instructions for Intel® NUC
Also, make sure you have the latest graphics driver installed, you can download it here:
Intel® Graphics Driver
I hope this can help.
Thanks for the suggestions. I already have the latest BIOS and Graphic Drivers and after reverting the BIOS to the defaults I can still reproduce the issue.
Want to reiterate that the keyboard will normally wake the NUC from sleep and that it only fails to after it is unplugged and plugged back in while the NUC is sleeping.
I know that the NUC is sleeping because the power light is blinking blue. I believe this has nothing to do with the Video driver ( if I force the PC to wake via pressing the power button, the video returns and the keyboard starts working).
Are you able to reproduce this behavior using a USB keyboard and setting the sleep time in Windows 10 to 1 minute?
Any other ideas?
I have tested this unit and we get the same behavior, also I did LAB with different computer and same issue, so it seems that the issue is not only with the NUC because I tested a dell computer and same problem, I tested another NUC and the same happen.
Do you get this behavior with other components beside the Intel® NUC?
In addition, I will appreciate if you can attach your system information to further investigate the issue, you can follow the steps how to get it below.
Intel SSU (System Support Utility): (Note - This is a new Intel tool that will eventually incorporate gathering all the data needed in one click. Targeting end of year to be fully featured. Until then, please provide the DxDiag and DispDiag as well)
Download Intel® System Support Utility
- Download the utility
- Run the exe and select 'Scan'
- Save and include as an attachment int he Intel Community Forum
- Click on the “Start Menu” -> Type “DxDiag” -> Press “Enter” -> Wait for the DirectX Diagnostic Tool to finish loading
- In the DirectX Diagnostic Tool, click “Save All Information” -> Save the file DxDiag.txt
- Include DxDiag.txt as an attachment in the Intel Community Forum
- Click on the “Start Menu” -> Type “cmd” -> Then a command shell window will open
- In the command shell, type “dispdiag -out %homepath%\Desktop\DispDiag-Intel-Issue.dat” -> The command shell will output something similar to “Dump File: C:\Users\[username]\DispDiag-########-######-#####-#####.dat”
- Locate the .dat file on your desktop and include DispDiag-Intel-Issue.dat in the Intel Community Forum
Thank you GroundedReality, I also try this on Linux and same happen, so is not an issue with Windows, at least that's what it seems to be. Have you seen this behavior in another system where your using Windows®7 or other Windows® version?
We really appreciate you have taken your time to report it.
On my windows 7 work PC, the PC never wakes from sleep via input from the keyboard, so it has bigger problems now than my NUC....
On another note, I did some additional research on KVM switches and according to this Wikipedia article, I will need to get a DDM type USB KVM. It is the only type of KVM that continually emulates the attached devices so that the attached computers always thinks that the USB devices are attached ( even when the KVM is connecting the USB devices to a different PC). Non DDM type USB KVMs will experience the same problem reported in this thread.
Thanks for your follow up. At this point, I will purchase a DDM KVM switch and feel confident that I will not experience the problem reported in this thread with my NUC.
My apologies if I you already mentioned this but how about testing the Keyboard directly connected to the NUC without unplugging and plugging it back? Does it wake up the system as expected?