• @IHawkMike
    link
    English
    0
    edit-2
    4 months ago

    I don’t care what you think. I’m playing chess with a pigeon here. Test it yourself.

    Edit: And sorry for being a jerk. Back to my original point, I’m pretty much fed up with the “technical” communities of Lemmy where correct information is downvote to oblivion and blatantly wrong information is lionized as absolute truth. And when I have tried to actually help and provide useful information I get met with the hordes of confidently incorrect people trying to discredit me.

    • @dogslayeggs
      link
      English
      14 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
        link
        English
        04 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.