etcher: Error: (0 , h.requestMetadata) is not a function
- Etcher version: 1.18.13 - 1.19.3
- Operating system and architecture: NixOS, x86_64-linux
- Image flashed: Arbitrary image
- What do you think should have happened: Image selected successfully, being able to select target
- What happened: Can’t select any image
- Do you see any meaningful error information in the DevTools? No, same error as above.
In Nixpkgs we package Etcher on the basis of the official deb. The procedure no longer works as of 1.18.13.
Likely a continuation of #4138. Probably that issue should be reopened? @dfunckt
About this issue
- Original URL
- State: open
- Created 3 years ago
- Reactions: 79
- Comments: 253 (12 by maintainers)
Commits related to this issue
- Revert "sys-boot/etcher-bin - upstream version increase (pre-release v1.19.2)" This reverts commit 3906e4953b8661dc7d7d7a5c6c2a294bb1c88940. Reverting update(v1.19.2 -> v1.18.12) Upstream Bug #4150 -... — committed to scottfurry/FurCaT_Gentoo by deleted user 3 years ago
- fix: etcher-util is corrupted in RPM package rpmbuild strips executables by default when generating an rpm packge. This was causing the JavaScript code bundled in the etcher-util file to be removed, ... — committed to rglidden/etcher by rglidden 2 years ago
- fix: etcher-util is corrupted in RPM package rpmbuild strips executables by default when generating an rpm packge. This was causing the JavaScript code bundled in the etcher-util file to be removed, ... — committed to rglidden/etcher by rglidden 2 years ago
- patch: etcher-util is corrupted in RPM package rpmbuild strips executables by default when generating an rpm packge. This was causing the JavaScript code bundled in the etcher-util file to be removed... — committed to rglidden/etcher by rglidden 2 years ago
- patch: etcher-util is corrupted in RPM package rpmbuild strips executables by default when generating an rpm packge. This was causing the JavaScript code bundled in the etcher-util file to be removed... — committed to balena-io/etcher by rglidden 2 years ago
- patch: etcher-util is corrupted in RPM package rpmbuild strips executables by default when generating an rpm packge. This was causing the JavaScript code bundled in the etcher-util file to be removed... — committed to balena-io/etcher by rglidden 2 years ago
Same issue on Ubuntu 22.04 with X11 using balenaEtcher-1.19.3-x64.AppImage but no error when using balenaEtcher-1.18.11-x64.AppImage
Like you but I’m using ArchLinux 😦
I simply skipped all 1.19.xx releases & pre-releases… and downloaded the last stable release (AppImage) which is v1.18.11. It works for me 😃
Nor
balena-etcher_1.19.21_amd64.deborbalenaEtcher-1.19.21-x64.AppImageworked for me onUbuntu 24.04. The only one that worked was the one from the balenaEtcher-linux-x64-1.19.21.zip package by running the main binary.I went to the Releases page and downloaded the .zip package. Then, I extracted and went inside the directory, finally, I was able to run it with the following command:
After that, I could attach the
.isoand flash it successfully.On
Arch Linux, the one that I normally use was the version installed fromAURviayay.On arch linux, installed https://aur.archlinux.org/packages/etcher-bin from the AUR and it works, https://aur.archlinux.org/packages/balena-etcher shows the error. For what is worth, the etcher-bin pkg was last updated 2023-07-15, while balena-etcher was updated 2023-12-20.
Also having this issue on Manjaro
Solved! Just check the compatibility settings of balena and you’re good to go!
Having the same issue with Arch Linux 6.4.12-arch1-1 and the version of etcher balenaEtcher-1.19.21-x64.AppImage. I found a way to bypass using the previous version:
https://github.com/balena-io/etcher/releases/tag/v1.18.11
I wanted to share my experience with this issue and thank a couple of users for their helpful suggestions.
I’m using Linux Mint 22.1, and I encountered this issue where the latest version of Balena Etcher didn’t work properly. After some troubleshooting, I found a couple of solutions that worked:
@github12101 suggested using GNOME Disks to write the image to the USB stick. This worked perfectly and was a great alternative to Balena Etcher, which I had trouble with. I highly recommend this method as it was easy to use and reliable!
@boddedo recommended using an older version of Etcher (v1.18.11). After trying it, I found that this version worked without issues on my system. This was another great suggestion, and it solved my problem with the newer versions.
While these solutions worked for me, I think the issue with newer Etcher versions still needs some attention. It would be great if the team could look into it or provide some guidance on how to get the latest version working reliably on Linux Mint 22.1 (and other distributions).
this has been an issue for 5 months with the balena-etcher aur. upon removing balena-etcher and replacing with etcher-bin, the issue is resolved.
The AppImage available on the website isn’t working. I just used the zip available in the latest release on GitHub, and it’s working for me! Thanks @entrusc and @leemm! 😃
Run the program as Admin, it’s fixed when I did that
@polsvoice @TerrorBite @myxor @gaby64 @wegank @lh1207 @GarlandKey @ShalokShalom @pamo22 @arbaes Looks like they finally fixed it with this commit > https://github.com/balena-io/etcher/commit/2dfa795129e287f887b9ea02f2eca717575d27ac
Archlinux, Is this same problem?
I have moved to Disks (from Gnome, but works on KDE. Package name is gnome-disk-utility). Select a drive, then select Restore Disk Image from menu and point to your ISO. It will be written to the drive without fail. I’ve dumped BalenaEtcher.
It is now painfully obvious to me that there is no interest in fixing this bug. A year plus and they have not addressed it? Might as well be a dead project. Moving on to other means to write linux boot USB’s.
Latest version without this issue: 1.18.12 After this version we have this issue.
Helped me a lot. Fedora 40. Thanks.
I also had the same problem when I plugged in two USB devices, then I unplugged one of the devices, restarted ether, and there was no error when I selected the image file again
Same error here on Fedora 40 with Wayland. Using version 1.18.11 this issue does not appears. The link below is to this version that worked for me. https://github.com/balena-io/etcher/releases/tag/v1.18.11
Same problem here with EndeavourOS.
It looks like the move to building with electron-forge causes build issues on Arch, and this is why the AUR package is still on version 1.18.
Hello !
Config:
I’m here to tell you I have the same problem ! as the Author :
Error: (0 , h.requestMetadata) is not a functionWhen I want to create a USB Key with Ubuntu 24.04.2 iso image on it.
The problem is exist for all versions greater than and equal to
1.18.13also this message on 1.18.12, but nothing on 1.18.11:or
IDK why in theses version the key failed the “verify” test because the USB Key disconnect/reconnect
Test with latest Balena-etcher:
.debin 2.1.0During the install with the
deb, I fixed the error:'/opt/balenaEtcher/chrome-sandbox': No such file or directorywith:sudo ln -s /usr/lib/balena-etcher /opt/balenaEtcher ; sudo chmod 4755 /opt/balenaEtcher/chrome-sandboxError during the execution:
Theses 2 lines at the end (with the
AppImageordebversion)Test with older version (
1.18.11):Package gconf was deprecated…
Missing dependencies when installing the deb:
same in debian: https://packages.debian.org/bullseye/gconf2
It work ! with the
AppImage 1.18.12orAppImage 1.18.11!I tried the version
balenaEtcher-1.18.11-x64.AppImageEDIT: problem with “AppArmor” ? You can disable with that: https://askubuntu.com/questions/1511854/how-to-permanently-disable-ubuntus-new-apparmor-user-namespace-creation-restric
EDIT2: IDK why in theses version the key failed the “verify” test because the USB Key disconnect/reconnect, but the ISO is on the key and it work without problem !
Findings: Ticket itself: Assignees No one assigned
Labels No labels Type No type Projects No projects Milestone No milestone
Relationships None yet
Opened on on Dec 21, 2023
Countless posters have confused issue with windows errors. There has been no attempt at moderation by team. The issue has not been addressed, resolved, or otherwise mentioned by team. No work around identified. The issue persists after 13 months. Linux App Image is still unusable. Deb packages still unusable.
This still happens with the just released balenaEtcher-2.0.0-x64.AppImage.
I got redirected to this thread and I’m on Windows. It seems it’s an issue arising for all operating systems.
This problem also applies to Mac OS. I found a workaround to get the result The terminal runs
sudo /Applications/balenaEtcher.app/Contents/MacOS/balenaEtcher.fixed by running as administrator on windows
Can confirm this still happens in Ubuntu 24.04 with latest AppImage (1.19.21).
Downloading the zip from github, and running
./balena-etcher --no-sandboxfrom it’s root folder works.I have the same issue in Ubuntu 23.10 using the AppImage (v 1.19.21).
I found that when I download the
.zipversion and use that one, that it works properly (the sub process starts as intended). So I conclude that the issue is somehow caused by packing the app as AppImage.@lh1207 So , i install the appimage available in official etcher site and now is working. The problem is in
1.19.16. The version in the official site is1.18.11. I think the latest stable version is1.18.11. So this version we should use.Thanks!!! etcher-bin is worked for me
OS: Fedora 39 pkg: balena-etcher-1.19.4-1.x86_64.rpm
Looking at the inspector the error is thrown in the
source-selectorcomponent here… https://github.com/balena-io/etcher/blob/v1.19.4/lib/gui/app/components/source-selector/source-selector.tsx#L425requestMetadatawhich is imported fromappis stillundefined.https://github.com/balena-io/etcher/blob/v1.19.4/lib/gui/app/app.ts#L139-L157
Since
requestMetadatais initially defined asundefinedthere needs to be an additional check inselectSourceto know thatrequestMetadatahas been defined. It appears the only way to know this is listening for the emittedscanevent, but I didn’t deep dive on a solution.Of course, developers clearly know about this, but decide not to work on it, there are more important things. New version has been released just 4 days ago. Fixing what? Build-in spyware analytics. I am done with this program.
Had to revert to 1.18.11 on Windows. Same error on 1.19+ with admin rights or not. Couldn’t open ANY ISO.
Not fixed since 2023? I am still experiencing this in 2025. Reverted back to old version and magically it works, WITHOUT ADMINISTRATOR.
This worked for me, too! In addition, I started the balenaEtcher using ‘Run as Administrator.’ Since then, I can also start the program in normal mode, and it works without errors.
Using newest version on windows, downgrading to 1.18.11 fixes it for me
Unsure if this was the actual fix, but i’m on MacOS Sequoia and right clicking the application, get info and changing the read only permissions to read write for all users and drives worked for me.
For me, simply running balenaEtcher-1.19.21 as Administrator solved the problem.
Did a little more investigation on the AppImage. What’s happening here is a bit different. In lib/gui/app/modules/api.ts there is a bit of code that tries to spawn the
etcher-utilprogram. From what I can tell, there two copies of this utility - one unprivileged that scans the source image, and a privileged one that handles writing to the target device.In the current AppImage, spawning either of these instances fails. Digging a bit further into the code, there is this routine that tries to determine the location of the
etcher-utilprogram:This code is failing whenever it’s in an AppImage. It’s building up a command line that fails to execute, or at least fails to do the correct thing and start the utility. I was able to work around the first instance of this error for the unprivileged access by passing in the flag that indicates whether the child process needs to be privileged or not so that for the unprivileged helper it just returns the standard
entryPointwhich results in correctly running the helper from the currently mounted AppImage. This allows the GUI to properly read the source image and allows you to select the target device.However, it still fails when it gets to actually writing to the target device, because at that point (as the comment above correctly notes) the mounted AppImage is no longer available to the
rootaccount, so it needs to spawn and mount a new copy of the AppImage.I haven’t figured out why exactly this is failing as I’m not exactly a JavaScript developer myself, and I don’t fully understand what processes the
-e "require(...)"portion of the arguments above. There are a lot of layers here, as the call goes through:And I’m not really sure which step in the process is responsible for deciding to run
etcher-utilinstead of running the GUI when it spawns that child process. But something in that chain is definitely failing to do the correct thing.I’ll keep poking at it, but hopefully this helps someone more familiar with the code narrow in on the issue.
I took a really quick look at the AppImage, which is also failing for me on Fedora Workstation 40. It looks like it’s a different issue that’s causing the same error message. Running the .AppImage file directly fails with the same error message. But extracting the image with
./balenaEtcher-1.19.22-x64.AppImage --appimage-extractthen running the resulting./squashfs-root/AppRunworks fine. And inspecting the extracted files, it looks like theetcher-utilin the AppImage is not corrupted like the one in the RPM was.I might try to take a deeper look at it later. Sounds like a good opportunity to learn how AppImages work under the hood. 😃
Win10 user here - This solution also worked for me.
I had same issue on Win 10. Even running as Administrator does not work as others mentioned here.
When I run with –no-sandbox option, it resolved the issue. So, just run cmd on the directory where you have Etcher installed (it can be under <user>/AppData/Local/balena_etcher - if not there, right click on the balenaEtcher in start menu and select “Open file location” - if it shows just shortcut, open file location of the shortcut until you see balena_etcher.exe)
Then start it with the option, e.g.: C:\Users<the user>\AppData\Local\balena_etcher> balenaFetcher.exe --no-sandbox
Old version 1.18.11 worked for me. @aethernet Can we rollback recent changes from 1.19.11 to 1.18 ? This is a regression blocker to use it.
I dunno if this was a total fluke. But I jumped out and reran as Administrator and the error is gone. Win 10. No idea if this will work for you. Im installing Ubuntu Studio and I was getting this error. I backed out of the install then tried again ad admin,…why I wasnt before, who knows. All I know if, it worked. Was is loggin in as admin or a fluke…I cant tell, But hopefully it works for you.
Same issue, but I tried downloading a previous version (1.18.1), and it worked!
Experienced this issue myself too with balenaEtcher 1.19.21 on Windows 10 Attempting to flash a Ubuntu ISO. The error message appeared after a short delay after navigating to the .iso file. Funnily enough after closing and re opening the program it worked without issue !
Newest didnt work for me on Arch and was giving the same error. Using the v1.18.11 appimage as suggested above worked.
Got the same error on Windows 10 and balenaEtcher 1.19.21(that’s on the official website). Downloaded balenaEtcher 1.18.11 on sourceforge and it worked.
Same issue with windows 11 version 19.19
wtf, this is still not fixed?
Getting the same on Fedora 39 with version v1.19.3. Tried both RPM and AppImage formats. Same result. -1706048290684.log
I use archlinux ,balenaEtcher-1.18.8-x64.AppImage can use
I just encountered the same problem with v2.1.2 on Ubuntu, I rolled back to v1.18.12 (just prior to where @wegank said it didn’t work) and that resolved the issue.
You’ve got to be kidding me… This comment helped me fix my issue. I’ve been trying to flash Linux Mint to a USB and, although it worked fine for flashing Elementary OS to a USB, I was getting this same error with Linux Mint.
In balena Etcher I went to Settings and enabled “Anonymously report errors to balena.io” and when I tried flashing the iso again it worked…
Same on Windows 10
Recently there is so many user is suffering this matter. I guess balena is not fixing issue. As alternate, raseberry Pi imager is working fine. You should select all as manul things rather than pre-defined. 😃
Still getting this error with the 2.1.13 .deb installed on Ubuntu 24.04 and the Tuxedo OS ISO from https://os.tuxedocomputers.com/
This is so f’in annoying after being unable to run the .appimage, WTF is so complicated about opening an .iso file?! And why did opening it work after I cd’ed to
/usr/lib/balena-etcherand ran./balena-etcherfrom there?Can you guys switch to Go, which generates cross-distro single-file executables without this Electron shit?
What do you need a fancy UI for anyway? Select a file and click a button to flash it?!
Saturday June 7 2025
What the hell, Etcher. Why does this happen !!??
Just had the issue with v2.1.2 on Windows 11. It worked yesterday when I used it for the first time with the Ubuntu latest LTS iso. It failed a couple times today with Ubuntu 25.04 iso. But then I ran it as administrator and it worked.
I used Raspberry Pi, as suggested by someone in the thread. It turned out to be easy, quick, and successful.
On Thu, Apr 10, 2025 at 1:50 AM spaceXrace @.***> wrote:
I even managed to track down the spot in the code where it’s failing, and described why. I just don’t know enough about Electron and JavaScript to fix it myself. I was really hoping one of the devs would at least pick it up from there, but…
And in that time this issue has accumulated over 200 comments, which means that it must be a reasonably widespread problem. (EDIT: as well as there also being multiple duplicate reports of this issue)
I’m obviously biased, but I think that Raspberry Pi Imager works pretty well. Although do note that there’s some features that Etcher has that Imager doesn’t; and likewise there’s some features that Imager has that Etcher doesn’t. 💾
its random, if i close and open the app like 5 times it fixes
You may need to run it as Administrator.
I had the problem on windows. running belenaEtcher as admin helped.
I ran into this issue on a Raspberry Pi 5 and could resolve it with this:
Maybe this helps some other poor soul.
guys. stahp. this isn’t a windows-related thread. linux. 1.18.13+ appimage. we already know about the windows fix. kthxbye. ❤️
I was receiving the same error - v1.19.25 and ubuntu 24.04.1 amd64 iso Windows 11 10.0.22631 Build 22631 The error occurred when running from downloads or trying to use the iso from downloads folder I created a folder in the root of C:\ , excluded folder from windows defender (this may or may not have been necessary, just including for completeness)
Subsequently, this has worked fine (twice)
Just adding in case this helps anybody out.
I tested the latest AppImage version, balenaEtcher-1.19.25-x64.AppImage, on Kubuntu 22.04.5. With balenaEtcher-1.19.25-x64.AppImage, I still get “Error: (0, h.requestMetadata) is not a function”. balenaEtcher-1.18.11-x64.AppImage still works OK.
I had the error with v1.19.21 with the file
open-super-clone-live_24.08.02_amd64.isobut I downloaded the pre-release v1.19.22 and the error went awayUm … @alexrem1978 this GitHub issue is for the Linux AppImage version, not Windows
Everyone, use an older version of the AppImage release like Version 1.13.0 found on this release page:
Same error opening source on LMDE6 with balenaEtcher-1.19.21-x64.AppImage version. I’ve fixed downgrading to last running version for me balenaEtcher-1.18.12-x64.AppImage. I’ve tried versions after 18.1.12 and same error.
can confirm on windows that close then re-open the app work
Well, it might help someone else troubleshoot it further, so… All I did was clone the repo, install the dev dependencies (I know enough about JavaScript that
npm cishould install everything) then checked in package.json to see thatnpm run makewill run electron-forge to build all the software.From there, I just modified the code to add extra debug logs where needed (use CTRL-SHIFT-I to see the logs while Etcher is running), then by reading the code, a bit of trial and error, and unpacking the resulting AppImage, I narrowed in on the areas that are failing. Some of the earlier comments in this thread and others also helped a bit.
I’m confident that etcher-util is not starting when running in the AppImage. I just still don’t understand what’s supposed to respond to those command-line parameters to make it run. As far as I can tell, nothing processes the command-line arguments, unless there’s some magic in Electron or JavaScript in general that I don’t fully understand.
I did run into the same problem on MacOS Monterey 12.6.5 but after reloading the program, I was able to flash without issues. I had Etcher on this machine in the past, always worked, deleted it at some point, then reinstalled. For reference
I did a bunch of investigation, and found root cause of the problem, at least for the .RPM packages. By default,
rpmbuildwill strip executables to remove debug symbols and other unnecessary data from the executables before bundling them into the .rpm package. However, because of howetcher-utilis compiled by electron, there is a bunch of necessary JavaScript code embedded in the executable that needs to be there. rpmbuild is erroneously removing the JavaScript code from this file, causing it to fail. This in turn causes the front-end to produce theError: (0 , h.requestMetadata) is not a functionmessage whenetcher-utilfails to start properly.I submitted PR #4304 to work around the issue, at least for RPM builds. Ideally we could pass a custom .spec file into rpmbuild, but this is currently not possible. So the PR just disables the
stripcommand by overriding it via an rpm macro.A better solution would be to add a custom .spec file to the repo, then pass that into
electron-installer-redhatvia the newoptions.specTemplateparameter. That option has been added in https://github.com/electron-userland/electron-installer-redhat/commit/ab6694f1aa9f19f44dd07a4aae11918b7cfbc59c but the feature has not yet been included in the latest release (currently v3.4.0).I haven’t had a chance to look into the AppImage yet, but it could be a similar issue.
Just encountered the same issue on Clear Linux OS, version 42210.
I ran into this error with both
v1.19.21andv1.19.22of the AppImage. As others here have mentioned,v1.18.12works fine on this same OS.Running into the same issue with balena-etcher-1.19.22-1.x86_64.rpm on Fedora Workstation 40. Downloading the .ZIP version for Linux appears to work properly. Digging a little further:
The
balenaEtcherfiles are symlinks, so not surprised there are errors. Ignoring those, theetcher-utilfile appears to be different. Doing a really quick check of file sizes:The etcher-util included in the RPM package is significantly smaller. Running the
etcher-utildirectly:Looks like the version of etcher-util that’s getting bundled with the .RPM package is corrupted somehow. So I tried:
And now the version that was installed via RPM is working properly with the “fixed” version of etcher-util.
Not sure what’s different, but I suspect something with the .rpm (and maybe .deb?) build is failing or causing corruption, where the version in the .zip file is not.
Linux Mint 21.3 (based on Ubuntu 22.04)
Same error
with both the native deb installer and AppImage version 1.19.21. Downgrading to
balenaEtcher-1.18.11-x64.AppImageworks like a charm. Balena, get your shit together!The google search AI says:
Which is probably a misleading statement.
Same problem on Ubuntu 22.04.4 LTS and AppImage.
Running on 1.18.11 worked flawlessly.
I downgraded to 1.18.11 to overcome the issue.
That worked. Had the same issue with win10 and newest version from Website. Removing USB flash and restarting program fixed issue while loading image. Thank you!
Till the image is loading very long, a loading spinner would be nice to be sure the program didn’t crashed
balenaEtcher-1.19.21-x64.AppImage on Ubuntu 20.04, same issue
1.18.11 works
Hello, Issue still reproduces running balenaEtcher-1.19.21.Setup.exe on windows 10 and trying to write image for Ubuntu ubuntu-24.04-desktop-amd64.iso Was able to run balenaEtcher-Setup-1.18.11.exe in the same conditions, and it run fine.
Same on Ubuntu 22.04 with balenaEtcher-1.19.21-x64.AppImage.
Having same issue with balenaEtcher-1.19.21-x64.AppImage on Ubuntu 20.04.
balenaEtcher-1.18.11-x64.AppImage worked.
This worked for me as well, installing Lakka for an RG351M on Fedora 40 Workstation (x64).
The AppImage and the RPM were NOT working.
This walkthrough also worked on Windows (Bin path:
%LOCALAPPDATA%/balena_etcher/app-(version)/BalenaEtcher.exe). I had issue when loading Fedora Workspace 40 x64 image file on Windows 11 Home 23H2.this is a functional workaround in mint 21.3 cinn 6.0.4 you’re a lifesaver, thanks man!!!
Hey guys,
I think I got the problem. Will take a bit to solve it. In the meantime the latest .zip works fine.
thank you it solved mine i was trying booting nvidia jetson nano and it worked for me
still occuring for me with linux mint with 1.19.21 too. Previous build without pre-release label that other’s mentioned (1.18.11) works fine.
Confirming this fix worked for me - Windows 10 Pro, version 1.19.21
This solved it for me on Manjaro.
Can we close this? @wegank
Having this issue now on MacOS
@ShalokShalom I might base my fork on the 1.18.x branch instead.
@aethernet @dfunckt @klutchell Is someone going to look at this? I’ve been waiting 2 months now. It prevents making working builds on Linux and Windows. I have a fork that still supports Windows 7, and this is blocking me from doing any more work on it. pkg or yao-pkg is not bundling all the native modules into etcher-util properly. I say yao-pkg because I tried @aethernet two patches related to this (and updating to Node 20, with no luck). Running pkg with --debug, the only thing I see is it complains about no prebuilt binaries. But shouldn’t it be building from source with electron-rebuild anyway?
Hello, same error here:
Same issue here on ElementaryOS and Zorin OS with balenaEtcher-1.19.5-x64.AppImage. Confirmed that balenaEtcher-1.18.11-x64.AppImage worked on both systems.
Same on Arch on both x11 and wayland, installed with yay from aur (since people above were talking abt wayland)
AppImage works fine
Thanks for the reports guys. This basically means the sub-process
etcher-utilscould not be spawned properly (or is not yet ready). There might be more infos in the debug console. Can you check what it says ( Ctrl + Shift + I should open it) ?This issue does not occur on the appimage version of Etcher
Same issue with balena-etcher-1.19.3-1.x86_64.rpm on Fedora 39
I’m getting this with version 1.18.14 on Garuda.