[Nicolas Ramz]

I noticed since some time that from time to time (usually after resuming from hibernation), the Surface Pen of my Surface Book stops working.

I can use the shortcut button but it won't draw anything in any app. It's detected properly, and battery is at 80%.

The only way I found to make it work again is to restart the Surface Book. But of course this isn't a solution.

Anyone having the same problem?

I am running Fall Creators Update with the latest updates installed.

[Rafael Dowling Goodman]

I also started noticing this. I too have the Fall Update installed, although I can't be certain it's the cause.

I've noticed that another symptom is that screen multi-touch stops working (e.g. can't pinch to zoom).

It's as if the digitizer driver is crapping out.

[d1stort1on]

Yep I have it too, although it doesn't even need to sleep for it to happen. Not very pleased about this.

[paxiundfixi]

I have exactly the same issue. Reactivating it or restarting the driver does not help. Reboot is fixing it. Got the problem exactly since the Fall Creators Update. Anyone contacted Microsoft yet?
(Surface Book i5 with dGPU on Win 10 Pro V. 1709)

[Rafael Dowling Goodman]

When it occurs, disabling/enabling the "Intel(R) Precise Touch Device" (under Human Interface Devices in Device Manager) does get it to work again.

[Rafael Dowling Goodman]

Looks like there's been a Microsoft Answers thread started on the issue:

https://answers.microsoft.com/en-us/...sso-surfpen//1

[Matthew Kreh]

My wife had this problem with her Surfacebook.

The best fix is to update the firmware and drivers for your device. Here is the link that I used to fix our issue:

https://docs.microsoft.com/en-us/sur...urface-devices

If this works for you, please revisit the other places that you have asked about this issue and pass along what the solution was so that others afflicted with this pen issue can fix their systems as well.

[Mattemt294]

Pen has 2 batteries. You try replacing both the watch battery and the aaaa then repair?

[coyo38]

A Solution (for now) is what Rafael DG says : "disabling/enabling the "Intel(R) Precise Touch Device" (under Human Interface Devices in Device Manager) does get it to work again."

It's annoying but better than rebooting.