Daedalus Flight - Known Issues

* Pairing Ledger device with Daedalus on a windows machine fails

When pairing a Ledger device with Daedalus on a Windows machine, after unlocking the device it is not recognized. The screen is still asking user to connect and unlock the wallet.

Workaround: Connect and unlock the Ledger device Before running Daedalus.

* If you are upgrading to Daedalus 4.3.1 from version 4.0.5 or older, verifying the blockchain can take from 30 to 90 minutes

Daedalus 4.1.0 and newer include a new version of cardano-node. Therefore, if you are upgrading Daedalus from version 4.0.5 or older, it can take from 30 to 90 minutes to verify the blockchain. This is due to DB migration on the first startup after the update. The migration can take from 30 up to 90 minutes (possibly longer) depending on your CPU. 

Learn more: Cardano Node 1.26.1 Release Notes

* Daedalus crashes when you connect a Yubikey to your Windows machine. 

Our team is working to fix the issue. Unfortunately there is no workaround. 

* [Trezor issue] When using Trezor T with a passphrase, user needs to confirm the passphrase several times

Due to an issue with the latest Trezor firmware, users need to confirm their passphrase several times when unlocking the device and accessing their wallet. This does not affect those who only use a pin code. Please note, the latest Trezor firmware is required for Catalyst Voting. If you use Trezor T with a passphrase and plan to register to vote in Daedalus/Yoroi/AdaLite, you will need to confirm the passphrase several times. The Trezor team is working to resolve the issue.

If your problem is not listed here...

For assistance, please submit a ticket to the IOHK support team from the Help menu in Daedalus, or by using the submit a request form.