this post was submitted on 13 Oct 2023
714 points (93.0% liked)
Memes
45666 readers
880 users here now
Rules:
- Be civil and nice.
- Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Literally does what's on the tin for me.
Updated, restarted to finish it and shut down completely after that.
My reboot button wipes the BIOS.
Never happened to me.
Maybe that's a problem because you dual boot?
If so: Not a supported use case by windows/ms and they will probably tell you to stop it and then it will work without issues.
If that is actually the case:
You can't just do stuff the company (as bullshit as it is) tells you not to, break the software and then call the company shit for doing something out of scope.
The company's software can't just do stuff I (as bullshit as it is) don't want it to, break my system and/or overwrite data on partitions and drives I did not give it explicit or implicit permission to read, access, or modify, and then tell me my use case is unsupported and so I just have to deal with it.
I'm not OP and I don't even dual boot, but it's my computer, not Microsoft's. If I want to dual boot, and Windows breaks that despite me not making any changes to Windows, then yes the company deserves to have shit placed at their feet. Linux doesn't overwrite any Windows data when it updates unless you tell it to, so why have tons of people (including multiple friends) had Windows overwrite their Linux data on updates?
Dual-booting literally is a supported use case
I had to do a firmware update for my new CPU. The firmware is shit. Last version I had the option of virtualization or networking, never both but the BIOS didn't wipe.