I wanted to comment I am having the same issue on my Win10 machine. I’m using balenaEtcher v1.5.70 on my windows machine which is running an Evaluation copy, Build 19536.rs_prelease.191211-1446.
Target: 64GB SanDisk Extreme microSD (SDSQXA2-064G-GN6MA)
I get the same results as the OP. I have tried;
- I checked the source file Hash (good)
- Verified I am running as admin
- I formatted the microSD to exFAT (Etcher when it starts wipes this)
- I extracted the ISO from the Zipped file
- Used a different USB adaptor
- Rebooted my PC
- Tried several other images (Fedora, BlackArch & Kali).
- Used a USB drive rather than the SD card (Innostor USB 4.03 GB)
I gave up on Etcher and tried Rufus (v3.1.1320) and it seemed to work fine.
Problem Solved, at least in my case. I have Controlled Folder Access enabled. For some reason balenaEtcher was trying to write to a folder under My Documents (In my case this is D:). I authorized it to access that controlled folder and it was able to burn the file. I’m uninstalling the program for now, I don’t really like a program writing to My Documents without a good reason.