live-usb-maker tool now available as an AppImage

For those non-MX or non-antiX linux users who might need to write iso images to USB sticks, we now have the joint antiX/MX live-usb-maker tool available as an AppImage. The tool has been tested on Manjaro, Debian buster and stretch, arch, Porteus, gentoo, xubuntu and ubuntu. You can use it to make a “disc-on-a-stick” similar to etcher, and if you happen to be making a antiX/MX family live-usb, you can use the “full-featured” mode as well to be able to access our persistence features right on the first boot of your live-usb!

Many thanks to all the testers and to adrian (gui) & BitJam (live-usb-maker backend) for their help in getting the AppImage running.

The 64bit-only AppImage (sorry , no 32 bit) is available here:

Download the archive file containing the AppImage, extract to a folder, enter that folder, and use

sudo ./live-usb-maker-qt-19.11.02.x86_64.AppImage

to run the AppImage.

There is a known issue in that the help button does not work from the AppImage. An online version of the help is available here:

31 thoughts on “live-usb-maker tool now available as an AppImage”

    • quote: Hmm not very beginner or user friendly? Also the appimage has to be chmodded right? Could there be a Flatpak rather?

      That depends on your perspective. the AppImage is meant to run on the widest array of systems possible, requires no preinstalled daemons like flatpak or snaps, and doesn’t even require gksu or pkexec to be present for authentication. Even if a user was a hardcore debian user with no sudo available, the appimage can still be run by the root user as well.

      as for needing to chmod, usually its true that AppImages require that. However, in this case, the AppImage executable bit is preserved inside the archive file that the AppImage is packaged in. I figure its far more likely a that even a new linux user will be able to extract from an archive than know about the necessity to chmod an AppImage.

      • Sorry, it’s just too complicated. It is evident even in ur long reply! The developers often cannot see the point of view of a regular “normal” user.

        For instance Snaps are one click installs. The way it should be. Really! Appreciate MX and your work full on though!

        • With AppImage you don’t have to install (I suppose Snap must be installed, as well as Flatpak) – just run with one click and use.

          It is like portable version for some programs in Windows.

          When I try new software or newer versions of programs I prefer AppImage files – it’s quick and easy, download and try – if I don’t like it, I just delete it, no need for uninstalling.

        • Seems like pretty basic stuff, not that complex. I run MX at home and really like it but have been running Debian 10.1.0 at work so that I’m forced to learn. Don’t be afraid of the command line interface. It’s very powerful! Thanks guys for all of the great work.

        • Trish, as a Linux (and MX Linux) newbie, I can confirm your concern for folks like me! I have MX Linux on a smaller laptop that benefits from the smaller MX footprint and the MX Live USB Maker tool is a great one to have. But I also have Linux Mint installed on another laptop that has enough RAM to use the Cinnamon DE and I was hoping that the availability of this tool would make it easy to create the same for other distros. I downloaded the file, extracted it…and then when I double-clicked on that I got “Must be run as root.” Huh? That’s probably very basic stuff for a lot of Linux users….probably easy to accomplish via some sequence of commands in Terminal. But it’s enough to dissuade me.

          • You need root access to write to the partitions on any device connected by design on linux. Even if it was a snap or flatpak you wuld still need to entero your root/sudo password or the software would nota work.

          • For ten years I follow command line instructions like a cookbook. I get a distro of linux running. I eventually break it when I try to update something (most recently NVIDIA drivers) and then the command line is a foreign language to me again. I shudder at tar balls. I don’t know where to put them and how to open them. There is always some strange magic command with xyz and I have no understanding on why I’m being instructed to type the incantations mentioned. And yet through all of this, I still greatly prefer Linux to any other OS.

          • here’s the thing (coming from a near newbie) — it’s not too much to ask a total Linux newbie to explore enough to know what the message “Must be run as root” means, and, how to change from user to root. It’s so fundamental to the logic and systematic of Linux. I’ll liken it to having learn that you press the start button on many a newer, keyless car, with the brake petal depressed; vs inserting a key in the older-style ignitions, turning it, but with the car in Park in most cases. I conclude in jest with the slightest of puns: get with the program. In this case learn at the very least su and sudo … there are many short simple videos explaining these very basics

  1. Good idea, as AFAIK ubuntu usb installer lost a lot of functionality, so users can judge firsthand how much mx is ahead in terms of live/installing tools.

    • yep, its baked right in. just make the live usb with our live-usb-maker tool or use something like rufus. things like dd and etcher make a readonly device, which obviously don’t work with persistence. I just finished a video series on the live features available in MX (and antiX) on my youtube channel

  2. Hi, but this fails like this:

    ssudo ./live-usb-maker-qt-19.11.02.x86_64.AppImage
    ./live-usb-maker-qt-19.11.02.x86_64.AppImage: 1: ./live-usb-maker-qt-19.11.02.x86_64.AppImage: Syntax error: “(” unexpected

  3. I create this tool in Kde Neon and when i try to execute i get this error : You may run this as root and i can;t find a way to do that. Any help?

    • sometimes. persistence is set up by the live system on first boot, so as long as your file system is writable, you should be OK. unetbootin depends on the host system’s sysVinit, so as long as your sysVinit is new enough, it should work.

  4. Seems a shame that you need to start a GUI from the command line. Is it not possible to make it prompt for the SU password like the built in app?

  5. I used YUMI (Win7 1GBram ASUS 1005PE)
    to put MX (latest 19.1) on 128G SD card.
    Boots ok. *HOW* (pref cli) do I *add* persistence
    (to the LIVE RUNNING SD card)??? TiA!

  6. Kto te bzdury pisze? Jak wykonuje się te komendy i polecenia, to nic nie działa. A mówią, że Linux jest przyjazny, prosty i nie wymaga dużo zasobów sprzętowych. Śmiech na sali. Pozdrawiam

    • I write this nonsense. If it doesn’t work for you, sorry. appimages have turned out to not be quite as universal as they advertise. they still expect some set of libraries to be on the host system.

      but there have been a lot of reports of success, so not a total nonsense anyway.

  7. “Must be run as root.” ? HOW? probably very basic stuff for a lot of Linux users….probably easy to accomplish via some sequence of commands in Terminal. But it’s enough to dissuade me.


Leave a Comment

Do NOT follow this link or you will be banned from the site!