Fingerprint reader stopped working with Surface Pro 3 after anniversary update

Hi JudoChoke,

My Driver Details from the Device Manager are:

Driver Date: 2/3/2016

Driver Version: 2.2.10.8

Also, it looks like the latest Windows update did not update the keyboard driver as the option to "Roll Back Driver" is disabled.

So I'm guessing based on the date and the option being disabled that I am definitely on an older driver.

Going on 4 days and so far each time I've needed to log in it's worked perfectly.

Hi got the same issue with my SP3 Pro and the Type Cover with Fingerprint. 

I´m on the latest Windows 10 Build and automatic Update is active. But the Fingerprintreader don´t work after sleep. Only deattach and reattach the Type Cover working. But not everytime, sometimes I have to do this a few times. 

The Workarounds on this Thread don´t work for me. So I did not bought the Fingerprint Type Cover for don´t using it. And because the Bug is known very long, there should be a fix from Microsoft. Maybe there is a Hardware Bug?!

Regards, 

Marcel

Marcel,

Did you try to roll back the driver? Are you using the same driver version i am? 

I don't know if this was related but before i thought to roll back the driver, i did a full backup and a complete system reset.

Once all the updates were done it seemed to work for all of 10 minutes before it stopped working again. Then, out of curiosity, i did the driver roll back and it's been working ever since without having to do that disconnect and reconnect thing. Which i had to before as well before it stopped working altogether.

Hope that helps.

Hi, thanks for your answer.

Yes, I use the same Driver. Reinstalled Window 10 with an USB Stick, too. But nothing changed. Did this a few Months ago, because I thought it would help. 

Try the Driver Roll Back again.

Reporting later.

Thanks,

Marcel

I do not know what my previous biometric driver version was, but believe it was from August of 2017?  My current version that I rolled back to is 2.2.10.8 from 2/3/2016.  I've had zero issues since rolling back the driver. I've acceptable all other updates.

Interesting in that I've only had stable fps functionality the past several months whereas driver I rolled back to is well over a year.  Not sure if it was released well after driver date or if it is an interoperability issue with a different driver.

In any event it's surprising it's an issue.  Personally it is significant enough that I stop using SP3 when it misbehaves.  Especially when my Microsoft Designer Bluetooth mouse is also losing connection due to a driver error that randomly shows up (and driver is from 2006 I believe).  I use SP3 because it's very portable, but I end up reverting to my larger laptop because it's predictable and user input always works (sorry, had to squeeze in a rant)