I've to agree that there is still problem with the SD adapter after update the Bios to ver 0052. Putting the NUC into SLEEP and awaking it again causes in one scenario the SD adapter code to be corrupted.

Scenario 1 – SD card inserted into the SD adapter slot.

In this case after NUC is awaken, the SD card is detected and the CPU power consumption is correct. Working OK.

Scenario 2- There is no SD card in the slot.

In this case after NUC is awaken and the SD card is inserted into SD card slot, the SD card can't be detected. Restarting the NUC doesn't help. The system works again correctly only after the SD host adapter (Mobile 6th/7th Generation Intel Processor Family I/O SCC: SD Card-9D2D) is uninstalled and new one is installed by the OS (from Device Manager). Because reinstalling the SD host adapter fix the failure, I assume that while NUC enters the SLEEP state and there is no SD card in the slot, SD host adapter S/w is corrupted.

Thank you, lw1948! that's my problem. I have installed the latest version of Bios and slot is not working properly. Intel needed to solve this problem! My wife is very angry, it is often necessary to use the SD card slot.

Since we can see that some other peers have this issue fixed in their systems, let's find out why it is not working for you.

Would like to check some scenarios to narrow down the issue, and then proceed accordingly.

Here the questions:

-Are you inserting the SD card after the NUC wakes from sleep?-Do you have the SDcard connected to the NUC while it is in sleep mode?-Do you have the exact same model? (Intel® NUC Kit NUC6i5SYH)-Are having this issue after following certain steps? Please let us know.

Looks that you are not reading carefully this thread. The problem is not fixed at all, is even worst, because after updating to Bios 0052 the SD card is not detected. At first, before I've have switched the computer to OFF, it was OK, but after switching to OFF, system fails to detect the SD card. Please read my post above from Sep 25, 2016 11:09 PM to cvare. Also please see this thread: NUC6i3SYH sd card slot is not working .

Finally please pas this problem to your engineers to fix it ASAP. And this time will take it last time and will be also checked before releasing to the customers.

After the bios update to 0052 I have done many investigations and the problem is still there(see also my threads and the threads from user lw1948.)

Now I found this:

When I start my PC with a card in the adapter there is NO PROBLEM. I can work normally and when I docard out, card in, sleep on, sleep off, the PC works without problems and with a normal CPU use.

When I start the PC without a card in the adapter the problem appears. I have to insert a card and do a restart.Before the pc restart I recieve the message " Close Program Manager" and then the restart.

It seems that the PC will not or cannot load a driver if there is no card in the adapter.

Now I want to know how I can change my startup (msconfig ?) so that the driver (Mobile 6th/7th Generation ?) or a service alwaysstarts.

Every time there is a change in the situation I will pass my investigation and information.

i have NUC6I5SYH, running on Windows 10 1511 (Build 10586.589), Bios 0052 and latest Intel Driver. I have also problem with SD Card adapter. My NUC generally can't detect the Kingston SDXC Card - SDA3-128GB and show empty drive. With USB Card Reader detect NUC the SDA3-128GB without any problem and i can use it. On my mac book pro can i use the SDA3-128GB also without problem.

Hi all. This is a known issue with Window 10 Anniversary update (RS1 Version 1607). We are working with Microsoft on a fix, but temporarily there is a solution.

If you disable Fast Startup; Control Panel->Power Management->Choose what the power buttons do->change settings that are currently unavailable->de-select Turn on fast startup (recommended). See picture. You MUST reboot after you change this setting. Please let me know if that works.

This is only partial solution (working after Power ON and still not working after awaking from Sleep). This solution has also big disadvantage for me: the boot time is prolonged by about 9 seconds. In the mean time I'II prefer to use Loeschzwerg workaround with the .bat file.