X131e Pointing Device problems

[Winfried]

Hello!

My machine: ThinkPad X131e
Machine type model: 3374
OS: Windows 10 pro (including all updates)

Since some recent Windows update (I presume) the Synaptics Pointing Device does not work anymore. According to device manager it is installed ("connected to PS/2 mouse connector"), has the latest UltraNav device drivers (ver. 19.0.17.85), installation has been confirmed, but in device manager properties it claims "This device is not present, is not working properly, or does not have all its drivers installed (Code 24)". When I open "Mouse" in systems control panel it says: "No connection to Synaptics Pointing Device possible" (translated from German) and suggests to de- and re-install the device drivers.

What I did to change this:

- De- and re-installed device drivers including removal of all Synaptics entries in registry (several times).
- Installed a new keyboard (de-installed it after it brought no result).
- Installed older device drivers.
- Ran Lenovo System Update after de-installing the pointing device.

In BIOS there is no entry where to switch on or off the pointing device, as I found it suggested in other forums. A USB-mouse works properly, but I would like to use the trackpoint again as well.

Has anyone an idea where this error could come from, and what to do to resolve it? Thanks a lot in advance!

Winfried

[RealBlackStuff]

Yup, ditch W10 and go back to W7.

[Puppy]

Have you tried the is one ?

Synaptics Pointing Device Driver for Windows 10 (32-bit , 64-bit) - ThinkPad X131e, X140e, ThinkPad Edge E130, E135, E145, ThinkPad T430u
http://support.lenovo.com/cz/cs/product ... s/DS104313

[Winfried]

To RealBlackStuff: I considered this, but otherwise I am content with Windows 10, and the trackpoint did work with Windows 10 at first. - I just did a Windows 10 reset, with no success, though, as far as the trackpoint is concerned.

To Puppy: Yes, I did try the newest driver 19.0.12.61, but the result was the same. It reported the drivers were installed successfully, but in device manager it stills shows the same error code.