SteamDeck-EFI-script VS SteamDeck-Clover-dualboot

Hey! I've tried asking before, hope you won't mind giving a response this time! Is there any chance you might work on a GUI tool for the steps needed in your repo here: https://github.com/ryanrudolfoba/SteamDeck-EFI-script?

https://github.com/ryanrudolfoba/SteamDeck-EFI-script it can fix the issue after windows update. and simple.

This script will make it so that you will boot to SteamOS by default, and no it does not affect the start time.

If you just want steamOS to boot first, use this

You can, of course. For ease of use though, you I also suggest you configure a boot loader: https://github.com/ryanrudolfoba/SteamDeck-Clover-dualboot

I use Clover for dual-boot (SteamOS 3.5 and Windows 10) - https://github.com/ryanrudolfoba/SteamDeck-Clover-dualboot (release 15.10.2023) And I noticed that SteamOS loads much slower due to Clover - ~30 seconds to even over one minute. Windows 10 starts immediately. If I boot SteamOS directly from UEFI (Vol - + power button), the system starts almost immediately.

git clone https://github.com/ryanrudolfoba/SteamDeck-Clover-dualboot

You may also find useful this project. It's a preconfigured Clover that can automatically reinstall itself after system upgrades. It automatically detects different OS on different drives and some OS are already preconfigured with beautiful icons. Works flawlessly for me, tested with Ventoy USB drive with multiple images and with Tails (Deck is an amazing device for anonymous Internet access!) on SDCard. The only things I adjusted were menu timeout and theme. I'm not sure if it's better or worse compared to refind.

I use SteamDeck-Clover-dualboot to manage a dual boot. Updates to either SteamOS or Windows will often mess with the boot priority, so installing this script on the SteamOS side tends to help. When one OS “takes over,” manually booting into SteamOS fixes it right up.