1219
you are viewing a single comment's thread
view the rest of the comments
[-] UnculturedSwine@lemmy.world 23 points 6 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.

[-] KillingTimeItself@lemmy.dbzer0.com 5 points 6 months ago

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

[-] ITGuyLevi@programming.dev 3 points 6 months ago

... on a proxmox host in another room.

[-] ElderWendigo@sh.itjust.works 3 points 6 months 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.

this post was submitted on 25 Mar 2024
1219 points (97.4% liked)

linuxmemes

20948 readers
423 users here now

I use Arch btw


Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS