Writing ISO to Usb no boot

Jason5 Yes I written the ISO file using Multi Writer as I normally do for every ISO

Hmmm ... I asked for more details, because without knowing, I thought you might just be copying the file to the USB drive, and I didn't know whether you were trying to boot the "live" session or the installed OS.

I've used multiwriter successfully in the past, but there are other good options. What I now use most of the time is Balena Etcher. Etcher is available in the Solus repository, and it's trivial to use. You just select the .ISO file and select what device you want it written to, and then provide your password for sudo. Perhaps your copy of multiwriter has become corrupted somehow? Maybe a flawed update?

One thing to be aware of is that the password dialog may appear behind the Etcher window, so you may need to move the small Etcher window out of the way in order to enter your password and allow Etcher to continue. It does that on my Plasma laptop, but that might not happen with Budgie. I thought I'd mention it, just in case it does.

If using a different tool to write the .ISO to your USB drive doesn't solve the problem, then I'm out of ideas. I've never created a Solus USB drive with Etcher that wouldn't boot, though.

Jason5

Then the most reasonable cause is that the Solus Budgie .ISO file is corrupted, perhaps by a download that didn't quite work as it should. If I were you, I'd download another copy from https://getsol.us and install that new copy to your USB drive and try again.

There's also the slight possibility that your USB drive is defective, but that's unlikely. Did you let Etcher verify the copy you made? If you did, and the verification passed, that's a pretty good indication that the .ISO file itself is corrupted. The verification process just reads back what it wrote and compares it with the file it was told to write.

I am having the exact same issue with trying to install Solus Budgie.

First attempt: Used Etcher to write the ISO to the USB drive. Secure Boot disabled. Verified shasum, did the usual things I've done to install a distro.

Second attempt: Redownloaded files. Doublechecked signature and shasum. Used Gnome MultiWriter. Tried enabling and disabling Secure Boot in case that was somehow the issue, even though the error message seemed unrelated.

Third attempt underway, using the torrent download and the command line option for writing to the USB (as explained in the quickstart guide at getsol.us). Same result.

Finally tried to download etc the Plasma edition to see if that works and it's just something weird with Budgie, but no -- still getting

Invalid Image
Failed to read Header: Unsupported
Failed to load Image: Unsupported
Start_image() returned Unsupported

So at this point I'm not sure what to do to troubleshoot, other than write some different distro ISO to the stick and make sure it's not a problem with my hardware.

Jason5

Jason5 You downloaded the Solus 4.4 budgies today and tried?

Not today, no. But I have no reason to believe that they were changed recently. I follow the Matrix conversations by the Solus team, because I'm learning to be a package maintainer, and I've heard no such chatter.

I'm not sure about the old motherboards, but I suppose that's a possibility. At the very least, it does sound like a local problem, because there are thousands of people who've downloaded and installed Solus Budgie, presumably without an issue like this.

Are you currently running Budgie 4.3 on your computer? Do you realize that if you've updated it regularly, you're already on 4.4?

murbert I think I also installed this time with Ventoy. The problem is that not always/not for all it works with each Ventoy setup/setup try.

BTW, and this is not a recommendation but just something I think I used,
I personally chose to later exFAT format it (Ventoy partition - the place you put bootable ISO in for booting, and BTW also chose so for the other, optional, storage partion I added, for some reason,) before I added the image, and probably it was GPT (and secure boot support) this time and not MBR, too (as using UEFI and GPT) though unsure, but each with one's own choices and style and for each one it might work different. For some it doesn't work.

On Linux, if it doesn't work or if people chose other way, they may use Gnome Multiwriter (this might be limited to up to 32GB USB keys though) or dd but as instructed on the help center, or in any other declared supported app/software mentioned there. https://help.getsol.us/docs/user/quick-start/installation/#usb

Some said etcher works as well and I think I "tested" it myself recently. (Yes I installed twice recently for some reasons. A fast app, at least usually in my experience works (no promise), I like it, but yes, I like Ventoy which has some nice benefits and which I find to be very useful for many purposes and also recycling/easily updating ISO versions in the way murbert said by just replacing a file.)

What is your hardware?
Its not a bad iso I think its telling you it doesnt like something about your setup
Maybe crappy usb (try another)

[deleted] I think I also installed this time with Ventoy. The problem is that not always/not for all it works with each Ventoy setup/setup try.

You are correct. I tried a lot of bare metal distros since January and always 1 out 10 needed to be burned on to USB. But that's still a 90% success rate for Ventoy....including Solus Budgie which I reinstalled recently. @murbert is right, this will cure his problem.
It won't solve the mystery of the Wiggy Hardware but it will let him install Solus.
............maybe he will need to setup the Ventoy program on a different USB though.
edit/sp