Windows 10: How do I turn off EdgeMotion on Surface Pro 8 magnetic keyboard touchpad?

I find the feature very annoying and would like to click and drag without the mouse continuing the motion.

:)

 

Synaptics PS2 Touchpad - EdgeMotion Problems


Hello all!

So - short and sweet. I have a Sager NP7358 laptop running Windows 10. Synaptics has a feature for touchpads called EdgeMotion. It keeps the cursor scrolling when your finger reaches the edge of the touchpad. It's annoying.

I have the latest Synaptics drivers and within the software I have EdgeMotion DISABLED under the one and two-finger scrolling, yet the cursor still scrolls!

Anyone run into this issue yet with Synaptics?

 

Surface Pro not recognizing keyboard

you can try the following suggestions:

1. Restart Surface
   

Restart (don't shut down) your Surface. Select the Start button, then select Power > Restart.

1. If you have a Type Cover, detach and reattach it
   

a. Unplug your Surface and detach the Cover.

b. Wet a cotton swab with rubbing alcohol. (Use 95% or stronger isopropyl alcohol if possible.) Rub the cotton swab back and forth over the six circular magnets on the Type Cover's connector. After you're done, make sure the pins are dry and that no cotton fibers remain on the connector. Then clean the connector on your Surface.

c. Reattach the Cover, making sure that all the magnets touch the bottom edge of your Surface.

1. Reinstall the Surface Cover driver
   If shutting down doesn't fix the problem, try reinstalling the driver for your Surface Cover.
   

a. Select the search box in the taskbar, enter device manager, and select Device Manager in the results.

b. Expand Keyboards.

c. Right-click Surface Type Cover Filter Device.

d. Select Uninstall > OK.

e. Restart your Surface. It'll automatically download and install the Surface Cover driver the next time you connect to the Internet.

 

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 - Force a shutdown 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.