Mouse and Touchpad settings Windows 8.1 and Surface Pro 3

I have a Surface Pro 3 running Windows 8.1.   I noticed that I can no longer use the right or left clicks when using the touch pad on the Surface Pro 3 keyboard. 

When I go to PC Settings - PC and devices - Mouse and Touchpad I only see the section for the Mouse, touchpad does not display.

This is occurs with a domain user account.  If I log in as a domain admin (different account) the touchpad settings now appear.  Does anyone have any thoughts?

If I make the original user and admin or domain admin the results don't change, the touchpad settings still do not display.

March 4th, 2015 11:56am

Hi,

Since you mentioned the setting of touchpad appeared within the domain admin user account. The root cause is user account permission issue. I would like to suggest you contact domain administrator to see if he/she set some limitation for standard user.

Free Windows Admin Tool Kit Click here and download it now
March 4th, 2015 9:36pm

I am the administrator. I agree it appears to be permissions related. However I can make the user in question an administrator and that does not correct the issue.   Seems to may be something related to the user profile, not sure what to look for in that.
March 5th, 2015 7:02am

Hi,

It's hard to troubleshoot since I have no specific Surface pro to do a test.

Based on your description, when you add the promblematic user account to domain administrator group, the touchpad setting still not appear.

I suggest you recreate a new local user either admin or standard to check if it could get the correct setting.

Free Windows Admin Tool Kit Click here and download it now
March 6th, 2015 5:31am

I am experiencing exactly the same problem (TouchPad settings not appearing under PC Settings / PC and Devices / Mouse and Touchpad on Windows 8.1 for most users) . . . it's driving me nuts . . . did you ever find anything that got the TouchPad settings back for anyone other than a Domain Admin? My gut feeling is that there has to be something somewhere in group policy (or registry or . . .) that has fouled this up, but I've tried everything I can think of to no avail.

Thanks!

May 18th, 2015 5:46am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics