Error using WinHello with database saved in Google Drive locally synced folder

[JohnLGalt]

Describe the bug
This just started happening today. I have been using WinHello with KeePass on a Windows 10 machine to use my WinX Hello PIN to log into my database, which has an extremely long and complicated Master PW only. I just updated KeePass (portable) from 2.43 to 2.44 and WinHello is breaking on that same database. If I export the database to another folder (not synchronized to Google Drive) WinHello works with KeePass 2.44 and that database with no issues. If I revert to KP 2.43, it works perfectly fine with the database in my Google Drive synced folder.

To Reproduce
Steps to reproduce the behavior:

1. Open KP 2.44 (portable), open database in Google Drive folder
2. Enter WinX Hello PIN
3. See error (screenshot below)

Expected behavior
Obviously, I expect it to open my database as it always has.

Screenshot of error

Additional context
I had a brainstorm to see if it would work from another folder, and v 2.44 + WinHello works as expected from another folder and an exported database, as well as a "save as" database to another location. I also noticed that reverting to KP 2.43 works with the original database that is saved in my Google Drive locally synced folder.

List of all plugins in KP:

Windows 10 Version 1909 (OS Build 18363.592)

[JohnLGalt]

I've since reverted to 2.43 (portable) to keep WinHello working as it should. I'm not sure where exactly the idiosyncrasy lies, as it could be:

1. A Google Drive issue
2. A KP 2.44 specific version issue
3. An incompatibility b/w current WinHello and KP 2.44 only
4. Something stupid on my system itself
5. Something completely off the wall

I'm currently setting up a laptop on which I will test with both portable and installed version of KP 2.44 along with the same Google Drive locally synced file and see if the error manifests there as well or not.

[Angelelz]

I would say, before doing anything, head to options and delete WinHelloUnlock data for that particular database and create it again. Let me know if that helps.

[JohnLGalt]

Oh, Roger, didn't realize that option was there. I will try it and see what happens.

…

On Tue, Feb 11, 2020, 09:38 Angelelz ***@***.***> wrote: I would say, before doing anything, head to options and delete WinHelloUnlock data for that particular database and create it again. Let me know if that helps. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#42?email_source=notifications&email_token=ABYWSQFP54V3226RM7Z44OLRCKZ5NA5CNFSM4KSURRL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELMUXZQ#issuecomment-584666086>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABYWSQGA5GTBT7CAJU4MFJ3RCKZ5NANCNFSM4KSURRLQ> .

[JohnLGalt]

Question: Could it have to do with the fact that I'm sharing the database through GDrive, and using on 2 physically different machines that both use the same Microsoft account to login (and thus using WinHello on both machines)?

Both machines are WinX current 1909 builds, one a laptop and one a desktop....

[Angelelz]

It shouldn't! I actually share all my databases with gdrive and use WinHelloUnlock in two machines. WinHelloUnlock data is saved locally, and is different depending on the machine.

Let me know if deleting the data and saving it again helps

[JohnLGalt]

That seems to have fixed it this go around. I have no idea why it was even doing it in the first place.

Odd.

Closing this as fixed.

[JohnLGalt]

Adding further comment - When I encountered the issue again (with the latest version) I was able to successfully delete the saved data and re-employ the hook and it is working perfectly again across both machines.

So, yes, deleting the saved data and saving it again works exactly as it should.