Live user password?

Staudey Also the username is live, and no password.

The user name is not changeable ... I can't set it to live. And if I don't provide a password, it just displays the login page again.

elfprince Tried live ?

This is what I've gotten with every suggestion so far, including live.

Brucehankins I remember seeing an old thread about an issue with the Mate 4.3 iso, maybe try a 4.2 iso?

The last time I needed to create these VMs, it was the Solus 4.3 GNOME ISO that wouldn't work, but I was able to use the 4.2 ISO to install it. This time, I was unable to click the [Next] button for the installer, but I'm going to try that one more time. I think I might be able to get to the top border of that button, and that might work.

I'm giving up on this for now. Maybe the new ISOs will work, when they're available.

I've created dozens of VMs using VirtualBox, and I've had the four Solus VMs available for years. This time, I've only been able to create a Budgie VM and a Plasma VM. No luck at all with GNOME or MATE.

SOLUS TEAM, PLEASE NOTICE:
Anyone working with the installer for the new ISOs should be aware that clicking the [Reboot] button at the end of an installation causes problems. I think it's because the installer might still have some data to flush to the file system, and clicking [Reboot] doesn't allow that to happen.

I've known for a long time that the way to avoid those problems is to close the installer, and shut down from the Live session. Then remove the ISO. When the VM is then started, it will boot to the new OS, not the Live session. Maybe this could be fixed in the new ISOs.

tomscharbach This is a VM issue.

Interesting. The VM is executing the same code, with the same instructions in the same order, but doing something different. How does the code know that it's being run on a VM? Just chalking it up to magic for now. Sorry for the bother.

tomscharbach I don't think that happens if the ISO remains mounted.

If the ISO remains mounted, the reboot simply restarts the Live session. That's happened to me as well. Then I shut it down, remove the ISO from the virtual CD drive, and boot again to the new OS. I've used that method in the past, but usually I just shut down the installer when it's done, and then close the VM and remove the ISO.

For two days now, I've been struggling to rebuild my laptop (which has gone well, but it's a really big job). tried to rebuild five VMs with limited success (Budgie, Plasma and Windows 10 were no problem at all), and had various things that always worked before fail completely this time. If I've annoyed anyone today with my lousy temperament, my apologies.

I've always kept four Solus VMs handy, updating them each week, but this time I was totally unable to create GNOME and MATE VMs. I spent hours trying. I finally gave up for today, because Windows 10 was starting to look very good in comparison. (The Win 10 VM built with absolutely no problems at all, and I've already used it to read a chapter in my current Nook book.)

I'm thinking my outlook tomorrow might be a bit brighter, but I'm unlikely to try to rescue those two failed VMs for a few days, at least. I need to take a break for a while. The laptop, at least, is fully healthy again, with a sparkling new installation of Solus Plasma on it. In fact, it's better than it was.