Trezor/KeepKey webusb does not work in VirtualBox with Windows guest
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.6k
- Forks
- 3.5k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 61
Description
Trezor/KeepKey is not detected when using VirtualBox with a Windows guest.
See https://github.com/trezor/trezord-go/issues/148
From https://github.com/trezor/trezord-go/issues/148#issuecomment-504519583:
On fresh Windows 10 1809 guest VM using VirtualBox 6.0.8, Trezor Bridge does not see Trezor One device.
Host machine is also running Win10.
After installing WinUSB driver through Zadig, the Bridge now sees the device.
Note that even without using Trezor Bridge, and using webusb/libusb directly through Electrum, the same issue applies. The workaround is to use Zadig.
Mostly logging this issue for myself for future reference; but if someone knows how to fix it, that would be most welcome.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the Trezor/KeepKey detection failure in a Windows guest running under VirtualBox, using the WebUSB/libusb path described in the issue. Compare behavior with and without the Zadig WinUSB driver and consult trezord-go issue 148. Done means the device is detected without the workaround, or the project documents that the problem is external to Electrum.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100