I bought Numeric Keyboard N960 Gray (https://pl.aliexpress.com/item/4001022651141.html - the one without 2 extra USB 3 slots ). On my rarely ever used fallback laptop Lenovo G70-35 with Windows 10 x64 not updated since 2019 07 I can without a sweat detect it, pair it, reconnect it afer reset of system and also remove it from OS
But on my main desktop machine running Windows 10 Enterprise 20H2 19042.746 x64 the very same device was not detected at all- but that was probably because I had many things blocked with O&O ShutUp10 1.9.1434. So I reset this program back then to factory settings, reset the system, checked if I had Bluetooth turned on in settings and paired the device after entering on it a PIN generated by Windows - and as a result they supposedly connected. But in reality after this pairing the keyboard was not working. So I reset the system, removed it from system and paired it again- and still had no input from it. And after another reset of system I am now unable to remove; thus I am not unable to try to pair it again
I tried turning OFF and ON Bluetooth, using 15 year old Bluetooth transmitter [that barely works, but nevertheless does work, with modern wireless headphones], disabling every Bluetooth hardware in Devices and even uninstalling them, checking if every other hardware shown to me in
Control Panel > All Control Panel Items > Devices and Printers
I can account for [i.e. I know what it is] thus I know I do not have a doubled entry for [shown to me there] "N960 Numeric Keyboard" hiding under some generic name. I also tried removing from Registry entries containing "N960", but after third consecutive one which I was unable to delete I ditched this approach. And also I changed my Manual setting to
services.msc > Bluetooth Support Service > Startup type >Automatic
But still I am neither able to start to really use this keyboard or to get rid of it for good. [I will have to restore my system form an image]
What else I could try?
I do not use any other Bluetooth devices, except for headphones which utilize an external transmiter; while this keyboard does not have a dedicated transmiter and as I said at the very beginning it does work- but not with this machine with which I would like it to work with
But on my main desktop machine running Windows 10 Enterprise 20H2 19042.746 x64 the very same device was not detected at all- but that was probably because I had many things blocked with O&O ShutUp10 1.9.1434. So I reset this program back then to factory settings, reset the system, checked if I had Bluetooth turned on in settings and paired the device after entering on it a PIN generated by Windows - and as a result they supposedly connected. But in reality after this pairing the keyboard was not working. So I reset the system, removed it from system and paired it again- and still had no input from it. And after another reset of system I am now unable to remove; thus I am not unable to try to pair it again
I tried turning OFF and ON Bluetooth, using 15 year old Bluetooth transmitter [that barely works, but nevertheless does work, with modern wireless headphones], disabling every Bluetooth hardware in Devices and even uninstalling them, checking if every other hardware shown to me in
Control Panel > All Control Panel Items > Devices and Printers
I can account for [i.e. I know what it is] thus I know I do not have a doubled entry for [shown to me there] "N960 Numeric Keyboard" hiding under some generic name. I also tried removing from Registry entries containing "N960", but after third consecutive one which I was unable to delete I ditched this approach. And also I changed my Manual setting to
services.msc > Bluetooth Support Service > Startup type >Automatic
But still I am neither able to start to really use this keyboard or to get rid of it for good. [I will have to restore my system form an image]
What else I could try?
I do not use any other Bluetooth devices, except for headphones which utilize an external transmiter; while this keyboard does not have a dedicated transmiter and as I said at the very beginning it does work- but not with this machine with which I would like it to work with
Last edited: