obbeel@lemmy.eco.br to Linux@lemmy.ml · 3 months agoMicrosoft’s latest security update has ruined dual-boot Windows and Linux PCswww.theverge.comexternal-linkmessage-square148fedilinkarrow-up1570arrow-down16cross-posted to: linux@lemmy.ml
arrow-up1564arrow-down1external-linkMicrosoft’s latest security update has ruined dual-boot Windows and Linux PCswww.theverge.comobbeel@lemmy.eco.br to Linux@lemmy.ml · 3 months agomessage-square148fedilinkcross-posted to: linux@lemmy.ml
minus-squareCyberpunk Librarian@lemmy.mllinkfedilinkarrow-up24arrow-down1·3 months agoI literally got this error using a bootable SSD with Ubuntu Mate on it. Separate drives aren’t immune to the issue.
minus-squareNutWrench@lemmy.mllinkfedilinkarrow-up13·3 months agoI think I’ve managed to avoid this by making the Linux drive my boot drive and by leaving the Windows drive untouched. (i.e. grub bootloader on the Linux drive, with option to boot to Windows as the second choice)
minus-squaread_on_is@lemm.eelinkfedilinkEnglisharrow-up1·3 months agoThis isn’t true if you have a bootloader on each drive, which, I think, is what the we’re talking about.
/cdn.vox-cdn.com/uploads/chorus_asset/file/25299205/STK453_Privacy_D_CVirginia.jpg)
I literally got this error using a bootable SSD with Ubuntu Mate on it. Separate drives aren’t immune to the issue.
I think I’ve managed to avoid this by making the Linux drive my boot drive and by leaving the Windows drive untouched. (i.e. grub bootloader on the Linux drive, with option to boot to Windows as the second choice)
I’ve got the same setup 😎
This isn’t true if you have a bootloader on each drive, which, I think, is what the we’re talking about.