- cross-posted to:
- linux@lemmy.ml
- linux@lemmy.ml
- technology@lemmy.zip
- cross-posted to:
- linux@lemmy.ml
- linux@lemmy.ml
- technology@lemmy.zip
Already got you? this article tells you how you can fix it.
With all their talk about loving Linux you’d think they’d work on not breaking grub all the time.
They love Linux*!
*the windows subsystem for Linux
I’m glad I deleted that Windows partition since I didn’t use it anyways. And in typical Microsoft fashion they don’t acknowledge there’s even a problem leaving people in the dark. I’m never going back to Windows.
I read news like this and I’m so happy I haven’t had to touch Windows since Win7
Is this the new embrace, extend, extinguish?
This is the ongoing story of Microsoft since it started.
This worked for me: https://askubuntu.com/questions/1523353/windows-aug-13-update-broke-my-ubuntu-system The answer from ‘Ivan Ati’
Windows is malware and deserves to be treated as such
Am I right in assuming this only applies to single disks partitioned with both Windows and a Linux distro?
No. Any efi dual boot is affected.
Even separate disks? Ouch. I’m guessing Fedora is not impacted here.
Yes. Separate or single disks makes no difference, it writes changes to the efi partition that bios references to boot.
I don’t know whether fedora is impacted, the article specifies the following as documented impacts
" The reports indicate that multiple distributions, including Debian, Ubuntu, Linux Mint, Zorin OS, and Puppy Linux, are all affected."
And I also note that at least 2 arch implementations are impacted in addition to that list (i first saw it on arch forums).
I would suggest you definitely DON’T assume fedora is unaffected until you check your install, fedora participates in safeboot so given all the article listed distros also do (and arch has a method for it)
Odds are they’re impacted, M$ has done a scattergun on this, the only ones you can be sure are unaffected are those still bios booting rather than uefi
Appreciate the heads up. I don’t have a particular need for secureboot on the workstation I have in mind so I suppose I can just leave that disabled for now.
Sounds like a smart move.
My solution for cases like this is
sudo format c: /q && apt install linux
.