• @ramble81@lemm.ee
      0•1 year ago

      Heard you and that wouldn’t fly. Just like you’re not supposed to run Windows on mission critical systems like nuclear reactors (seriously, check the EULA), running multiple operating systems side by side is most likely out of a supported configuration and “use at your own risk”. You’d have zero standing or less for any sort of lawsuit.

      • @DaddleDew@lemmy.world
        0•1 year ago

        But just because it is in the EULA doesn’t make it legal. At a time where big tech is being kept under a microscope for antitrust regulation, I’d say that an OS that actively destroys other competing OSes on the machine it is installed on should be considered an unfair anti-competitor tactic.

          • KillingTimeItselfEnglish
            0•1 year ago

            Might not hold up legally, but it’s still insane that the single largest vendor of operating systems cant figure out how to install a bootloader with playing russian roulette.

  • @ZILtoid1991@lemmy.world
    0•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.”

  • @smb@lemmy.mlEnglish
    0•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.

  • @Pan_Ziemniak@midwest.social
    0•1 year ago

    Pfft, even 2 separate ssds for dual booting doesnt stop this from happening to me -___-

    On the plus side, this is the first i recall hearing of someone encountering the same issue, so i guess i dont feel as alone now.

    • @fuckwit_mcbumcrumble@lemmy.world
      0•1 year ago

      Windows has a lovely “feature” where it installs the bootloader on a secondary drive if there’s one connected. It doesn’t install it on drive 1 and drive 2, just drive 2. I always disconnect all secondary drives before installing windows for this very reason.

      That said you can configure the windows bootloader to recognize your Linux (or grub) and just use that to manage booting two OSes and it’s less likely to not destroy things.

    • Kerb
      0•1 year ago

      it stopped happening to me after i stopped using the grub entry to boot windows.

      i now use my mainboards boot menu to select the windows entry when i need to boot it

    • RBG
      0•1 year ago

      Is that actually easily fixable? Was planning to go dual-boot soon on my laptop and haven’t even considered this scenario.

      • Teppic
        0•1 year ago

        It’s relatively quick and easy to fix if you have a live boot Linux usb stick …and probably a second machine so you can Google what to do. It’s just also rather worrying at the time.

      • Kerb
        0•1 year ago

        iirc the last time it happened to me, i just needed to fix the uefi entry which wasnt that bad.
        (just remember to have a usb stick with a live image ready)

        if it were to overwrite your bootloader that would be a way harder fix.

        i dont remember if the second ever happend to me

      • @Steve@startrek.website
        0•1 year ago

        My old thinkpads have this great feature where the hard drive is easilly accessible on the side, so I leave the cover off and just swap the drive to boot into a different os

  • @hedgehog@ttrpg.network
    0•1 year ago

    Easy solution if you only have one SSD: instead of installing Windows as your second OS, install a different Linux distro.

  • @brucethemoose@lemmy.world
    0•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

  • JackGreenEarthEnglish
    0•1 year ago

    Both my drives are the same Linux distro, I have Windows and MacOS in a VM when I need them, and Windows To Go for rare cases where I actually need to boot win11.

  • @redcalcium@lemmy.institute
    0•1 year ago

    I have three ssd and none of them boot windows. I do have a windows vm (and macos too) in virt-manager in case I need it, but I haven’t boot them for about a year.

  • CubitOomEnglish
    0•1 year ago

    Windows actually works better in a vm on Linux than on bare metal. And it’s got a much smaller chance of breaking my PC that way too.