this post was submitted on 03 May 2024
181 points (94.6% liked)

Technology

59589 readers
3148 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
 

20240520 UPDATE: I just ran winupdate on an ancient win10 surface and after the same 643 error two more times, and running through all the available updates, it's now reporting I'm up to date. yippee.
I guess the latest update finally fixed it, at least on the Surface.

Anyone tried and succeeded? Not too awful plodding through the resizing? Tips to avoid destroying a partition and having to reinstall the os?

you are viewing a single comment's thread
view the rest of the comments
[–] Nougat@fedia.io 6 points 6 months ago* (last edited 6 months ago) (2 children)

I have done this multiple times on servers. It's beyond simple and doesn't take but a few minutes. Follow the instuctions and you're gold.

Edit: In short, you use diskpart to resize the boot partition down, then use diskpart again to resize the recovery partition up with the space you created in step one.

[–] Creat@discuss.tchncs.de 11 points 6 months ago (1 children)

Or you just runs the ps script provided by Microsoft. 1 line. No clue why they can't do that themselves for affected systems...

[–] catloaf@lemm.ee 3 points 6 months ago

Change board says no

[–] possiblylinux127@lemmy.zip 1 points 6 months ago

You could just free up space in the recovery partition