Quantcast
Channel: Intel Communities : Discussion List - Intel® NUC
Viewing all articles
Browse latest Browse all 18668

Bluetooth keyboard and mouse suddenly stopped working / NUC5i7RYH / Windows 10

$
0
0

I'm having a Intel NUC NUC5i7RYH running Microsoft Windows 10 Pro x64 RTM. My NUC has the Intel Dual Band Wireless-AC 7265. I just bought Microsoft Designer keyboard and mouse with Bluetooth and I've had problems, big problems, connecting them because they don't show up in the list of available Bluetooth devices. First I thought the problem were related to Windows 10, BIOS or the drivers and I even reinstalled Windows but the same problem occured.

 

  • BIOS version RYBDWi35.86A.0348.2015.0703.1124, 2015-07-03 (newest). I had 0249 before and the same problem with that version.
  • Intel Bluetooth driver for Windows 10 x64, version 17.1.1504.05G (newest). But in the Device manager-->Bluetooth I only have Intel(R) Wireless Bluetooth(R) which I found odd. I then checked on my Dell XPS 13 with Intel 6235 and as expected there were more devices under Bluetooth.

 

In another thread I read about removing the power cord from the NUC to resolve the problem and even if it worked for a few I couldn't imagine it would do the trick. So I turned off my NUC, removed the power cord, put the power cord back in and started the computer. Now there were more devices in Device manager-->Bluetooth and the computer could "see" my Microsoft Designer keyboard and mouse and also my Harman Kardon SoundSticks III Wireless and I also could pair all of them.

 

Now I thought everything was OK but after about 5 minutes the keyboard och mouse suddenly stopped working. If I check connected Bluetooth devices they seem to be paired. I then unpaired them and set the devices in "pair mode" but Windows/NUC cannot detect the keyboard and mouse.

 

So, Intel, how do you want to proceed with this?


Viewing all articles
Browse latest Browse all 18668

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>