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.
Google Drive File Stream and user account elevation issue
See original GitHub issue- Etcher version: 1.2.1
- Operating system and architecture: Windows 10 Pro 64-bit (1703)
- Image flashed: ubuntu-17.10-desktop-amd64.iso
- Do you see any meaningful error information in the DevTools?
Description of the issue On a corporate system with Google Drive File Stream installed and connected to a G Suite account, it is currently impossible to flash a USB drive while the virtual network drive Google Drive File Steam (G:) is connected.
This issue occur mainly when the user runs the app without admin privileges and needs to elevate the app through UAC. Since the G: network drive is unreadable to other accounts, it shows this error:
Couldn't scan the drives: Permission eeor
Error: Couldn't scan the drives: Permission error
Workaround Temporarily stop the Google Drive File Stream client if you need to elevate the app to write a USB drive, or completely sign out and login with an account with administrative rights on the system instead of proceeding with a runas.
Is that something that could be filtered out from the drive scan, or at least make USB drives to show up anyway?
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (4 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
Hi, I’ve tried it (back from paternity leave) and it works fine on my end. Thanks for your help!
Sweet, thanks for the update @m-p-3! Closing this then