en-US windows computer

Require additional authentication at startup (Windows Server 2008 and Windows Vista)

Verified with Windows 11 25H2 — updated on July 12, 2026

Windows 11 25H2

Supported on: Windows Server 2008 and Windows Vista

Path in the GPO console

Computer Configuration\Administrative Templates\Windows Components\BitLocker Drive Encryption\Operating System Drives

Description

This policy setting allows you to control whether the BitLocker Drive Encryption setup wizard will be able to set up an additional authentication method that is required each time the computer starts. This policy setting is applied when you turn on BitLocker. Note: This policy is only applicable to computers running Windows Server 2008 or Windows Vista. On a computer with a compatible Trusted Platform Module (TPM), two authentication methods can be used at startup to provide added protection for encrypted data. When the computer starts, it can require users to insert a USB flash drive containing a startup key. It can also require users to enter a 4-digit to 20-digit startup personal identification number (PIN). A USB flash drive containing a startup key is needed on computers without a compatible TPM. Without a TPM, BitLocker-encrypted data is protected solely by the key material on this USB flash drive. If you enable this policy setting, the wizard will display the page to allow the user to configure advanced startup options for BitLocker. You can further configure setting options for computers with and without a TPM. If you disable or do not configure this policy setting, the BitLocker setup wizard will display basic steps that allow users to turn on BitLocker on computers with a TPM. In this basic wizard, no additional startup key or startup PIN can be configured.

Registry

HKLM SOFTWARE\Policies\Microsoft\FVE

More options available

Options

Allow BitLocker without a compatible TPM (requires a password or a startup key on a USB flash drive)
EnableNonTPM boolean - default: 1
Configure TPM startup key:
UsePartialEncryptionKey enum
  • Allow startup key with TPM -> 2 (default)
  • Require startup key with TPM -> 1
  • Do not allow startup key with TPM -> 0
Configure TPM startup PIN:
UsePIN enum
  • Allow startup PIN with TPM -> 2 (default)
  • Require startup PIN with TPM -> 1
  • Do not allow startup PIN with TPM -> 0

Export Builder

BETA

Configure the state, scope and options, then generate .reg, PowerShell, Intune and SCCM outputs — or add the setting to a multi-setting collection.

These exports write the registry — this is not a managed GPO.

.reg file

Windows Registry Editor Version 5.00

; Exported from gporais.com
; Policy: Require additional authentication at startup (Windows Server 2008 and Windows Vista)
; State: Enabled
; Supported on: Windows Server 2008 and Windows Vista

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\FVE]
"EnableNonTPM"=dword:00000001
"UsePartialEncryptionKey"=dword:00000002
"UsePIN"=dword:00000002
More formats (PowerShell, Intune, SCCM)

PowerShell

# Exported from gporais.com
# Policy: Require additional authentication at startup (Windows Server 2008 and Windows Vista)
# State: Enabled
# Supported on: Windows Server 2008 and Windows Vista

$path = 'HKLM:\SOFTWARE\Policies\Microsoft\FVE'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'EnableNonTPM' -Value 1 -Type DWord
Set-ItemProperty -Path $path -Name 'UsePartialEncryptionKey' -Value 2 -Type DWord
Set-ItemProperty -Path $path -Name 'UsePIN' -Value 2 -Type DWord

Building a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.

Open the Builder

Embed this policy on your site

What to embed
Theme

Adds one script line: the theme follows your site’s appearance and the height fits the content. If your site blocks scripts, the embed follows the visitor’s system theme.

Preview