DMT cannot connect to Trezor device about dash-masternode-tool

[Bertrand256]

Try one of these options:

1. install/update Trezor Bridge (https://wiki.trezor.io/Trezor_Bridge)
2. run DMT as Administrator
   Windows update 1903 requires leveraged privileges for apps using libusb, but if you have Trezor Bridge installed (solution 1) you should be able to avoid having to run the app as Administrator (solution 2).

[tbonestone]

Great, thank you! Solution 1 worked.

[tbonestone]

Hi I am having the exact same issue as above! I have the latest DMT and trezor bridge and it is running in the back ground, but DMT still gives the 'no hardware wallet device detected'. Not sure what to try now? Any help is greatly appreciated.

[Bertrand256]

Hi. Does this problem occur in both, v0.9.26 and v0.9.27 or only in the latest one?
If you send me (by email) the contents of the app log file from the time when you started it to the time after the error occurred, it will very helpful in diagnostics. Thanks.

[tbonestone]

great thank you.   I have not tried to use the V09.26, recently, but when I had the problem last Aug, your suggestion to use the Trezor bridge fixed the problem in the usb drive.   The V09.27 seems to not work with either the Trezor bridge or running as admin.    Here is the log file attached.    On Monday, May 24, 2021, 01:36:00 PM MDT, Bertrand256 ***@***.***> wrote: Hi. Does this problem occur in both, v0.9.26 and v0.9.27 or only in the latest one? If you send me (by email) the contents of the app log file from the time when you started it to the time after the error occurred, it will very helpful in diagnostics. Thanks. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe. [...] logs truncated

[tbonestone]

I did run the v09.26 and it does recognize the device.   Thanks. On Monday, May 24, 2021, 02:56:58 PM MDT, Travis Eiseman ***@***.***> wrote: great thank you.   I have not tried to use the V09.26, recently, but when I had the problem last Aug, your suggestion to use the Trezor bridge fixed the problem in the usb drive.   The V09.27 seems to not work with either the Trezor bridge or running as admin.    Here is the log file attached.    On Monday, May 24, 2021, 01:36:00 PM MDT, Bertrand256 ***@***.***> wrote: Hi. Does this problem occur in both, v0.9.26 and v0.9.27 or only in the latest one? If you send me (by email) the contents of the app log file from the time when you started it to the time after the error occurred, it will very helpful in diagnostics. Thanks. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe.

[Bertrand256]

great thank you.   I have not tried to use the V09.26, recently, but when I had the problem last Aug, your suggestion to use the Trezor bridge fixed the problem in the usb drive.   The V09.27 seems to not work with either the Trezor bridge or running as admin.    Here is the log file attached.    On Monday, May 24, 2021, 01:36:00 PM MDT, Bertrand256 @.***> wrote: Hi. Does this problem occur in both, v0.9.26 and v0.9.27 or only in the latest one? If you send me (by email) the contents of the app log file from the time when you started it to the time after the error occurred, it will very helpful in diagnostics. Thanks. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe. [...] logs truncated

Thanks for the log file. I've removed it from plain sight though, as it may include some sensitive data.

[Bertrand256]

I did run the v09.26 and it does recognize the device.   Thanks.
I will try to reproduce the problem on other windows machines. I'd like to know the actual cause, because using the old version isn't a good long-term solution.

[Bertrand256]

Check the latest windows build for v0.9.27. It should resolve the issue and additionally it should work fine without having to run it as administrator.

[tbonestone]

Excellent!   Thank you, for the help.   It works wonderfully. On Tuesday, May 25, 2021, 03:43:55 PM MDT, Bertrand256 ***@***.***> wrote: Check the latest windows build for v0.9.27. It should resolve the issue and additionally it should work fine without having to run it as administrator. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe.

[Bertrand256]

Excellent!   Thank you, for the help.   It works wonderfully.
Great. Thanks for the feedback!