Etcher 1.5.5 windows, writer process problem

I upgraded from 1.4.4 today and hit this issue. Last month I upgraded to Win 10 1809 and this is my first use after OS upgrade.

This is the relevant part from the console (happened for different images and sd-cards):

Tue Mar 05 2019 06:11:49 GMT+0300 (Turkey Standard Time) Flash error ({“error”:{“name”:“Error”,“message”:“EPERM: operation not permitted, write”,“stack”:“Error: EPERM: operation not permitted, write”,“code”:“EPERM”,“syscall”:“write”,“errno”:-4048},“applicationSessionUuid”:“8632f56a-7eec-4d6d-9916-81e6ff386c82”,“flashingWorkflowUuid”:“bb07637d-ebc8-492b-8a21-f126fc82a43d”,“flashInstanceUuid”:“84b2fd2c-8624-49be-b295-5eb4d08a628b”,“image”:“M:\__EX_SERVE_BACKUP_SYS_OLD\hkbox-os-images\OPi\PC2\Armbian_5.75_Orangepipc2_Ubuntu_bionic_next_4.19.20_desktop.img”,“drives”:[{“size”:31914983424,“isVirtual”:false,“enumerator”:“USBSTOR”,“logicalBlockSize”:512,“raw”:“\\.\PhysicalDrive7”,“error”:null,“isReadOnly”:false,“displayName”:“U:\”,“blockSize”:512,“isSCSI”:false,“isRemovable”:true,“device”:“\\.\PhysicalDrive7”,“busVersion”:“2.0”,“isSystem”:false,“busType”:“USB”,“isCard”:false,“isUSB”:true,“devicePath”:null,“mountpoints”:[{“path”:“U:\”}],“description”:“Generic MassStorageClass USB Device”,“isUAS”:false}],“driveCount”:1,“uuid”:“84b2fd2c-8624-49be-b295-5eb4d08a628b”,“unmountOnSuccess”:true,“validateWriteOnSuccess”:true})

@bozden did you see a windows elevation dialog when you clicked “Flash”?

Yes, of course… I tried 3 Sandisk Ultra 32GB sd cards one after another with the same result. I therefore reported here…

But those were used ones from last year. I’m more inclined to think that those are defective.
I ordered 5 new Sandisk Ultra A1 16GB sd-cards, lets see what happens…

BTW, is there a public list of errors names/id’s somewhere?

I just tried SD Card Formatter v5.x on these sd-cards, on the same machine with another old USB2 sd-card reader.

In one case it caused a BSOD (very interesting), the other two did error out with “Formatting failed”.

They were indeed defective. Sorry for the confusion and hijacking of the thread.

No worries @bozden. Thanks for the followup. Hope the new SD cards serve you better : )

I’m actually having the same problem now. I’ve tried using SD cards from Samsung and SanDisk. I’m trying to write a Raspberry Pi image ( 2018-11-13-raspbian-stretch-full.img ) from a Windows 10 x64 machine. I’ve been able to successfully read and write from the SD cards from other applications. In my case I do not believe that the cards that I am using are defective.

After selecting the card and the image I get the Security Elevation prompt in Windows. After giving permission there is an immediate failure. The message I get is identical to what is in the OP.

I’ve copied and pasted the log (minus the time stamps) below.

Modal accepted ({"name":"warning","value":true,"applicationSessionUuid":"d54da878-bc21-4f53-a895-71fc347bf108","flashingWorkflowUuid":"04e45594-252d-42bd-894a-b4d41507523f"})
    Restart after failure ({"applicationSessionUuid":"d54da878-bc21-4f53-a895-71fc347bf108","flashingWorkflowUuid":"04e45594-252d-42bd-894a-b4d41507523f"})
Flashing 0 devices, 0% at null MB/s (total null MB/s) eta in undefineds with 0 failed devices
Flash ({"image":"C:\\Users\\joel\\Downloads\\2018-11-13-raspbian-stretch-full.img","drives":[{"size":15931539456,"isVirtual":false,"enumerator":"USBSTOR","logicalBlockSize":512,"raw":"\\\\.\\PhysicalDrive4","error":null,"isReadOnly":false,"displayName":"F:\\","blockSize":512,"isSCSI":false,"isRemovable":true,"device":"\\\\.\\PhysicalDrive4","busVersion":"2.0","isSystem":false,"busType":"USB","isCard":false,"isUSB":true,"devicePath":null,"mountpoints":[{"path":"F:\\"}],"description":"Generic MassStorageClass USB Device","isUAS":false}],"driveCount":1,"uuid":"76b79576-1319-4b8c-9961-4b34cd7451fa","status":"started","flashInstanceUuid":"76b79576-1319-4b8c-9961-4b34cd7451fa","unmountOnSuccess":true,"validateWriteOnSuccess":true,"applicationSessionUuid":"d54da878-bc21-4f53-a895-71fc347bf108","flashingWorkflowUuid":"04e45594-252d-42bd-894a-b4d41507523f"})
Elevating command: C:\Users\joel\AppData\Local\Programs\balena-etcher\balenaEtcher.exe C:\Users\joel\AppData\Local\Programs\balena-etcher\resources\app.asar
SafeWebview loaded ({"event":{"fromCache":false,"headers":{"Accept":"text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8","Upgrade-Insecure-Requests":"1","User-Agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) balena-etcher/1.5.5 Chrome/66.0.3359.181 Electron/3.1.3 Safari/537.36"},"id":177,"method":"GET","referrer":"","resourceType":"mainFrame","responseHeaders":{"access-control-allow-origin":["*"],"age":["489"],"cache-control":["max-age=600"],"cf-ray":["4b6e6f5e581ac546-ORD"],"content-encoding":["br"],"content-type":["text/html; charset=utf-8"],"date":["Wed, 13 Mar 2019 13:43:07 GMT"],"expect-ct":["max-age=604800, report-uri=\"https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct\""],"expires":["Wed, 13 Mar 2019 07:35:36 GMT"],"last-modified":["Tue, 05 Mar 2019 17:31:05 GMT"],"server":["cloudflare"],"status":["200"],"vary":["Accept-Encoding"],"via":["1.1 varnish"],"x-cache":["HIT"],"x-cache-hits":["2"],"x-fastly-request-id":["a33d2b23569ffc863aa21e1bd8b21051610d3d1a"],"x-github-request-id":["83D6:07D4:E51C4:1342DF:5C88B070"],"x-served-by":["cache-mdw17377-MDW"],"x-timer":["S1552484587.259467,VS0,VE0"]},"statusCode":200,"statusLine":"HTTP/1.1 200","timestamp":1552484585677.9832,"url":"https://assets.balena.io/etcher-featured/index.html?etcher-version=1.5.5&api-version=2"},"applicationSessionUuid":"d54da878-bc21-4f53-a895-71fc347bf108","flashingWorkflowUuid":"04e45594-252d-42bd-894a-b4d41507523f"})
Flash results {cancelled: false}
Terminating IPC server
pen modal ({"name":"warning","applicationSessionUuid":"d54da878-bc21-4f53-a895-71fc347bf108","flashingWorkflowUuid":"04e45594-252d-42bd-894a-b4d41507523f"})

I tried rolling back to version 1.5.0 Portable and received the same error.

I had to move over to the OS X version of Etcher to write the image from a different machines. I wasn’t able to write any image to any card using the Windows version.

I have a problem flash but validation stop at 28 percents . what going on guys

@grannysgt what OS are you running Etcher on?

Windows 10

I have the same problem. My OS is Windows 10. Is there any update for this?

I’m getting exactly the same issue running on Windows 10 1809 with Etcher 1.5.56.

Tue Sep 17 2019 18:35:55 GMT+1000 (AUS Eastern Standard Time) Flash error ({“error”:{“name”:“Error”,“message”:“EPERM: operation not permitted, write”,“stack”:“Error: EPERM: operation not permitted, write”,“code”:“EPERM”,“syscall”:“write”,“errno”:-4048},“applicationSessionUuid”:“aa57119b-f598-40a0-868d-7e00db44d982”,“flashingWorkflowUuid”:“276a7714-00ea-4bd0-83cc-ebc5ca063b59”,“flashInstanceUuid”:“d58c45a7-0fea-4490-b356-6e4164eb782a”,“image”:“C:\Users\Jarrett\Desktop\balena.img”,“drives”:[{“size”:7948206080,“isVirtual”:false,“enumerator”:“USBSTOR”,“logicalBlockSize”:512,“raw”:“\\.\PhysicalDrive2”,“error”:null,“isReadOnly”:false,“displayName”:“E:\”,“blockSize”:512,“isSCSI”:false,“isRemovable”:true,“device”:“\\.\PhysicalDrive2”,“busVersion”:“2.0”,“isSystem”:false,“busType”:“USB”,“isCard”:false,“isUSB”:true,“devicePath”:null,“mountpoints”:[{“path”:“E:\”}],“description”:“Mass Storage Device USB Device”,“isUAS”:false}],“driveCount”:1,“uuid”:“d58c45a7-0fea-4490-b356-6e4164eb782a”,“unmountOnSuccess”:true,“validateWriteOnSuccess”:true,“trim”:false,“sample”:0.1})

This is occurring with multiple SD cards/brands and SD card readers. Has anyone found a solution for this?

Hi, we’re still trying to figure this out unfortunately. Have you already tried starting etcher with admin privileges?

Also, which version of etcher is giving you this issue?

Hi! I’m facing the same problem with etcher 1.5.56.
Last week it worked well, but now I receive the same error as above. Windows tries to mount the USB stick a few times while flashing.
I tried both as regular user and with admin privileged. Same error.

@rene hi there! Windows defender has a “Controlled folder access” setting which can cause unexpected permissions errors. It might be worth looking into if that could be the cause for your issue (It have been disabled by default in the past, but maybe it’s not in some installs?) . More info: https://support.microsoft.com/en-us/help/4046851/windows-10-allow-blocked-app-windows-security

3 Likes

This worked for me. I think that a recent update to Windows 10 may have switched this setting on.

Hi,
Great to hear that it worked for you. We will see how/if we can mitigate this issue in the future.

I had the same problem. Was trying to get an image of Hassio onto a Samsung 64GB EVO SD card.
Searched everywhere on the internet for a solution.
The solution was as described by mikesimos. I added balenaEtcher to the list of excluded programs to block and everything is fine.

Nice Mike thanks

Maybe short term solution is to catch the error and get the user to check windows defender permissions

Thanks Mike. This did the trick for me also! explains why it started happening “all of a sudden” too… it worked for me months ago… and stopped working, but I did enable windows defender recently!