Windows 10: Logitech K780 Multi-Device Wireless Keyboard and Surface Pro 3 - Num Lock issue

Hi,


I connected a new Logitech wireless keyboard to my Surface Pro 3 and have the following issue: When I activate NumLock, numbers don't type. In fact the only keys that respond are '5' and '+'. When used, they act like a mouse right-click. I have connected to my computer using both USB and Bluetooth - the results are the same.

When NumLock is deactivated - keys respond as they are supposed to.


My first port of call was Logitech Support. They sent me to a troubleshooting page. It wasn't very helpful. In their opinion, my next step is to return the keyboard and get a new one. I want to try more options before I do that. I jave a feeling that this might be a compatibility issue more than a keyboard issue.


I have tried updates and keyboard troubleshooting. I am hoping that someone in this community has managed to resolve this or similar issue before.


Thank you for your time. Both reading and responding.


*I will be upgrading my Surface at some point, maybe this year, maybe not - she still works well enough for me at this time.

:)

 

Num Lock on Keyboard

I am using a wireless Logitech K800 keyboard. Every time the computer in started or rebooted, the num lock is disingaged. According to Logitech, this is controlled and caused by Windows. Is there any way to fix this?

Thanks.

 

Logitech Keyboard Num Lock problem

Hi I appreciate everyone taking the time to help me

I have a Logitech MK330 wireless keyboard + Mouse combo

When I type numbers with the number pad, it types numbers, but when I press the num lock and then attempt to use the arrow keys on the number pad, nothing happens.

This is strange to me as the arrow keys on my previous keyboard would do what an arrow key would when the num lock was pressed.

I'm not sure if a new windows update changed this but I only noticed the problem recently.

Thank you

 

MS Surface Keyboard Cover not recognized by MS Surface Pro 3

My Surface Pro 3 cover mysteriously stopped working (other USB keyboards work).

I’ve exhausted all of the steps from the Internet and am hoping for some advice here on what to try next.

• Clean the metal pins on both the keyboard and the Surface Pro 3 with alcohol swap and q-tip.
  
• Performed the standard two button shutdown procedure - https://support.microsoft.com/en-us/help/4036280/surface-force-a-shut-down-and-restart-your-surface
  
• Update "HID keyboard" device in Device Manager.
  
• Uninstall and reinstall "HID keyboard device" in Device Manager.
  
• Removed HID keyboard device in Device Driver and manually installed Surface Type Cover device (which later automatically turns to "HID keyboard device" when you hit "update drivers")
  
• Updated all Windows 10 patches to date.
  
• Tried a brand new keyboard (Microsoft FMM-00001 Type Cover for Surface Pro https://www.amazon.com/gp/product/B073W4MPJF/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1 )
  
• Updated firmware for Surface Pro 3 (typed in “winver”, took that Windows version, then downloaded the specific patch required here - https://www.microsoft.com/en-us/download/details.aspx?id=38826)
  
• Reset Surface Pro 3 while keeping personal files
  
• Reset Surface Pro 3 and deleted all personal files
  
• Performed hardware tests on aka.ms/surfacerepair (nothing bad found; all looks ok)
  
• Drained the battery most of the way before connecting again - the two times it worked momentarily these last few days was when I connected my new type cover keyboard to the Surface Pro 3 after the battery had died down to below 50%; a simple reboot later, everything stopped working. This user seems to have the same problem with it working briefly when there is low battery - https://answers.microsoft.com/en-us...pe-cover/52f983c6-2e53-49fa-aac6-7c4cc5d25d9f )
  

A breakdown of the steps I've done to sometimes get it working

• Leave Surface Pro 3 on about 2 hours on battery only.
  
• Power on Surface Pro 3.
  
• Working Keyboard.
  
• Turn off Surface Pro 3 (or reboot)
  
• Keyboard not working anymore
  
• Another similar user here - https://answers.microsoft.com/en-us...er-issue/2d6ed60a-c892-4ed9-907f-846fd9496f5a
  

Can anyone recommend any other troubleshooting steps? One of these steps seemed to work ok for others having this same problem.