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?

  • Crackhappy@lemmy.world
    link
    fedilink
    English
    arrow-up
    18
    ·
    edit-2
    7 months ago

    I’ve been using windows since windows 3. The number of times I’ve used the “recovery” feature is exactly zero.

    Edit: Corrected by another user below. I have used it a couple times for update rollbacks, I just haven’t used it for a full recovery. When I’ve run into serious issues I just reload it from scratch, as I keep data and OS on completely separate drives.

    • Buelldozer@lemmy.today
      link
      fedilink
      English
      arrow-up
      15
      ·
      7 months ago

      The number of times I’ve used the “recovery” feature is exactly zero.

      The RE Partition is for more than Recovery. If you’ve ever uninstalled an update then you’ve used the RE Partition.

      • N3Cr0@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        7 months ago

        In this case I’m happy I always installed Windows without RE partition. It works fine and you can still uninstall updates. Broken system files can also be replaced by a fresh pull from Windows Update.

    • subignition@fedia.io
      link
      fedilink
      arrow-up
      6
      ·
      7 months ago

      Lucky for you! Twice over the years I have had Windows 10, the system failed to come back up after a windows update and the ability to uninstall the most recent update through the recovery partition saved me.

    • Possibly linux
      link
      fedilink
      English
      arrow-up
      3
      ·
      7 months ago

      It recovers in the background with no user intervention when things go wrong.