Etcher stuck at " Decompressing...100%"

Hi There,
I trying to flash image to SD card but it stuck at " Decompressing…100%" What is the problem can someone help me to solve this? I had tried different laptop and PC and also tried different SD card but no luck. Please help. Thanks.
I was using Windows 10.

It sounds like you have tried changing everything except the actual image to be flashed. Can you try that (use something standard like Raspbian) and see if it fixes the problem? That way we know the culprit is the image and someone from Balena can reproduce it locally.

One other thing I’ll ask: if you are still encountering this, can you please open up the Developer Tools in Etcher and copy-paste the output you see into a reply to this thread? You can do this by hitting Ctrl-Shift-i.

Thanks,
Hugh

I’m having this problem as well. I was able to flash the first image to the card, but now nothing.

So, I deleted and reinstalled, and used a freshly downloaded openhabian image file.
Still no joy.
Here’s a console snippet:

Decompressing , 82% at 58.90 MB/s (total 0.00 MB/s) eta in 11s with 0 failed devices   gui.js:6038 
Decompressing , 84% at 67.80 MB/s (total 0.00 MB/s) eta in 9s with 0 failed devices    gui.js:6038 
Decompressing , 85% at 66.80 MB/s (total 0.00 MB/s) eta in 8s with 0 failed devices    gui.js:6038 
Decompressing , 88% at 65.90 MB/s (total 0.00 MB/s) eta in 7s with 0 failed devices    gui.js:6038 
Decompressing , 90% at 87.70 MB/s (total 0.00 MB/s) eta in 4s with 0 failed devices    gui.js:6038 
Decompressing , 93% at 95.00 MB/s (total 0.00 MB/s) eta in 3s with 0 failed devices    gui.js:6038 
Decompressing , 94% at 77.30 MB/s (total 0.00 MB/s) eta in 2s with 0 failed devices    gui.js:6038 
Decompressing , 96% at 69.10 MB/s (total 0.00 MB/s) eta in 2s with 0 failed devices    gui.js:6038 
Decompressing , 99% at 76.30 MB/s (total 0.00 MB/s) eta in 0s with 0 failed devices    gui.js:6038 
Decompressing , 100% at 72.10 MB/s (total 0.00 MB/s) eta in 0s with 0 failed devices

Then, it sits there…

I’m going to try a different machine and SD Card, and will update with those results.