• dogslayeggs@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 months ago

    I don’t think you’re right. Those bullets are: “The following list provides examples of common events that cause a device to enter BitLocker recovery mode when starting Windows:”

    Why would entering the Bitlocker PIN too many times cause BitLocker to activate? If you are entering a BitLocker PIN then you have already activated BitLocker, right? Please explain to me why, in your scenario, I would be in the position to enter the BitLocker PIN too many times when all I was doing was restarting my tablet after an OS update.

    The last bullet says it also happens when “Exceeding the maximum allowed number of failed sign-in attempts.” So even if you are correct that the first bullet is about the BitLocker PIN, then the last bullet is about failed sign-in attempts to Windows.

    I like how you keep dismissing someone who is providing evidence by replying with being a jerk instead of giving helpful or factual information. You’re dying on the stupidest hill here.

      • dogslayeggs@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        3 months ago

        https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-10/security/threat-protection/security-policy-settings/interactive-logon-machine-account-lockout-threshold

        Right there, in plain English directly from Microsoft:

        "Failed password attempts on workstations or member servers that have been locked by using either Ctrl + Alt + Delete or password-protected screen savers count as failed sign-in attempts.

        The security setting allows you to set a threshold for the number of failed sign-in attempts that causes the device to be locked by using BitLocker. This threshold means, if the specified maximum number of failed sign-in attempts is exceeded, the device will invalidate the Trusted Platform Module (TPM) protector and any other protector except the 48-digit recovery password, and then reboot. "

        • IHawkMike@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          3 months ago

          Look man, this is just exhausting. I’m well aware of that security policy. I have enabled it at some of my clients. But it’s not a default setting and would never be on a random non-enterprise PC. This is what I mean when I say the only people who are getting locked out this way were screwing with their computers in ways they don’t understand, installing random garbage and following bad advice on the internet.

          From your link:

          If you set the value to 0, or leave blank, the computer or device will never be locked as a result of this policy setting.