Error Message: Flash Failed

Trying to write ubuntu-22.04.1-desktop-amd64.iso to a USB Flash Drive. The process starts normally, writes to the new device, and goes through the validation step. At some point during the validation, three new drives appear in Windows Explorer. In every case I get “Flash Failed!”, and the three drives disappear.
I have tried:
a) upgrading from 1.5.116 to 1.7.9
b) repeating the flash operation
c) trying two different USB drives: one 16 GB (USB 2.0), one 64 GB (USB 3.2)

I am running Etcher on Windows 10, but I am not trying to copy Windows to the drive.

I have opened the developer console and copied the error output to a file, but I cannot understand the listing, and it is too big to paste into this posting. I can put it on a web page, if it would be useful.

Similar problem spending hours with multiple attempts using Etcher 1.10.6 to write an image to SD card. Tried multiple SD cards, USB cables, SD adapters.
Realised that Win 10 is attempting to access the devices to format the drive at the instant that Etcher crashes.
Even though Win10 AutoPlay settings on this PC say take no action on Removable drive and Memory card. Microsoft sick arrogance thinks they know better than the user.

Hello there,

i’ve tried many times and flashed different images with etcher 1.10.6 (and other versions as well).

For @bill41 's case my guess is that etcher tries to unmount the drive at the end of the validation and that task fails, so the partitions created by the flashing show up in windows explorer and windows does not understand anything about linux partitions.
If this is happening you may proceed and use the flashed drive.

I must apologise for being stupid. And apologise for bad-mouthing Microsoft.

The SD card readers I tried were old ones (probably with 16-bit address chips in them).
The image file I was wanting to write was 2.1 GB which exceeds the 2 GB limit of 16-bit addressing.

I bought a new SD card reader (USB 3.0) and the process worked perfectly. Thank you Balena Etcher.

1 Like

No worries, and no need to apologize.
This is a very good debugging information.