Describe the bug
I am using ledger nano S to sign in on windows 10 may 2019 update (version 1903 build 18362.175). After clicking sign in with ledger, Windows Security popup (the new native FIDO U2F from Microsoft i suppose) keep on popup up and automatically closing itself for a while.
After the popup flashing stops and I accepted login on ledger, I got stuck with an error screen in the windows security popup. Closing the window and retrying sign in yields either another error popup or getting stuck with Take action on your security key , while ledger is stuck in Returning Address...
To Reproduce
Returning Address.Expected behavior
Only 1 popup of Windows security asking me to press button should appear, I should be about to login after I press accept on ledger.
Screenshots
After the "Windows Security" popup flashing decided to stop
After pressing accept on ledger:

Result:
Desktop (please complete the following information):
There sadly is an issue with Ledger on the newer Windows version. I recommend using a secondary machine running Linux or OSX or an older Windows. Ledger told us, that a real fix will only be available later this year.
We are working on alternative signing mechanisms as I write here!
We're reviewing this issue with @jleni - it should be fixable with the current implementation before migrating to WebUSB later.
Linked to this PR
https://github.com/LedgerHQ/ledger-app-cosmos/pull/8
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Absolutely the same problem. I have tried lots of solutions without sucess.
Did you find a solution?
Absolutely the same problem. I have tried lots of solutions without sucess.
Did you find a solution?
It worked for me after a new cosmos app veriosn was released on ledger an year ago. Not sure if the latest cosmos app and windows would cause similar issue now though.
Most helpful comment
We're reviewing this issue with @jleni - it should be fixable with the current implementation before migrating to WebUSB later.