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. Barb Bowman 80,805 Reputation points MVP Volunteer Moderator
    2017-11-25T12:25:43+00:00

    others have found that going into device manager and disabling/enabling the

    "Intel(R) Precise Touch Device" in device manager made both the pen and the

    multi-touch work again. Less disruptive than restarting. And the problem will

    probably re-occur.

    Open device manager,  Click on human interface devices to expand it and it

    should be near the bottom of the list. This is a temporary fix and the issue

    will return until Microsoft issues a new driver

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2017-11-14T19:20:07+00:00

    Hi Barb,

    Your tip for disabling and re-enabling the driver works, albeit that it is clearly a temporary solution.  I have downloaded a thing called DevManView, an alternative to the standard Windows Device Manager, which also allows a command line input.  Saving it to my %Public%\Downloads folder I then wrote this small batch file to automate the process of disabling and then re-enabling the driver ...

    Echo off

    cd "%Public%\Downloads"

    if not exist DevManView.exe goto error

    echo Disabling the Intel(R) Precise Touch Device driver ...

    devmanview /disable "Intel(R) Precise Touch Device"

    echo Waiting ...

    ping 1.1.1.1 -n 1 -w 1000 > nul

    echo Enabling the Intel(R) Precise Touch Device driver ...

    devmanview /enable "Intel(R) Precise Touch Device"

    echo Done.

    goto end

    :error

    echo DevManView doesn't exist in the current directory.

    :end

    pause

    Works well enough for me when I need to get around this irritating problem.  Perhaps it will help others too.  Perhaps Microsoft will fix the issue and help us all.

    Angus

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2017-10-21T17:06:27+00:00

    i have the same problem also

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2017-10-21T07:10:54+00:00
    • Have you tried installing and updating the drivers and firmware specifically for Surface Pro 4? If not yet, it will be a good idea to do so: Surface Pro 4 Drivers and Firmware.

    I am running build 16299.19 which is the latest. If there are newer files among those listed, I cannot easily tell what they are. I also checked some drivers in Device Manager to ensure they matched the latest version on the SP4 Update History page.

    Instead of posting a link to a bunch of hard to identify files though it would be nice if you told me which ones I actually need! This would show me you actually thought about my issue and checked the link for me.

    • We recognize that you've made an emphasis on [NOT] providing generic troubleshooting. However, we need to clarify if you've tried the solution steps found in this support article: Troubleshoot Pro Pen.

    I'm glad you recognize it, but clearly you don't believe it! Of course I have tried these very basic steps. For your reference, I am an IT person. I do miss things and make mistakes, but God do I try.

    I have added a video showing the issue.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments