08-22-2018 09:48 PM
There is another thread with the same issue... Yet Lenovo doesn't seem to care.
09-15-2018 07:37 PM
I'm using a 6th gen X1 Carbon.
I've been experiencing some touchpad delays and not registering my soft tap.
Thought it was some conflicts between the touchpad and my wireless mouse...
Anyway, it's quite frustrating.
Imagine you having to reset your laptop everytime to get it fixed, especially when you are in a hurry.
09-15-2018 11:58 PM
Exactly... it is super annoing....and after all this is business laptop!
When im presenting something at clients site I dont have time for restarting computer!
And on both sides od laptop paint goes down after 3 months of using.
Next week I will try to replace this laptop. It should not happen in laptop worth 4k $ !!!!!!!
09-19-2018 02:46 AM - edited 09-19-2018 03:10 AM
I replaced the motherboard with a warranty. The problem still exists.
Updating the driver does not solve the problem. Updating the Windows also did not solve the problem.
Lenovo - work on the elimination of errors in the drivers for the Carbon 6 generation.
09-21-2018 10:28 PM
Just want to add I'm having the same issue.
I'll give Lenovo credit, it seems that the drifting mouse issue has been fixed, but now I notice this delay/lag when I begin moving my finger on the touchpad.
I am fully up to date from Lenovo Vantage and Windows.
I'll test and see if it does it all the time or only after hibernate as some others here have mentioned.
10-02-2018 01:33 AM
The problem manifests itself immediately after a reboot or exit from sleep mode. Apparently, the drivers are written disgustingly: they cannot communicate with Windows, which replaces them with their own during the initial work of the computer, after which it switches the drivers to branded.
05-13-2019 10:49 AM
I found a workaround -- open Services, restart SynTPEnhService.
I've chatted with Lenovo support, and unfortunately they have no clue regarding this issue.
It's a lot of work to trace the root cause, so an official fix, if even possible, can't be expected anytime soon.
Getting the strong feeling it's a Synaptics driver/service/firmware issue, but it's tough to eliminate other possibilities.