Latest Windows 11 update erased my Solus boot entry.

juampiursic

Hey guys. This happened. I just updated Windows 11 cause it said it had an update and with all the Ryzen stuff, that is underperforming on W11, I update everything that it gives me. Now I don't have the boot entry of Solus, really don't know what to do.

I have Linux in one drive and Windows in another drive, so they both got an entry at boot, I F8 and select whenever I need one or the other and now only Windows appears.

WetGeek

juampiursic Now I don't have the boot entry of Solus

I suspect that Windows has defaulted to "secure boot." and that may be the root cause of your problem. Each new version of Windows seems to make it harder and harder to use any other system on the machine.

murbert

I suspect it is because you had 2 partitions flagged as 'boot, esp'. One on each drive for it's respective OS. Windows likely hijacked the Linux boot partition.

In GParted, I right click on my boot partitions, select manage flags, then check msftdata. This way no other OS will think the EFI partition is theirs. Sometimes the Windows update will fail because of this. When this happens I temporarily switch it back to the boot flag on the Windows drive, complete the update, then switch it back.
I like Solus but dual booting is harder than it should be.

WetGeek

murbert I like Solus but dual booting is harder than it should be.

You're almost certainly right about that, and I didn't even think of it.

I run both Solus and Windows on my main laptop and on a desktop workstation, but in both cases Windows 10 is in a VM. I avoid any issues with dual booting that way. I recommend running the most important OS as the host (e.g., some may need Windows for work) and the other OS as a VM.

In my case both machines use Solus as the host, but people's needs vary.

tomscharbach

murbert I like Solus but dual booting is harder than it should be.

I agree, although the Solus boot manager is a lot easier to deal with than grub, which is akin to the Mushroom That Ate New Jersey, insistent on completely taking over the boot process.

I used dual-boot, dual-drive in the past with some success, by installing the two operating systems entirely independently -- that is, installing Windows having the Windows drive (but not the Solus drive) in the computer, and then reversing the process, installing Solus having the Solus drive (but not the Windows drive) in the computer, and then putting both drives in the computer. That effectively gave me two entirely independent computers, each drive with its own boot partition, and the two drives not seeing each other. That was stable, but required an F12 boot every time, and careful attention when rebooting because BIOS has to be set up so that one is primary.

At this point, I run Windows on one computer, and Solus on another. It is a lot simpler.

juampiursic

Hi guys! Solved it with EasyUEFI, I just added a new boot entry, entered the path to systemd-boot and it worked.

It's like murbert said, boot partitions on each drive but Windows apparently hijacked the Linux one. I found dual-booting having 2 drives really easy, never ever had an issue like that in the last 3/4 years, not even upgrading to Windows 11 from Windows 10 erased the Linux boot entry.

algent

tomscharbach That worked was stable, but required an F12 boot every time

I do the same, 2 different SSD drives for two systems. But I have set Linux drive as primary drive because there I can manage which system to boot first.