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.
Unable to open an image from the mapped network drive
See original GitHub issue- Etcher version: 1.5.51
- Operating system and architecture: Windows 10 Home x86-64
- Image flashed: Any
- Environment: Windows 10 Home is executed in the VMware Fusion on a Mac
- This is probably irrelevant, because the problem is with mapped network drives
- Forums post: Etcher on Windows7 under VMware can only access C drive?
VMware Fusion can share folders from the host OS. It’s implemented via mapped network drives.
When I open an image from Z:\SharedWithVM\..., etcher thinks that the location is C:\SharedWithVM\... (Z -> C) and fails to open the image. Nothing interesting in logs, just ENOENT with wrong path:
I’ve found an old issue with suggested workaround (comes from the Microsoft Support). I have this value already set …
… and it still doesn’t work.
It works if the image is copied to a local drive.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:25 (20 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
@lurch we don’t know if the read will fail in the writer process at this point.
@lurch that makes sense, but this error appears immediately after the image selection. I mean, target device not selected yet, didn’t click on the Flash button, just launched Etcher and selected an image. AFAIK elevated privileges are required when I click on the Flash button.