ID manager / UareU finger print reader - Windows 10

[timbo343]

Our finance team uses ID manager and the UareU fingerprint reader which is causing a bit of a concern. We have never been able to get this to work on Windows 10 until we looked into the issue this year. What i mean by this is i have to add the domain user to the local administrators group for ID manager to detect the UareU finger print reader otherwise ID manager shows No Scanner Found.

 

This work around was found out when we tried domain admin with ID manager and local administrator. Creating a standard local user to test with ID manager and the UareU fingerprint reader also gave the No Scanner Found error. When we moved this standard local user to the local administrators group, did ID Manager show Waiting For Finger.

 

I have tried giving the domain user full access to the following files:

c:\windows\syswow64\

- dpd00701.dll

- dpdevctl.dll

- dpdevdat.dll

- dpl00701.dll

 

C:\windows\system32\

- dpd00701x64.dll

- dpdevctlx64.dll

- dpdevdatx64.dll

- dpl00701x646.dll

 

C:\windows\system32\drivers

- dpk00701.sys

- usbdpfp.sys

 

We've tried

- adding the user to power users - this doesnt work.

- allowing FULL ACCESS to the BioStore folder in Program Files - this doesn't work.

 

I was wondering if anyone else has found a fix to this or if there is something we are missing.

 

Thanks

[Ditto]

I had trouble with a UareU reader (I think 4800 from memory) on Win10 a few months back where it was OK on Win7 PC. This might have been a different problem to yours, but on one machine I got it to work by completing a driver update, but let it search the web - it did take a good few minutes to complete. I think on another W10 machine, even that didn't work. The symptom often was that the Blue light in the reader wouldn't come on and 'No scanner found' error is reported, yet device manager said everything was fine. I got to the point of researching this and there was a suggestion Windows 10 settings to do with Fingerprint authentication might be part of the the issue, so it might be worth researching that. Whether trying compatibility mode would help I'm not sure, but also have a look at https://answers.microsoft.com/en-us/windows/forum/all/solved-why-cant-i-use-my-biometric-fingerprint/ba07945d-68fa-484c-96d2-5bd20d3dfeaa.

[timbo343]

Cheers, the blue light does come on and the finger print reader works with Domain Admin, just not general users.

 

Things used to work fine on windows 7 but as we have been on windows 10 for the last 3 or 4 years the fingerprint device hasn't worked so we used to use a laptop for this. What is interesting is that the MLS system works fine - not sure if the FS is a different kind as it's slightly bigger than the UareU 4500 ones.

[DrBeaker]

I'm sure I got one of these off eBay earlier this year, tried it but couldn't get it to work properly.

[MatthewL]

There is an issue with programming the RFIdeas card readers on certain versions of Windows 10, wondered if its linked, money on it been a Windows 10 issue.

[ass17]

We’re on 1709 edu and no reports of issues as yet... but there is time [emoji1]

[Ditto]

Cheers, the blue light does come on and the finger print reader works with Domain Admin, just not general users.

Things used to work fine on windows 7 but as we have been on windows 10 for the last 3 or 4 years the fingerprint device hasn't worked so we used to use a laptop for this. What is interesting is that the MLS system works fine - not sure if the FS is a different kind as it's slightly bigger than the UareU 4500 ones.

 

I'll be honest, I don't really have much of an idea, but to me it looks like a permissions/policy issue. With my setup, I had admin access so not comparable. My instinct from reading around this is that 'Windows Hello' (and/or Windows Biometric Framework) is some how interfering with the software functionality. A coupe of articles I saw (apologies if you've seen these before) where others have similar issues, albeit generally for using FS for logging in to Windows.

https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/solved-why-cant-i-use-my-biometric-fingerprint/ba07945d-68fa-484c-96d2-5bd20d3dfeaa - see comments from Prasath Sivanesan part way down. Also, it would be interesting to see the policy for admin versus domain user - see

https://www.tenforums.com/tutorials/107406-enable-disable-domain-users-sign-windows-10-using-biometrics.html

https://community.spiceworks.com/topic/1840001-windows-10-fingerprint-some-settings-are-managed-by-your-organization

 

Unfortunately, I can't run any tests as the school I was at didn't renew the contract, but the problem-solver in me would love to see this understood and resolved! What support call options do you have?

[Ditto]

We’re on 1709 edu and no reports of issues as yet... but there is time [emoji1]

Are you using a DigitialPersona type device or RFIdeas? What software are you using. Is it working for a standard domain windows user?

[timbo343]

I'll be honest, I don't really have much of an idea, but to me it looks like a permissions/policy issue. With my setup, I had admin access so not comparable. My instinct from reading around this is that 'Windows Hello' (and/or Windows Biometric Framework) is some how interfering with the software functionality. A coupe of articles I saw (apologies if you've seen these before) where others have similar issues, albeit generally for using FS for logging in to Windows.

https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/solved-why-cant-i-use-my-biometric-fingerprint/ba07945d-68fa-484c-96d2-5bd20d3dfeaa - see comments from Prasath Sivanesan part way down. Also, it would be interesting to see the policy for admin versus domain user - see

https://www.tenforums.com/tutorials/107406-enable-disable-domain-users-sign-windows-10-using-biometrics.html

https://community.spiceworks.com/topic/1840001-windows-10-fingerprint-some-settings-are-managed-by-your-organization

 

Unfortunately, I can't run any tests as the school I was at didn't renew the contract, but the problem-solver in me would love to see this understood and resolved! What support call options do you have?

 

I spoke to Cunninghams as that is who did our install for ID manager and they really didn't know. I think i briefly spoke to BioStore about it but they weren't much help either hence it's been an on going issue for so long.

 

I would be interested to know how to get it working with a standard user though as having the user with local admin rights just isn't right.

[ass17]

I made a mistake in my first response, I didn’t realise the PC was still in Win7, but have since installed Win10 and it doesn’t work. So I’ve sent a support request to Cunninghams and they are sending me new driver for our 4500 scanner tomorrow. If all goes well I can post the driver link..

[timbo343]

Cheers, would be interesting to see what the driver version is.

[DrBeaker]

Yes thanks, would be good.

[admars]

make sure you uninstall all the bio software first, at least that's my experience from being on a session when biostore dialed in. they were were helpful, bloke connected to pc we had problem on,

 

windows saw bio reader in device manager, but id manager wouldn't.

he gave me a new version of driver for win 10 64bit, and we had to unplug physical device, removed existing software and drivers, reboot, install driver he gave me, plug in software when it said so, then it worked.

 

I have found that you then need to "run as administrator", or change teh shortcut to run as admin in compatability etc

Edited September 4, 2019 by admars

[admars]

I use a digitalPersona One Touch file called setup64.msi 16/1/2012 16:17 11,240kb

[ass17]

Cunninghams have sorted out the issue. If you need help I can provide via PM the email of the person who was competent enough to sort out the issue.

 

Or you could raise a support ticket via their website and they will get back to you, just like I did.

Edited September 5, 2019 by ass17

[ass17]

Also now works as admin and non-admin user

[keyboards]

Oh this is interesting, we've got one of these or similar, one of our team tried getting it to work but to no avail, going to keep an eye on this, almost one of them things you could spend hours trying to get work and end up with it not Edited September 5, 2019 by keyboards

[DrBeaker]

Did they provide you with the updated driver?

[keyboards]

I haven't seen any updated drivers or any of our team mention one, if anyone has a link to one, I'm happy to try it and see what it does.

[Ditto]

Also now works as admin and non-admin user

As non-admin, did that work without "runas" or other elevated credentials, i.e. is the OPs issue resolved just by getting the appropriate drivers?

[ass17]

As non-admin, did that work without "runas" or other elevated credentials, i.e. is the OPs issue resolved just by getting the appropriate drivers?

 

Yes, works without elevated privileges.