Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Drives locked by Bitlocker causes "Couldn't scan the drives: An unknown error occurred" error message
See original GitHub issue-
Etcher version: 1.1.2 (64bit and 32bit)
-
Operating system and architecture: Windows 10 Pro 64bit
-
Image flashed: Any
-
Do you see any meaningful error information in the DevTools? Not sure
Under resolved issue 1639 I also had the error message “Couldn’t scan the drives: An unknown error occurred”. I had locked drives using bitlocker but once unlocked the program works as expected. I was asked to make a new issue from the closed issue 1639.
Original message:
I just joined github to leave this comment, I was also receiving the error “Couldn’t scan the drives: An unknown error occurred”. I have 2 drives that I lock with bitlocker. Once I unlocked them I was then able to scan my drive like it should. Once I locked my drives again I ended up getting the error again and can repeat it.
I am running the 64bit version on windows.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@mgalde This should be fixed by https://resin-nightly-downloads.s3.amazonaws.com/etcher/2017-08-21/1.1.2%2Bf9d7dd2/Etcher-Setup-1.1.2%2Bf9d7dd2-x64.exe
Sounds great, but it’d require some non-trivial amount of refactoring on the drivelist module (e.g. to emit errors but still emit the drives that worked fine). Do you mind creating a new ticket so we can come back to it later?