• azenyr@lemmy.world
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    8 months 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.

  • Kerb@discuss.tchncs.de
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    7 months ago

    i use a different drive for my windows installation because that happened to often,
    and i swear it once managed to wipe the bootloader on the linux drive.

    i have no idea how it did that,
    but i avoided starting windows using the grub entry since then.

    • kadu@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      8 months ago

      Having two drives is sometimes not enough, either. I have no idea why, but anytime Windows installs for the first time or goes through a major update (not the small security patches, but the periodic feature releases) there’s a random D20 dice throw to determine if it will randomly decide to create the bootloader and recovery partitions in another drive, even though your main installation isn’t there.

      I kid you not, Windows 10 once decided that my external SSD enclosure was the best place to put the bootloader.

      • henfredemars@infosec.pub
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        8 months ago

        This happened to me! Did an update, unplugged my eSATA and BAM! Can’t find bootloader. I literally, physically facepalmed when I realized what happened. At least the old one still worked from the primary.

        I’ve done a ton of Linux updates and this has never happened to me once (yet).

      • raspberriesareyummy@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        8 months ago

        It’s the usual problem: if your employer IT refuses to budge, you get locked into a Windows (or Apple) ecosystem. I had the same. My solution was to remove myself from corporate IT, and use my own device.

        I use workarounds for the interfaces with corporate:

        • MS Teams Linux client (sadly discontinued as of 2022) still works out of a jail, but the browser solution is also tested and ready as backup should I be forced
        • Webmail instead of a proper mail proram - that’s a big trade-off, but I can work with it, as much as it sucks
        • Webex for conferencing (as it works properly with Firefox, contrary to many other solutions)
        • Web portals continue to work - even though sometimes I need a user agent switcher to pretend I am using chrome (fuck you @MS Teams)
  • Pan_Ziemniak@midwest.social
    link
    fedilink
    arrow-up
    2
    ·
    8 months 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.

    • RBG@discuss.tchncs.de
      link
      fedilink
      arrow-up
      1
      ·
      8 months ago

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

  • UnculturedSwine@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    8 months 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.

  • joe_archer@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    8 months ago

    Remember kids, if you’re gonna dual boot, stay safe, use 2 drives, and pray you’re fast enough to mash the boot menu button when you power on.

  • IninewCrow@lemmy.ca
    link
    fedilink
    English
    arrow-up
    1
    ·
    8 months ago

    Never trusted this setup to begin with because I didn’t trust Microsoft and I’m not all that capable or want to take time to sort this stuff out on a regular basis.

    So I just setup my ThinkPad laptop with two removable SSDs and I just swap one or the other whenever I need. The drive is easily switched, from power down, remove drive, insert other drive and restart only takes about two minutes.

    I’m not going to risk messing up my setup because two operating systems can’t work with one another.

    Besides I seldom switch, I use Windows if I really have to about three or four times a year.

  • CubitOom@infosec.pub
    link
    fedilink
    English
    arrow-up
    1
    ·
    8 months 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.

  • Jordan_U@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    8 months ago

    It’s at least gotten a bit better.

    There was a time when Photoshop and other programs used a copy-protection scheme that overwrote parts of grub, causing the user not to be able to boot Linux or Windows.

    They knew about it, and just DGAF. I don’t remember their exact FAQ response, but it was something along the lines of “Photoshop is incompatible with GRUB. Don’t dual boot if you use Photoshop.”

    Grub still has code for BIOS based installs that uses reed-solomon error correction at boot time to allow grub to continue to function even if parts of its core.img were clobbered by shitty copy protection schemes for Windows software.

  • BCsven@lemmy.ca
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    8 months 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.

  • TacoNot@mander.xyz
    link
    fedilink
    arrow-up
    0
    ·
    8 months ago

    I have power switches for my drives. If I want to boot into windows, I turn that one on and the others off.

    • Hadriscus@lemm.ee
      link
      fedilink
      arrow-up
      1
      ·
      8 months ago

      how do you do that ? physical switches ? do you buy them separately and solder them ? where ?

  • BeigeAgenda@lemmy.ca
    link
    fedilink
    arrow-up
    0
    ·
    8 months ago

    Two ssds is when you need to run stuff on windows that requires the bare metal.

    Windows needs to be contained, controlled and told who is the boss, I suggest using Tiny11 or MicroXP in a VM for stuff that can’t run in wine.