Echer 1.19.21 "Something went wrong. If it is a compressed image, please check that the archive is not corrupted".

[saulpugg]

• Etcher version:
• Operating system and architecture:
• Image flashed:
• What do you think should have happened:
• What happened:
• Do you see any meaningful error information in the DevTools?

[saulpugg]

The software doesn't allow me to flash the USB stick. It stops showing the message shown on the title.

[gramtech]

Hey, I am having the same issue, I have tried a couple different USB sticks, one of which I have used before with Etcher

Etcher version: 1.19.25
Operating system and architecture: MacOS Somona, Intel 
Image flashed: ubuntu-mate-24.04.1-desktop-amd64.iso 
What happened: Received the following error:

Something went wrong. If it is a compressed image, please check that the archive is not corrupted.
The writer process ended unexpectedly

[SeQwintial]

I have also received the same error as the above comment; in addition, 4 separate windows popped up during the validation process telling me I needed to format the new drives (each one is partitioned from the flash, i'm assuming) before I can use them. Is Windows getting in the way of the final validation?

[juniorr001]

I solved it by running as administrator.
right click on the shortcut > run as administrator.

[SeQwintial]

I solved it by running as administrator. right click on the shortcut > run as administrator.

I have unfortunately tried this, as well as disabling my antivirus/windows defender, and trying it in a different usb slot. Attempting to boot the kobo with the sd card in it also does nothing (in the case that the validation error was irrelevant and the flashing had worked properly)

[2ZZ]

This is happening every time on MacOS for me, I tried 3 different Macbooks, different USB sticks and all on the latest version of Etcher.

[stellar-liyanbin]

I first tried flashing the file in the file.img.xz format, but it failed. Then I tried extracting it to somefile.img first and then flashing it, and that worked, all on MacOS.

[fatso83]

@saulpugg There is absolutely nothing to go by in your bug reports. It's near useless when you don't even bother filling out the template. Like which version, which os, ... how do you expect anyone to be able to work with this?

[2ZZ]

I first tried flashing the file in the file.img.xz format, but it failed. Then I tried extracting it to somefile.img first and then flashing it, and that worked, all on MacOS.

My failures were with .xz as well.

[SeQwintial]

I first tried flashing the file in the file.img.xz format, but it failed. Then I tried extracting it to somefile.img first and then flashing it, and that worked, all on MacOS.

My failures were with .xz as well.

I've solved my problem with this, and it turns out I had to extract the .xz file first before attempting to flash it. Worked on first attempt, Win10.

(Note the "0-N905C file" extension - this was the one that worked)

[MrTechGadget]

I am also experiencing this issue on macOS with 1.19.25 on a .img.xz image that I have used dozens of times with no issues with 1.7.8. Apparently there has been a feature regression.