For Reactive AutoBoot, the preboot authentication screen isn't displayed if you exceed the specified number of Windows authentication failures

Technical Articles ID: KB80003
Last Modified: 4/17/2023

Environment

Drive Encryption (DE) 7.1.x
Endpoint Encryption (EEPC) 7.0.x

For details of DE 7.1.x supported environments, see KB79422 - Supported platforms for Drive Encryption 7.x.

Problem

If you exceed the specified maximum number of Windows authentication failures, Reactive Autoboot doesn't display the preboot authentication screen. Instead, you see the Windows logon screen and your Windows account is locked.

Cause

Preboot authentication isn't enabled after the maximum number of Windows authentication failures because after your account is locked by the Group Policy Objects (GPO) setting, Windows no longer processes through the Credential Provider. Therefore, EEPC doesn't see the subsequent logon attempts. EEPC relies on Windows to inform EEPC when the login fails and doesn't listen for accounts that are locked.

Solution

Set the Reactive Autoboot option to Disable and restart system after x failed logons or unlocks to be the same value as the Windows GPO setting, although it's best if you set it to one less than the GPO setting.

For assistance with setting the option above, see your EEPC Best Practices Guide or Product Guide.

For product documents, go to the Product Documentation portal.

Affected Products

Languages:

This article is available in the following languages:

Knowledge Center

For Reactive AutoBoot, the preboot authentication screen isn't displayed if you exceed the specified number of Windows authentication failures

Environment

Problem

Cause

Solution

Affected Products

Languages:

Title

Title

Knowledge Center

For Reactive AutoBoot, the preboot authentication screen isn't displayed if you exceed the specified number of Windows authentication failures

Environment

Problem

Cause

Solution

Affected Products

Languages:

Choose your region

Title

Title