While on Wasabi v1.1.4 and Windows 10, a user has connected an already initialized Trezor Model T to Wasabi. Here the watch-only wallet was successfully initialized. Then the user send funds to a receive address of this hardware wallet.
Now the hardware wallet is no longer recognized by Wasabi, even though it is USB connected with the valid PIN entered. When trying to sign a transaction, the error Could not find hardware wallet. Make sure it's plugged in and you're logged in with your PIN. shows up. After deleting the wallet file, and trying to setup the watch-only wallet again, in the Wallet Manager / Hardware Wallet tab, it does not recognize the trezor, and does not exchange the xpub. The same behavior on v1.1.4 and v.1.1.6.
Interestingly, the trezor.io website wallet does work, the hardware wallet is recognized here. So it seems to not be an issue with the USB cable, or hardware wallet, or drivers, but something specifically to Wasabi.
The user has the mnemnoic recovery words, so sats are safu, hopefully.
Windows 10 Pro - v19.03
Wasabi v1.1.4 & v1.1.6
Trezor Model T
The user can connect the same hardware wallet on Mac OS Mojave v10.14.2. It seems that everything works in this setup, a transactions has been successfully signed and broadcasted.
Windows 10
Trezor T Model Bootloader 2.0.3 - Firmware 2.1.0
Device unlocked!
Tested on MainNet
Upgraded to 2.1.1
Tested on MainNet
So it is working for me. Let's start debugging. Wasabi is using hwi as an interface to HWW. There is an enumeration command which is listing all the connected HWW to the computer.
After ~10 second I received this:
C:\Program Files\WasabiWallet\Hwi\Software\hwi-win64> .\hwi.exe enumerate
[{"type": "trezor", "path": "webusb:001:4", "fingerprint": "f89eabfa"}]
If HWI could not find the device we should debug HWI. If HWI enumerate the device we should debug Wasabi.
Confirmed. Trezor T with HWI doesn't work anymore on Windows 10.
Unfortunately on win10, Trezor is not recognized anymore. Neither with the newest HWI because the problem was caused by a windows update. The solution also came from windows:
Start Wasabi in Administrator mode and Trezor will work like before.
Looks like some permissions which were used by HWI got under Administrator privileges.
Administrator rights is a hack, not a solution:)