I bought a Framework Laptop 13 Intel 13th last year and it works fine wth the exception of the fingerpting. Unfortunately the camera doesn’t have IR which makes it not being supported for Windows Hello.
My experience with the fingerprint has been really bad, it does work but it always stops working completely after a while, to make it work I just need to reset the Windows Hello fingerprint setup and do the setup again, which is getting really old.
I have been back and forth with Framework support, even had a replacement of the fingerprint and the issues still remains. From the behaviour this looks like some issue with software/drivers.
Not sure where to look for logs or how to troubleshoot this further.
When your fingerprint isn’t recognized anymore, are all devices shown fine (without exclamation mark or so) in the device manager (devmgmt.msc)?
Because you need to set it up new, it could also be somehow related to the TPM. You might check the status of it when the problem occurs again (tpm.msc and devmgmt.msc)
The eventlog looks fine?
But I guess it would be hard to find something useful in this scenario.
@mahe yes, both tpm seems to be fine and in device manager there is nothing flagged as having issues, the fingerprint reader seems to be recognised fine.
The TPM also reports that is ready for use.
I have used the driver bundle to install all the drivers, I have also tried to reset things in the bios as instructed by Framework.
Framework also kindly sent a fingerprint replacemente which I replaced but exactly the same issue.
Based on this I truly believe there is some software issue. No sure wha to look for in event viewer tbh.
What I know is if I do the fingerprint setup again, everything works fine for a couple of days and then stops working and I have not idea where to go from here.
Haven’t tried to format and re-install, might try to do that.
Then it could also be a problem related to the account.
I don’t have much experience with private MS accounts, but I would check the security settings of the account on the website (should be somewhere here https://myaccount.microsoft.com/)
Precisely what I was kind of thinking. One possible solution is to make your user account a local user account (IE: disconnect your microsoft account), and see if the problem persists.
