• @[email protected]
    29•1 year ago
    • install windows
    • adjust main partition so you have space for Linux
    • install linux, during install create anither efi partition, and root partition.
    • linux probes foreign OS (some distros might not) and creates a chainloader entry from your new EFI to Windows EFI
    • set BIOS to boot from linux EFI

    Windows never knows the other partition exists and leaves it intact.

      • @[email protected]
        10•1 year ago

        Don’t even have to do that. Install windows first, then install Linux with refind bootloader on preferably a separate disk. Done

        • @[email protected]
          1•1 year ago

          You do need a separate EFI, even though linux finds EFI, otherwise windows update trashes it randomly and why the meme we see here exists, with separate EFI windows doesn’t know about it. You can shutdown windows mid update and boot linux, then reboot back to windows and update will continue. Siloed System

            • @[email protected]
              3•1 year ago

              It will, thats why that meme exists.

              Not during typically reboots, but when some windows update or autofile repair happens it thinks it is the only OS on that partition and does what it likes.

                • @[email protected]
                  1•1 year ago

                  Then you have been lucky, because most peoples experience with grub EFI on Windows partition is windows will eventually scrub it.

      • @[email protected]
        2•1 year ago

        Yes. When you install Linux it will auto detect the Windows EFI partition and put boot stuff there by default, but then windows comes along and will randomly trash that setup. So during install don’t go with the suggested option, instead use the partitioning tool to creat another small EFI boot partition elswhere on disk, leaving Windows EFI and OS paetitions as is. Also create your root and home partition(s). Install to those partitions, then Linux should prompt for Probe Foreign OS and add a chainloader entry to your grub menu. This entry, when selected, points grub to windows EFI partition ID and hands off the boot process to Windows. Windows is unaware it has been chainloaded. As long as you set BIOS to load directly from the LINUX EFI entry then you will boot to Grub with Linux/Windows Dual option…But technically it is not a true Dual Boot, it is a sequential boot I guess. I have had this for 7 years on same install and boot between W10 and Linux daily. Windows has never touched my Linux EFI.

          • @[email protected]
            1•1 year ago

            I responded how to via another comment, but wanted to mention that you may have a chainload to Windows already with your dual boot, but the main point was using two EFI partitions and chainloading to the other one, so Windows isn’t ever in charge of files in your linux boot partition

          • @[email protected]
            1•1 year ago

            For something like OpenSUSE you go into YAST2-GUI and click the probe foreign OS and then it asks you if you want Windows or Linux as the default boot. But to do it manually you add a menu entry to /boot/grub2/custom.cfg. or in /etc/grub.d/40_custom. After editing this you will have to run grub2-mkconfig -o /boot/grub2/grub.cfg which will compile all the grub info into /etc/grub2/grub.cfg I believe the custom.cfg entries end up after the 40_custom entries that the OS may have included. There is a persistent method entry if you did want to edit the /etc/grub2/grub.cfg directly, but probably not advised.

            Here is my entry for Windows boot partition and location of MS boot. Also below that is a UEFI entry for geting back to the BIOS, not relevent to this topic, but just so you see how the menu entries are defined. In my system these are at the end of all the other Linux entries.

            ### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows Boot Manager (on /dev/nvme0n1p2)' --class windows --class os $menuentry_id_option 'osprober-efi-4E48-193F' {
	insmod part_gpt
	insmod fat
	search --no-floppy --fs-uuid --set=root 4E48-193F
	chainloader /efi/Microsoft/Boot/bootmgfw.efi
}
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/30_uefi-firmware ###
menuentry 'UEFI Firmware Settings' $menuentry_id_option 'uefi-firmware' {
	fwsetup
}
  • @[email protected]
    18•1 year ago

    That’s why we need two ssds for dual boot

    And one day, we will have updates that will tell us “Windows have fixed a drive with partition table issues.”

  • @[email protected]
    11•1 year ago

    Ugh, that’s so annoying. Every time windows updates i have to open the BIOS and put ubuntu first on the boot order so it doesn’t skip grub.

    I Also have a drive that i can access on both linux and Windows and every so often Windows will make it inaccessible on Linux because it didn’t fully unmount the drive.

  • @[email protected]
    36•1 year ago

    Picture this: you buy a car. You buy a new set of wheels/rims and a new radio system with Android and whatever. You also put some new carpets on the floor of the car. Now you need to take it for a simple routine maintenance and checkup at the car brand official shop. After a few hours you go back there to pick you car up and it has the stock wheels, stock radio, stock carpets and everything and you ask where the hell is your stuff and ALL of them on the shop look at you confused like if they never seen any different accessory on that car before other than the stock ones, or don’t know what you are talking about. All they know is that the car is now “according to spec”.

    This is what it feels like after updating Windows with Linux in dual-boot on the same drive.

  • @[email protected]
    8•1 year ago

    For me its the opposite, Linux always boots fine but occasionally a linux system update will break the Windows boot option in systemd-boot

  • KillingTimeItselfEnglish
    7•1 year ago

    i need to remove my windows boot drive from my workstation, but it lives in a rack. And has a temperament. Sometimes when losing power shit just refuses to boot for like an hour, eventually it randomly boots. Still unsure why. Could be anything really. Best guess is bad cmos battery though. Could be slightly bunged bios, could be marginally fucky cpu. Who knows. It’s fine when shutdown with power for long periods of time though.

    Gotta love modern hardware, if only 7 segment displays weren’t a 300 dollar privilege.

  • @[email protected]
    23•1 year ago

    If I dual boot windows, I tend to disconnect my Linux drive any time I do anything on the Windows side. Even installing Windows fresh using default settings, it managed to completely erase my Linux disk to put the Windows bootloader on it even though I selected a completely different disk for the Windows OS. Won’t be making that mistake again. And by mistake I mean dual booting Windows. That pile of spaghetti code gets a VM.

    • @[email protected]
      3•1 year ago

      I got used to windows overwriting the MBR and could generally work around that. But the last time I tried windows/Linux dual boot, it was windows that got caught in a recovery loop after a windows update. Linux was fine. I was impressed at how thoroughly Windows had killed itself on a basic unmolested install. At that point I decided I was done with windows on bare metal unless it was the only thing running. Windows goes in the virtual sandbox or plays by itself.

    • KillingTimeItselfEnglish
      5•1 year ago

      windows installing its bootloader on a completely separate drive is such a weird and fucking idiotic issue for it to have.

  • SunRed
    20•1 year ago

    For the rare occasion that I need Windows bare metal, I have a Windows 11 installation on a usb ssd originally installed via the Rufus Windows-To-Go option that I can just plug into the system and boot off it whenever I need it without it touching my uefi menu or partition on my internal drives. This way I can also use it on another machine if that need arises. Windows can even trim the usb drive it’s running on. It pretty much works as if installed internally.

  • @[email protected]English
    2•1 year ago

    i have two other possibilities at hand, that do not involve two SSDs:

    1. don’t use intentionally broken software in the first place ;-)
    2. use another device for bootloader, could be a readonly CD or a usb drive, PXE/bootp could also do it.

    And if your company wants you to use rotten software, they also want you to give them the delays, downtimes and annoyances that naturally come with rotten decisions, just keep that in mind.

    Here is one thing to remember and why i call it rotten software and rotten decisions:

    Microsoft offers a free “blame the ransomware people” to any CTO who just wants to receive money without working at all or not having to “think” during work. That same CTO can get a bonus after “solving” the ransomware issue and then: “look how ‘invaluable’ that CTO is to the company” he “worked” for month ( yelling at engineers he previously told to install rotten software???) and resolved the ransomware issue!! This is same to those who work. no law has ever given people that many payed breaks from work as “rotten software” vendors did. and if you made a mistake and did not get trained before, you could blame bot beeing trained.

    Look at it from a “fingerpointer” point of view, one cloud always blame someone else for everything and the only one to blame is too big to fail and also untouchable due to their army of darkness lawyers. thus anything happened? no one could be guilty AND be held responsible. Also if one is slow at work, and so is his OS, obviously easy to blame someone else again.

    so microsoft offers a “solution” to “boss wants you to work more and quicker” but remember, that same boss only “needs” a cover for his own ass to be able to point to someone else and the ones creating the rotten software do deliver that ;-)

    i do not know any better wording for such a situation than “rotten” thus i name it so.