Last week, I got a FW 13 Pro with the X7 chip and Ubuntu installed. I deleted the Ubuntu partition and installed Windows. Everything had been working well and it was directly booting to Windows with no Grub2, along with the fingerprint reader working well, but then I tried to boot Batocera off a USB stick, and everything went haywire…
It started going to the grub command line every time unless I went into the EFI settings and forced Windows, but then every time it also insisted on me entering the Bitlocker key and the fingerprint reader didn’t work.
With Claude’s help, changing my MS password, and more reboots than I counted, the last remnants of linux finally disappeared.
At the same time, I also decided to change my login (think going from john to johnd) and I have that set up now too.
The one thing that I’m having trouble with now is that I can’t register my second and third fingers to the reader. Before all of this started, I had 3 fingers registered. I managed to re-register one of them, but the other two throw the following error if I try.
I was able to register a different finger, but I’d rather be able to re-register my original set.
Anyone have hints or things to try? I’d deleted the Biobase file at least once, and removed the fingerprint recognition option on the Sign-in options.
Since you already deleted the database under C:\Windows\System32\WinBioDatabase, the likely leftover is on the sensor itself: the fingerprint reader in Framework laptops is a match-on-chip Goodix, so the old templates stay stored on the sensor even after the Windows database is gone. Dual-boot users here run into the same thing from the Linux side. One option is booting a Linux live USB and clearing the prints from the sensor with fprintd (fprintd-delete manages exactly that on-chip storage) - that is my hypothesis for a self-service fix, I could not test your exact setup. The safe route is asking Framework Support to clear the sensor storage for you.
Well, after talking to support, resetting my mainboard, mucking about with Claude to use usbipd to talk to wsl and having it create a couple of python scripts to list then clear the Goodix, I ended up deleting the WinBioDatabase again and it’s working.
Here are the actual commands that fixed the issue when run in an elevated command prompt:
net stop WbioSrvc
dir C:\Windows\System32\WinBioDatabase
del /q C:\Windows\System32\WinBioDatabase\*.DAT
dir C:\Windows\System32\WinBioDatabase
Some of this is on the hardware design side of fingerprint readers. They have notoriously vague or non existent documentation on how their hardware works or how to clear/reset it if issues arise. It is a wonder more people don’t have issues with these but only a handful of companies are even bothering making readers since it is a niche market.