this post was submitted on 20 Apr 2024
752 points (93.1% liked)
linuxmemes
21189 readers
570 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo in Windows.
- No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
I mean, if you duel boot, it's just a matter of time until Windows nukes your other OS. At least with me, my Linux was about to solve world peace, but Windows got wind of that and shut it the fuck down.
Meme is correct, they're coming for you.
I almost wanted to correct you and say its dual not duel, but when I think about it windows will fight to be the only bootloader right when you think its finally behaving.
Wanted to say the same: the typo made the comment better. There has to be a community for this.
Windows basically never nukes the actual linux install. It DOES like breaking the bootloader though. Which is fixable but still deeply annoying.
Ah damn this is exactly what happened a few days ago. My popos boot entry suddenly disappeared. I can still just boot from the physical ssd it's installed on, but I found it strange it just pooped out somehow. Any pointers on how to fix it?
Here's an article on how to fix it.
TLDR: You need to boot from a live disk, mount your install and reinstall the bootloader.
I still need to fix mine, thanks for the link. The weirdest break it did once was messing with my Wi-Fi driver, managed to break Linux' driver somehow, making the Internet a no go. Still no idea how Windows managed that though, they shouldn't be messing with my bios. :/
Make sure you disable fast boot in Windows. I’ve read that can put devices into a state where Linux can’t use them.
I haven't had it happen to me for a while now. I used to have a boot repair liveCD that'd always do the trick, but I don't think that specific distro even exists anymore.
The gist is you'll want to boot a liveCD and use the liveCD to reinstall GRUB, I'm sure you can find the right incantation to do so online somewhere.
Reminded me how Windows would set the hardware clock to different timezone that Linux uses, can't remember which.
It would make my blood boil, that's when I decided to never boot it again. 100% Linux everywhere, I get it on routers when I can.
Windows sets the hardware clock to local time, Linux sets it to UTC. It's possible to tell one to respect the others preference
I will never expect Windows to respect any preference. Updates burnt me too many times.
Linux for life.
Then you're clearly not dual booting and this advice wasn't for you
Not anymore I'm not, you are correct.
Also wrote that earlier.
So that's why windows always has the wrong time after I've been in my Linux install...
It should change it back eventually if you didn't disable setting the clock from Microsofts ntp servers
I have never had this issue on Mint/Windows duel boot
I have been running it for at least 6 months if not longer. So , I think that's a valid sample size
Do you receive windows updates?
I do update both OSes routinely
Hmmm maybe that depends on your configuration are you on windows 10 or 11?
Maybe thats why. Or do you have dual boot in two different drives?
Nope it's a partitioned M2
Maybe that problem occurs in relatively bigger updates, which is not now being pushed to win10, or maybe because the way bootloaders and handled may differ in your setup