Surface Pen or Multi-touch not working after Fall Creators update is installed on Surface Pro 4 or Surface Book

Anonymous
2017-10-20T17:33:35+00:00

After installing the new fall creator update, my surface pro 4 pen no longer writes, erases or interacts with the screen at all. All the buttons function normally. I used the Microsoft diagnostic trouble tree which had me replace batteries re-install the device, which did nothing. Is anyone else having this issue after the Fall Creator update installed, and if so do you have a solution? Thanks.

Surface | Accessories | Surface Pen

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
Answer accepted by question author
Anonymous
2017-12-08T02:31:30+00:00

Hi everyone,

Today, we released an update to the Intel® Precise Touch driver (Intel Corporation – HIDClass – 1.2.0.99). This driver resolves an issue where after Surface Pro 4 or Surface Book wakes from sleep, the touch driver will no longer respond to multi-touch input (like pinch to zoom) or the pen does not write.

We recommend that you install the latest updates to keep your Surface performing its best. You can get updates now by checking Settings > Update & Security > Windows Update.

You can find the details of the latest update on our Surface update history page.

Greg

Was this answer helpful?

20+ people found this answer helpful.
0 comments

260 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2017-11-22T01:13:19+00:00

    One other guy on reddit has got the updates that I got last night and he too says the touch problem is solved. He's not on the insider build as well so I'm guessing these updates will roll out to all soon and fix the problem. Just hang on tight

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-11-21T17:25:01+00:00

    Unfortunately for me, resetting the Intel Precision Drivers don't fix the issue, only a reset fixes it. I turned hibernation off, seemed like it worked for a day but eventually got the issue coming back. I'm desperately waiting on a firmware update that fixes it.

    Was this answer helpful?

    0 comments
  3. Barb Bowman 80,805 Reputation points MVP Volunteer Moderator
    2017-11-21T17:24:30+00:00

    Charles, your issue is different. the one being discussed here is a direct

    result of something that was triggered in 16299.*

    >Im on build 15063.674 (pre-FCU) and my HIDClass Driver is 1.2.0.83 (2017-01-26). Im still having issues.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-11-21T17:20:47+00:00

    I'll definitely post an update here a as soon as I can confirm it. But my advice would be not to move to the insider build as it is too buggy. Unless you are ok with the risk. In the mean time I have a powershell script that I could share if you want that disables and enables the driver everytime it stops working. It isn't the best fix but its way faster than opening device manger everytime

    Was this answer helpful?

    0 comments