​Microsoft has confirmed that it won't provide an automated fix for a known issue causing 0x80070643 errors when installing recent Windows Recovery Environment (WinRE) updates.

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

  • Aniki 🌱🌿@lemm.eeEnglish
    0·
    2 months ago

    Tips to avoid destroying a partition and having to reinstall the os?

    Start with a file system that doesn’t suck, like ext4, bless the drive with a boot loader that doesn’t suck, like Grub, and then get yourself a kernel that doesn’t suck, like GNU/Linux, then get yourself a software stack that doesn’t suck, like Arch.

    I use Arch, BTW.

    • FaceDeer@fedia.io
      0·
      2 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.comEnglish
          0·
          2 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.devEnglish
            0·
            2 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.