This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I am using a Surface Pro 4 typepad cover on a Surface Pro 3. Ever since the Windows 10 anniversary update, the fingerprint reader does not work when I turn on the Surface, unless I detach and reattach the typepad cover. The keyboard and mouse work fine - the only problem is with the fingerprint reader.
I tried checking drivers, but the Windows says they are up to date.
The Surface family includes Surface Pro, Surface Laptop, and other Surface products. Surface is designed to help organizations, students, and consumers be more productive.
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.
I have the same problem with my Surface Pro 3 except the fingerprint scanner completely stopped working after the Anniversary Update. I can't even change fingerprint settings in settings.
Update: The solution posted by NevilleCarpenter solved my issue.
So the problem reappeared for me. Seems to have started after that latest major update.
My Windows is now on 1709 OS Build 16299.248 and it seems during this update the fingerprint driver got updated again to the latest version.
I had to go and download the 2016 driver and reinstall it manually and all back to working again.
So the problem reappeared for me. Seems to have started after that latest major update.
My Windows is now on 1709 OS Build 16299.248 and it seems during this update the fingerprint driver got updated again to the latest version.
I had to go and download the 2016 driver and reinstall it manually and all back to working again.
One of the reasons your problem would appear is most probably the new build has overwritten the drivers. You will have to revert back to the old drivers. That is why I keep it handy as with every new build comes new drives.
This is so stupid that SO MANY people have complained about the issue, and even discovered a fix, yet the driver team at Microsoft, does nothing to fix the issue.
How hard is it to compare the working driver and their new driver and determine what the issue is??