When I tried to flash an .iso to a usb, I get a “Flash Failed” message.
I’ve formatted the usb
My os is windows 10
Hello there,
do you have any questions about it, or do you want to share the failure message?
Yes I have a question. I would like a solution, so I can make a bootable usb.
I’ve downloaded Linux Mint, and it is an iso. Etcher is recommended.
Quote from linux mint
" In Windows, Mac OS, or other Linux distributions
Download Etcher, install it and run it."
From this short desctiption it is pretty difficult to see what could have gone wrong. So lets start at the beginning.
- you download etcher from the official site
- you install it and run it
- you downloaded a linux mint (live?) image
- you have a big enough pendrive / sd card
- the pendrive / sdcard is not old/corrupted
in etcher:
- you run it as administrator
- you don’t have windows defender or other antivirus blocking access
- you select the image as source
- you select your plugged in pendrive as target
- you click flash
- a window pops up to ask for your admin password (not necessary if already run as admin)
- flash starts, you see a progress bar
- flash finishes and verifying starts, you see a different progress bar
- verify finishes or you skip it, success screen appears
- you have a bootable pendrive/sdcard (which looks weird on windows, but boots linux)
I hope this steb by step list helps. Where I put question marks are the spots where the problem could be but it is not clear from your message. The green ticks are also just guesses based on your message, that you succeeded with those steps/requirements.
Let us know if it answered your question.
Hi Peter,
in etcher:
After clicking Flash,. I get a progress bar.
After a few seconds a window pops up saying Flash Failed
Hey Gary,
Would you mind confirming if this happens or not?
Or if you are running etcher as an admin?
@Repairman1946
Also, it’s hard to help when we have so little detail about what might be going wrong.
Can you please confirm the version of etcher you are running? (click the settings button on the first window to see the version.
Then after you see the flash failed message please press: Ctrl+Shift+I and send us the logs from the console window of the developer tools that open.
Example of what the console window looks like:
Thank you,
-Thomas
Hi Thomas,
I will have to reinstall Etcher, and will gather all information.
Gary
Hi Thomas,
I have made a bootable disc, so I don’t need a bootable USB.
In the process of trying to create a bootable USE, it ruined 3 USB sticks.
Gary
Hi Thomas,
it is unlikely that etcher by itself makes a USB stick unusable.
Etcher broke my USB stick … or did it? on this link you find several ways to recover them.
Thank you mcraa.
I will try and recover the three USB sticks.
Gary
Thanks, my issue has been fixed.
I’ve had a similar issue when trying to flash “linuxmint-21.2-cinnamon-64bit.iso”. Seems to flash OK, but verification fails. I successfully flashed earlier Linux Mint using an earlier version of balenaEtcher last year, using the same USB stick. I’ve re-partitioned and formatted the USB drive to NTFS, I also initially tried with the earlier version balenaEtcher, but then updated to 1.18.11, both gave essentially the same failure.
When I try to install Linux Mint 21.2 from the flashed USB, it only boots to Live version, but install fails, so I’m guessing there is a corruption somewhere.
Any thoughts gratefully received.
The following is the log dump from balenaEtcher with username in path redacted. The log includes the Issues at the end, which highlighs “To fix this issue, replace the usage of navigator.userAgent, navigator.appVersion, and navigator.platform with feature detection, progressive enhancement, or migrate to navigator.userAgentData.”:
=====
Failed to load resource: net::ERR_FILE_NOT_FOUND
gui.js:354 _____ _ _
| | | | |
| | | | | | ___ _ __
| || / | ’ \ / _ \ '|
| || || (| | | | / |
_/ ____|| ||___||
Interested in joining the Etcher team?
Drop us a line at join+etcher@balena.io
Version = 1.18.11, Type = nsis
gui.js:37 Elevating command: C:\Users\xxx\AppData\Local\Programs\balena-etcher\balenaEtcher.exe C:\Users\xxx\AppData\Local\Programs\balena-etcher\resources\app\generated\child-writer.js
gui.js:37 Error: Error invoking remote method ‘disable-screensaver’: No handler registered for ‘disable-screensaver’
at o.invoke (node:electron/js2c/renderer_init:57:526)
(anonymous) @ gui.js:37
gui.js:35 0 devices, 0% at 0.00 MB/s (total 0.00 MB/s) with 0 failed devices
gui.js:37 Successfully connected to IPC server: etcher-server-12948, socket root C:\Users\xxx\AppData\Local\Temp
gui.js:37 Image: C:\Users\xxx\Downloads\linuxmint-21.2-cinnamon-64bit.iso
gui.js:37 Devices: \.\PhysicalDrive2
gui.js:37 Auto blockmapping: true
gui.js:37 Decompress first: true
gui.js:37 Finish: 0
gui.js:37 Terminating IPC server
gui.js:37 Flash results Object
gui.js:37 Error: Error invoking remote method ‘enable-screensaver’: No handler registered for ‘enable-screensaver’
at o.invoke (node:electron/js2c/renderer_init:57:526)
(anonymous) @ gui.js:37
gui.js:37 Elevating command: C:\Users\xxx\AppData\Local\Programs\balena-etcher\balenaEtcher.exe C:\Users\xxx\AppData\Local\Programs\balena-etcher\resources\app\generated\child-writer.js
gui.js:37 Error: Error invoking remote method ‘disable-screensaver’: No handler registered for ‘disable-screensaver’
at o.invoke (node:electron/js2c/renderer_init:57:526)
(anonymous) @ gui.js:37
gui.js:35 0 devices, 0% at 0.00 MB/s (total 0.00 MB/s) with 0 failed devices
gui.js:37 Successfully connected to IPC server: etcher-server-12948, socket root C:\Users\xxx\AppData\Local\Temp
gui.js:37 Image: C:\Users\xxx\Downloads\linuxmint-21.2-cinnamon-64bit.iso
gui.js:37 Devices: \.\PhysicalDrive2
gui.js:37 Auto blockmapping: true
gui.js:37 Decompress first: true
gui.js:37 Finish: 0
gui.js:37 Terminating IPC server
gui.js:37 Flash results Object
gui.js:37 Error: Error invoking remote method ‘enable-screensaver’: No handler registered for ‘enable-screensaver’
at o.invoke (node:electron/js2c/renderer_init:57:526)
(anonymous) @ gui.js:37
logException @ gui.js:37
(anonymous) @ gui.js:354
Issues:
Audit usage of navigator.userAgent, navigator.appVersion, and navigator.platform
1. A page or script is accessing at least one of navigator.userAgent, navigator.appVersion, and navigator.platform. Starting in Chrome 101, the amount of information available in the User Agent string will be reduced.
To fix this issue, replace the usage of navigator.userAgent, navigator.appVersion, and navigator.platform with feature detection, progressive enhancement, or migrate to navigator.userAgentData.
Note that for performance reasons, only the first access to one of the properties is shown.
2. AFFECTED RESOURCES
1. 1 source
gui.js:1
1.
I’ve now resolved this.
I ended up buying a new SanDisk USB flash drive and it worked perfectly first time. I suspect my previous USB sticks were corrupt, so have destroyed them now.