Post new question
Question
Reply
 
Student
Posts: 1
Member Since: ‎04-21-2017
Message 1 of 2 (84 Views)

FIngerprint stopped working following Creator Update

Product Name: Envy 14 L8V12AV#ABA
Operating System: Microsoft Windows 10 (64-bit)

I recently updated Windows 10 Pro x64 on my Envy 14 to the new Creator Update from Microsoft and now Windows does not recognize the fingerprint reader. HP Simple Pass recognizes it when I manually open the app but will not recognize any fingerprint. I updated the driver manually through device manager to no avail and HP Update Assistant says there are no updates for my computer. Help please.

Reply
0
Regents Professor
Posts: 4,165
Member Since: ‎05-06-2013
Message 2 of 2 (45 Views)

Re: FIngerprint stopped working following Creator Update

[ Edited ]

Hello @kissmad82

 

Welcome to the HP Support forum. Thank you for posting.

 

This may be caused either by something in the driver or some Windows bug.

 

You may try completely uninstalling the driver, reinstalling it back and also reinstall HP Client Security Manager app.

 

 

 

Since you already updated the drivers and If Windows 10 Creators Upgrade (CU)  was installed recently, I recommend you this workaround. You have an easy option to restore back to previous Windows build - probably Anniversary Update build 1607. You can go to Settings > Update and Recovery and follow the steps to revert back to the build that worked fine for your PC. Here is how to do it >> https://www.howtogeek.com/235474/how-to-roll-back-builds-and-uninstall-updates-on-windows-10/

 

This option will work in case the update was installed recently and if the recovery partition/files created by Win 10 itself are working.

If it worked fine with AU, keep this build.

 

 

Some more tips - my personal opinion:

You are using Win 10 Pro - this is the professional edition of Windows 10 which gives you certain privilages and one of them is the option to Defer upgrades. This privillage is there to be used, not to be kept disabled Smiley Happy I think you know what I mean.

In Windows 10 there are several branches for updates. And here is how it goes:

Windows 10 alpha/beta testers (insiders) > 'stable' release Current Branch > Current Branche for Business / Enterprise > LTSB

 

 

Win 10 Creators Update is currently in the Current Branch updates for mass deployment and is not in the Current Branch for Business, therefore not recommended by MS for all the real Pro and business users, and there is a reason for this. It will go there after about 4 month. If you are real Win 10 Pro user, you should keep the current branch for business release cycle and not rush to install all updates. Note that your PC will still continue to receive security updates, just will delay feature upgrades such as CU. Current Branch for Business is slightly more stable and reliable.

 

Using gpedit.msc you can defer upgrades (feature upgrades such as CU) for 4 to 12 months

Using gpedit.msc you can defer security and other updates for 1 to 4 weeks

Here is how > http://www.computerworld.com/article/3005569/microsoft-windows/how-to-defer-upgrades-and-updates-in-...

 

Generally speaking, I recommend you defer upgrades to 12 months and defer standard updates for 2 weeks.

If you do want to install CU, you can defer the upgrade for 4 months and try again after 4 months where CU may be more stable and drivers may be updates.

 

More info:

>> http://www.windowscentral.com/how-delay-windows-10-creators-update-your-pc-and-why

>> https://betanews.com/2017/04/07/dont-rush-to-install-windows-10-creators-update/

>> https://technet.microsoft.com/en-us/itpro/windows/update/waas-overview

>> https://blogs.technet.microsoft.com/enterprisemobility/2016/01/06/navigating-the-windows-10-servicin...

 

============================

 

 

Hope this helps.

* You can click below on the Thumb Up+ button for (+1) kudo if you want to say thanks.
*
If my comment helped you, please, accept this post as a solution
 
 Smiley Wink
----------------   Best wishes,   IT_WinSec  ----------------
I do not work for HP Inc.  I express personal opinion only.
I work as consumer support technician, cyber security engineer, network support specialist
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation