• Verdant Banana@lemmy.world
    link
    fedilink
    English
    arrow-up
    25
    arrow-down
    2
    ·
    edit-2
    10 months ago

    pc shop here

    BitLocker has caused several phone calls and most of the time a new drive (depending on the integrity of the current drive) and a fresh windows install is the only fix and that usually exposes bad or outdated hardware complicating things more

  • Corngood@lemmy.ml
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    1
    ·
    10 months ago

    I’m very curious about the vulnerability, but there doesn’t seem to be much info (only what MS posted).

    How could you possibly bypass bitlocker, unless they write the key to the recovery environment?

  • Toes♀@ani.social
    link
    fedilink
    English
    arrow-up
    7
    ·
    10 months ago

    Reminds me of when it was discovered that many hardware implementations used a fixed master key or random seed. Resulting in mass deployments of patches to disable hardware encryption in favour of software mode.

  • ryper@lemmy.ca
    link
    fedilink
    English
    arrow-up
    6
    ·
    10 months ago

    The manual fix requires the recovery partition to be after the OS partition, while my partitions go Recovery, EFI/System, then OS. I guess I’m just SOL? I don’t even have BitLocker enabled but an update that won’t install is going to be annoying.

    • mrtzlbm@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      10 months ago

      You could recreate the recovery partition behind the OS partition. You are able to shrink the OS partition to make space, the recovery partition only needs to be ~1 GB in size. It only takes a few diskpart commands to do this.