Etcher waits for a thread. GUI not showing. Win10
See original GitHub issue- Etcher version: 1.1.2
- Operating system and architecture: Windows 10 - 64 bits
- Image flashed: No
- Do you see any meaningful error information in the DevTools? No, gui could not be started
When starting nothing is displayed, but it shows in running processes. When analyzing wait threads, it appears that etcher is waiting for a thread in etcher.
I had to restart the machine and use the portable version.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:4
- Comments:94 (26 by maintainers)
Top Results From Across the Web
Flash failed need help - balenaEtcher - balenaForums
I have a problem (i use win10 64) i wanna flash octopi (2.88gb file size) on my 32gb sandisc sdcard i unzip the...
Read more >Bootable windows 10 USB made with etcher won't boot ...
No bootable device--insert boot disk and press any key. Upon pressing a key it says 'PXE-e61: Media test failure, check cable' and then...
Read more >Why WPF gui not showing on Windows 10?
Since WPF uses DirectX to render its UI, I suspect that the issue is probably caused by graphic driver in Windows 10. Can...
Read more >[SOLVED] - USB not detected and unable to format
I make it bootable with PowerISO and I format it to use as my regular pen drive. Recently I came upon this tool...
Read more >USB flash installation medium - ArchWiki
Tip: If the UEFI version of the USB's Arch ISO hangs or is unable to load, try repeating the medium creation process on...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I thought that I had this problem, but while reading this issue, the GUI finally popped up. So it could be that it just takes a reeeally long time on some systems.
I suspect it is as well, and my question is, why over the last 3 years has there been no indication of anyone collecting detailed information from all the affected people to see if there is a common thread?Also if there is a clear point where it seems to have happened, the above version 1.1.2 works for me, the differences between that version and the next non-working version should be checked.
Are there any frameworks or anything this software uses?
That’s the result when I run it with -disable-gpu
still doesn’t start, but a minor issue is present.