this post was submitted on 08 Apr 2024
322 points (93.8% liked)

Technology

59534 readers
3135 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Kongar@lemmy.dbzer0.com 42 points 7 months ago (2 children)

Glad they have time to call out everyone else’s problems, yet Microsoft still can’t fix their broken jan win 10 update.

[–] AlphaOmega@lemmy.world 17 points 7 months ago (1 children)

Is that the one where MS updated the recovery partition by including a file that's too big for that default partition? I had to manually resize my recovery partition to fix that issue

[–] T156@lemmy.world 9 points 7 months ago* (last edited 7 months ago) (1 children)

Yes. Normally, the OS "fixes" this by making a second, bigger recovery partition, but that only works if you have the space for it.

[–] AlphaOmega@lemmy.world 3 points 7 months ago (1 children)

Well I guess 60 GB wasn't enough space for the 10mb update

probably requires you to have un-allocated space on the drive, which is even funnier.

[–] KillingTimeItself@lemmy.dbzer0.com 4 points 7 months ago (1 children)

don't worry, microsoft never figured out how to write bootloader installation software.

It can not only, install itself onto a slower, hdd, but also completely wipe any additional drives you have hooked up at the time of installation.

The fact that this STILL isn't fixed is baffling to me.

[–] exu@feditown.com 1 points 7 months ago (1 children)

Is this still an issue with UEFI nowadays? The other bootloader should still be selectable in the bootmenu if it wasn't overwritten.

well you see that's the problem, windows doesn't believe in this cute little thing called following standard, so sometimes it just fucking yeets that shit, taking the bootloader with it, because keep in mind, when you dual boot on the same drive. You usually end up using grub to dualboot between linux and windows, which windows doesn't like.

And as for installs, some updates are basically installs, so who knows what the fuck kinda bullshit windows will be doing then. And like i said, if you ever do a clean install on a system with other disks, you better hope you get lucky.