As announced in our Solus 4.4 blog post we are deprecating our MATE edition and so this issue will not be addressed.

@jedibrooker, is this still an issue? It has been a long time since there was an update to this task, and there have been many updates since this issue was opened.

Tracked at https://github.com/getsolus/solus-installer/issues/13

While Calamares doesn't strip leading/trailing spaces, it does actually tell you very clearly what's wrong. So this will indeed be resolved by switching to Calamares.

Calamares (I believe) can do this, it probably just has to be set up to do so. Something to look in to down the road.

Closing per request on the forums. Appears to be resolved.

In T10563#202105, @stalebrim wrote:

Did you format the disk as GPT?

Thanks for the detailed bug report. Since we are retiring os-installer, this won't be fixed for that. We will keep this issue in mind for its replacement.

What I am saying and have done is to select the Fat 32 partition, normally the ESP or EFI boot partition on the Windows disk (in this case), click on the right with the mouse, go to manage flags and untick the boot flag. It will untick the esp flag as well. Then, do the Solus install. Once it's done, you can reset the boot flag of the windows partition.
It will go back to boot and esp. It hasn't made any trouble on all my partition (Windows, OpenBsd, Mint, Solus and Fedora). It's just the time of the install. I found it here : https://discuss.getsol.us/d/4467-installer-not-seeing-new-efi-boot-partition

In T10324#201398, @Foid wrote:

Hi,
I went into the same problem (I have around 10 disks !!). On each ESP partition (boot Fat 32 parttion), with Gparted (didn't work with Kdedisk manager (can't remember the exact name)), I unticked flag boot (it comes with esp), that changed then to msftdata with the manage flags menu.
If your disk is empty, then on install, it will ask you if you want to create an Esp partition on the disk you expect. I actually found this solution on the forum (can't find it again, but it's there).
I would say on your case, you untick the boot flag of the windows partition, and bob's your uncle. (by the way, you can install Gparted with the live iso, it works fine).

Hi,
I went into the same problem (I have around 10 disks !!). On each ESP partition (boot Fat 32 parttion), with Gparted (didn't work with Kdedisk manager (can't remember the exact name)), I unticked flag boot (it comes with esp), that changed then to msftdata with the manage flags menu.
If your disk is empty, then on install, it will ask you if you want to create an Esp partition on the disk you expect. I actually found this solution on the forum (can't find it again, but it's there).
I would say on your case, you untick the boot flag of the windows partition, and bob's your uncle. (by the way, you can install Gparted with the live iso, it works fine).

Ran into this issue as well, instead of risking breaking dual booting between solus and manjaro, I popped my laptop open and removed my Manjaro drive while installing.

For me workaround is using gparted and creating new partitions. Also you need to untick "boot" flag from windows EFI partition and mark newly created Fat32 partition flak as "boot". After that installer will see the new EFI partition.

Have you tried manual partitioning? I found once I manually created /, swap and boot partitions like in the helpcenter docs, rebooted, it detected the new partition nicely.
https://getsol.us/articles/installation/disks/en/

installer issues need to be reported on github https://github.com/getsolus/solus-installer

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/29

Closing due to lack of response in over 30 days. Please reopen if you have more information to add.

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/15

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/28

Closing due to lack of response in over 30 days

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/27

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/26

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/24

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/23

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/22

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/21

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/20

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/19

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/18

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/17

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/16

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/16

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/16

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/15

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/13

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/14

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/13

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/12

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/11

Moved to GitHub for the new installer https://github.com/getsolus/solus-installer/issues/11