Technology

59223 readers

3147 users here now

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

Our Rules

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

Approved Bots

founded 1 year ago

MODERATORS

[email protected]

182

Microsoft won't fix Windows 0x80070643 errors, manual fix required (www.bleepingcomputer.com)

submitted 6 months ago* (last edited 5 months ago) by [email protected] to c/[email protected]

38 comments fedilink hide all child comments

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

[–] [email protected] 20 points 6 months ago

I agree that if there was enough space in the recovery partition to begin with, this wouldn't be a problem, but the user isn't the party that specified that size or the party that decided to add enough stuff to the recovery partition to exceed that spec.

MS knows that this is a widely-deployed configuration (they deployed it), but they're going ahead with an automatic update that is incompatible with that configuration anyway, failing to communicate to the user why the failure occurred, and refusing to automate a fix to the thing their automation broke in the first place.