this post was submitted on 24 Jan 2025
487 points (96.4% liked)
Actually Infuriating
328 readers
510 users here now
Community Rules:
Be Civil
Please treat others with decency. No bigotry (disparaging comments about any race, ethnicity, religion, gender, sexuality, nationality, ability, age, ). Personal attacks and bad-faith argumentation are not allowed.
Content should be actually infuriating
Politics and news are allowed, as well as everyday life. However, please consider posting in partner communities below if it is a better fit.
Mark NSFW/NSFL posts
Please mark anything distressing (death, gore, etc.) as NSFW and clearly label it in the title.
Keep it Legal and Moral
No promoting violence, DOXXing, brigading, harassment, misinformation, spam, etc.
Partner Communities
- Mildly Infuriating
- Furiously Infuriating
- Memes
- Political Memes
- Lemmy Shitpost
- Not The Onion
- You Should Know
- Lemmy Be Wholesome
founded 3 days ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I mean Microsofts programming is also just shit. I remember installing Windows 7 back then. The computer had an SSD and a HDD in it with old files. I later removed the HDD and it wouldn't boot. Because even though I installed Windows on the SSD, it put the bootloader onto the HDD.
I had the exact same thing happen to me and it pissed me off so much.
Windows still does that to this day. For some random reason, it will often create the EFI boot partition in a different drive than the one you're installing Windows to.
Yeah... It's typically best to only connect the drive you want the OS on, then add the other(s) post install