H
Howard Davis
Guest
I recently upgraded my high end Dell laptop to Windows 10. After the upgrade everything seemed to be working fine, but then I found that periodically the wireless keyboard I am using will stop working (even though my physical laptop keyboard continues to work). I am using the Microsoft Sculpt Ergonomic Keyboard which is a wireless keyboard. This problem is happening multiple times per day.
After a lot of troubleshooting I finally discovered that when the wireless Microsoft keyboard stops working I need to go to the Settings -> Devices -> Connected Devices list and look under the Other Devices section for the entry for Microsoft Nano Transceiver v2.1. When I find this entry it will be showing a message that the device is not available. I then click to remove the device. Then I unplug the transceiver from the USB port, wait a few seconds, plug the transceiver back into the USB port and a new device will show up called "Microsoft Wireless Transceiver", in addition a second device called "Sculpt Ergonomic Keyboard" will also show up. Now my wireless keyboard will work again. This keeps happening over and over throughout the day.
As long as the "Connected devices" continues to show that the device "Microsoft Wireless Transceiver" is connected my wireless keyboard will work fine. At the point when the keyboard stops working (usually right in the middle of typing a sentence) I hear the notification sounds that are usually associated with unplugging a usb device and then plugging in a usb device, and at that moment my keyboard stops working. No physical USB port change actually occurred during this time and I have been unable to determine what is triggering Windows 10 to periodically and automatically switch the device and the driver it is using to communicate with the wireless keyboard. Each time when the keyboard stops working I go back to the Connected Devices list and sure enough the entry for "Microsoft Wireless Transceiver" has disappeared and it has been replaced with an entry for Microsoft Nano Transceiver v2.1 along with a message telling me the device is not available.
How can I get Windows 10 to stop periodically switching the Microsoft transceiver device to one that does not work? This has gotten to be extremely frustrating.
Continue reading...
After a lot of troubleshooting I finally discovered that when the wireless Microsoft keyboard stops working I need to go to the Settings -> Devices -> Connected Devices list and look under the Other Devices section for the entry for Microsoft Nano Transceiver v2.1. When I find this entry it will be showing a message that the device is not available. I then click to remove the device. Then I unplug the transceiver from the USB port, wait a few seconds, plug the transceiver back into the USB port and a new device will show up called "Microsoft Wireless Transceiver", in addition a second device called "Sculpt Ergonomic Keyboard" will also show up. Now my wireless keyboard will work again. This keeps happening over and over throughout the day.
As long as the "Connected devices" continues to show that the device "Microsoft Wireless Transceiver" is connected my wireless keyboard will work fine. At the point when the keyboard stops working (usually right in the middle of typing a sentence) I hear the notification sounds that are usually associated with unplugging a usb device and then plugging in a usb device, and at that moment my keyboard stops working. No physical USB port change actually occurred during this time and I have been unable to determine what is triggering Windows 10 to periodically and automatically switch the device and the driver it is using to communicate with the wireless keyboard. Each time when the keyboard stops working I go back to the Connected Devices list and sure enough the entry for "Microsoft Wireless Transceiver" has disappeared and it has been replaced with an entry for Microsoft Nano Transceiver v2.1 along with a message telling me the device is not available.
How can I get Windows 10 to stop periodically switching the Microsoft transceiver device to one that does not work? This has gotten to be extremely frustrating.
Continue reading...