Microsoft Precision Touchpad, not very precise

Anonymous
2015-03-02T22:40:42+00:00

I recently purchased a laptop from Microsoft (2015 Dell XPS 13") that uses the Microsoft Precision Touchpad. 

There are a few issues I'm having with this touchpad that I've never noticed with other laptops and I'm wondering if anyone else is experiencing these or if there are any fixes. 

  1. There is a noticeable delay when trying to make slow light movements. My finger can move several millimeters before the cursor responds. It may not sound like much, but if you're trying to make subtle movements in photoshop, or select a specific character anywhere it's very noticeable and difficult to use. 
  2. The majority of the time when I lift my finger the cursor will jump several pixels, often moving away from the object I'm trying to target. 
  3. If you use any browser besides IE, two finger scrolling is very choppy and has a similar delay that's experienced in the first issue. 

There are a few other minor annoyances, like poor palm detection and using two hands (one to move the cursor and one to click with) but the issues above are the biggest annoyances, ordered by most annoying to least. 

If anyone has any ways to fix these issues or install different drivers, I'd love to hear about them.

Thanks!

Windows for home | Previous Windows versions | Search, touch, and mouse

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

63 answers

Sort by: Most helpful
  1. Anonymous
    2016-06-18T21:15:26+00:00

    I cannot believe the level of apathy from MS reps in this post. This is a basic troubleshooting step: Confirm if the issue persists across multiple devices.

    It has been confirmed multiple times from various users in this thread alone, and I will add to the pile:

    I have an MSI CX61 2QC and I have this same issue. I used to have an HP Pavillion 9009US running windows XP and the issue was there. I had installed both the MS drivers and the Synaptic drivers. Anyone who has tried to Google the issue will know that it manifests in versions of Windows since (at the very least) XP, through 7 and 8, and up to the current version, and across many, many platforms, including Microsoft's own hardware (unless you somehow, ridiculously, attempt to claim that the Surface isn't a Microsoft product). 

    It is 100% a Microsoft issue, as it is something which has manifested across multiple models of computers and across differing versions of Windows. This is Troubleshooting 101. Stop passing the buck. 

    Seriously, you reps are the worst; arguing with customers, and basically giving the rep's version of f-off ("It's someone else's problem; call them.) to anyone asking for help, not even providing some basic troubleshooting or workarounds, even if they're partial fixes. You remind me of the guy from "A Week in the Life of a Lotus Notes Support Person from H**l".

    The least you could do is reply, "We understand your frustration. What I can do for you is send this issue up the line. It seems as though it may be relevant considering it is an issue that many people seem to be having, and our engineers should be made aware if they are not already." Even if you've already logged the issue 10 times today already. It's basic customer service. 

    Apple's tech support is way better. It's too bad they don't write Windows.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2017-09-09T20:42:37+00:00

    I recommend we all just ignore these useless Microsoft "MVPs."  They won't help you, and they like to think that because they know Microsoft's official line on how your problem is not actually Microsoft's problem (even though it is), that makes them a special and helpful "MVP."  Ross (from a page back) is an Engineer at Microsoft who is interested in how Microsoft's precision drivers are falling short, which is actually a big reason people still choose Apple over Microsoft.  I suggest reaching out to him, and talking amongst ourselves, as the discussion around the MVP's is actually helpful.  It takes awhile, but Microsoft is slowly improving their drivers.  MVP's need not reply.  You are not helpful.  Seriously, just keep it to yourself.  None of use are interested in being referred to the endless rabbit hole that is a manufacturer's customer service.  If you think talking to Dell, Samsung (or Microsoft, as in the surface, Microsoft is actually the manufacturer sometimes... Doh!) is helpful, don't waste your time posting here.  Please go talk to Dell (or Microsoft...) on our behalf if you want, but just stop polluting the discussion here.  It's not helpful.  We'll keep talking amongst ourselves and the Dell engineer who gives a hoot. 

    Thank you.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2015-10-24T18:22:47+00:00

    FALSE.

    The Microsoft Surface Pro 3 has this issue. The trackpad in the surface Pro 3 type cover - a precision touchpad - has this exact same issue. I was referring to the Microsoft Product, not the Dell product.

    There is no OEM in this case, only Microsoft. The operation of the Precision Touchpad - when controlled by Windows 10 (or 8.1) - using Microsoft drivers - on Microsoft hardware - does not work correctly.

    I am trying to work with the hardware (and software) manufacturer on this one. It is Microsoft.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2015-08-12T13:00:38+00:00

    The precision touchpad and the microsoft driver is the problem. You can track the problem over notebooks which use the precision touchpad and Win 8 or 10. Microsoft introduced something called Pointer Events (opposed to Mouse Events or Touch Events) which it uses in the Win 8 and 10 Apps, Internet Explorer and Edge. The Precision Touchpad driver scrolls incredibly well and smooth with these programs. Other software, like Google Chrome for instance do not support Pointer Events jet, so it "listens" for Mouse or Touch Events coming from the trackpad and this is where the Microsoft driver fails. While Synaptics programmed a driver which also allows good scrolling via the old methods, Microsoft does not care. One might also think Microsoft does this intentionally to either promote their browsers for smoother scrolling or to force other software makers to use Pointer Events...

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2015-05-14T00:45:12+00:00
    1. This problem is not in the hardware: when you use Ubuntu or Windows 7 on same machine, touchpad works just fine. That means the hardware is OK.
    2. This is not driver problem: touchpad scrolls flawlessly in Metro mode (Start screen). That means the data fed to OS by the driver is correct.

    So the only conclusion is that the OS is at fault.

    At the PTP thread on reddit, TS said that MS has introduced new API: Direct Manipulation (DManip). So when you do a two-finger scroll they inspect active window and try to discover DManip consumer there, and if this check fails they fallback to standard behavior and inject legacy mouse wheel(or vertical scroll) event which is recognized by any software nowadays.

    So this is most probable place containing problems. And since 99.99% of the desktop software doesn't support DManip, we're having horrible scrolling experience everywhere (except Metro).

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments