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?

  • FaceDeer@fedia.io
    link
    fedilink
    arrow-up
    44
    arrow-down
    7
    ·
    7 months ago

    OP asked “how can I accomplish goal X?”

    You responded “Goal X sucks, you should accomplish goal Y instead!”

    That’s not exactly useful.

      • wizardbeard@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        6
        arrow-down
        2
        ·
        7 months ago

        They don’t need to reinstall the OS to resolve this issue though, unless they absolutely fucked their paritions.

        Which is why Microsoft couldn’t automate a fix. It’s incredibly easy to fuck your partitions to hell and back, especially through Windows. Too many conditions to check for and try to handle automatically.

        • NekkoDroid@programming.dev
          link
          fedilink
          English
          arrow-up
          6
          ·
          7 months ago

          It’s incredibly easy to fuck your partitions to hell and back, especially through Windows.

          Fun fact: Windows won’t allow you to delete any EFI partition (that is the only one I know of/tried) unless its through diskpart with a specific override/force option.

          But then again, I somehow nuked my recovery partition by accident at some point as well.

      • FaceDeer@fedia.io
        link
        fedilink
        arrow-up
        4
        arrow-down
        1
        ·
        7 months ago

        And if they’re having trouble with their car they could just hire a taxi. But they’re trying to fix their car so telling them to hire a taxi is useless advice.