Windows can't fuck your bootloader if you never boot to Windows
furry_irl
"For the fur in u"
Welcome to Furry_irl, a community for furry memes, shitposts, and other relatable images or comics.
Community rules:
- Code of Conduct โ Follow our instance rules.
- Post formatting โ All titles should be a single word, followed by _irl. An emoji may substitute the underscore.
- Credit artists โ If it's not your art, include who made it in the title or the post body. Links are appreciated, except to X/Twitter.
- Stay on topic โ Images should contain or be related to furries. Images should be relatable or a meme. This isn't the place for general art posts.
- Avoid AI images โ Our fandom has countless artists, please share their (or your own) labors of love instead.
Can you imagine how fluffing concerning it would be if it did though? Like what arbitrary code execution fluffery is this??
Maybe nest an install script in cpu microcode that executes at random power ons to install a minimal windows IoT for the sole reason of highjacking boot sequences?
Their linux should still be there, right? They just need to fix their bootloader. (and wipe Windows.) Right?
Yeah. I dual boot on an old laptop just in case I happen to need windows for something and sometimes the windows partition puts itself at the top of the boot order, but my Debian partition is still there and I just have to put it back at the top.
I can't trust windows enough to install it on the same ssd where my Linux distro reside.
solution: make a linux distro that deletes the windows bootloader
Place Grub and Linux on one drive (physical) and Windows on another is what I did.
yeah windows sneeky snacking the bootloader was one of the reasons i quit dual booting a decade ago, have not missed windows a single moment since then
I don't doubt that it can happen but Windows has never messed with my GRUB even on major updates and even, IIRC, when "upgrading" from Windows 10 to 11.
Use sleep mode