Thanks. I just installed so I don't know yet. I'll be back.
Surface Book 2 Trackpad and Keyboard Lag
Hi. I have a brand new, i7 256 Surface Book 2 with an annoying problem. The trackpad and keyboard both exhibit huge lag when running on battery power, with anything less than "Better Performance". Even then, it's not perfect unless you go for the 'Best Performance' setting.
When running in battery mode, it's easy to appreciate that more people might be using the trackpad rather than a mouse (for portability) so why this won't function properly on the lower power saving modes, is confusing to say the least. One would expect the keyboard to work cum-what-may.
I've never experienced this issue with my Surface Pros and feel rather disappointed given the cost or the Book 2.
Any fixes please, other than disabling the two-finger pinch to zoom function?
*** I no longer seem to be experiencing this issue ***
Surface | Surface Book | Power and battery
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.
89 answers
Sort by: Most helpful
-
Anonymous
2018-08-04T02:21:05+00:00 -
Anonymous
2018-08-03T21:50:10+00:00 I tried the insider program a while back, that did solve the lag problem mostly for me but caused many other issues since it is beta. I did get that batch up surface and intel updates yesterday as well. That actually did seem to solve many of my problems. I can now run Hyper-V while on battery in any power setting and the lag appears to be gone. I do still see lag when task manager is running though, so it's not totally solved but much better. A new problem I had after the update was a hard lock-up every time I would wake the surface book while on my surface dock. I found this to be related to using a 4k monitor over display port. I have since replaced that mini display port to display port cable with the official microsoft mini display port to hdmi 2.0 and all is well there now too. Of course it hasn't been a full day yet, but I'm hopeful that I'm potentially seeing an end to this issue.
-
Anonymous
2018-08-03T19:35:01+00:00 Something interesting. As I mentioned earlier, I am in the "Windows Insider Program" slow mode. I think anyone can join and slow mode seems to be pretty safe but of course it is still beta software so keep that in mind. The latest build they make available here seems to really help this "lag" problem but something interesting happened yesterday and I'm not sure if all Surface Book 2 owners saw this.
Windows Update downloaded almost 2 dozen driver updates for everything imaginable on this machine. It also installed a firmware update yesterday and another one today. Every possible Intel Driver and the NVidia driver were all updated. Somethings going on for sure. Anyone else experience this?
-
Anonymous
2018-07-27T12:09:29+00:00 I have Hyper-V installed, so will try removing it to see if I can reproduce your improvements.
Oddly, on Monday night I had a Surface Firmware update and that next day I didn't have a single issue. I thought Microsoft had nailed it. That continued until Tuesdays Windows 10 update was installed, and I saw the issues again pretty quickly.
These last few days I have been monitoring the CPU clock speed and temperatures to see if this could be related to thermal throttling at all. I have seen that when the issue happens and the trackpad gets very laggy, the CPU is running at a very slow speed (< 1GHz), and the lag stops after it ramps up. This would explain why turning the performance up to Best Performance alleviates the problem as it would reduce the amount of throttling.
-
Anonymous
2018-07-26T23:00:01+00:00 I have been back and forth trying to figure out a solution to this without jumping to beta windows builds since my company is starting to buy more surface book 2's. The one thing that I have found is that when I install and enable Hyper-V the problem really exposes itself and then uninstalling Hyper-V seems to make it mostly go away.
Is anyone experiencing this problem without Hyper-V installed?