Show an internal recovery path on BitLocker preboot screens

Use this document to resolve one bounded operational decision: Show an internal recovery path on BitLocker preboot screens. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official BitLocker preboot recovery screen from Microsoft supports the following bounded statements:

• BitLocker policy can place a custom recovery message and URL on the preboot screen, including a self-service recovery portal, internal support site, or support phone number. The research record locates this support at Custom recovery message.
• BitLocker provides no specific hint for a recovery key saved to on-premises Active Directory; it displays the configured custom message or a generic instruction to contact the help desk. The research record locates this support at Recovery key hints > ordered rule 8.

Only the traced statements above are asserted as source facts. Apply the review to Windows security controls, protected identities, audit policy, telemetry, exclusions, administrative roles, and response workflows after confirming that the source and deployed context match.

What the source does not establish

Applies to Windows 10, Windows 11, and Windows Server 2016 through 2025; screen guidance does not prove key escrow, user access, localization, or successful recovery. It does not establish a deployment’s current state, authorize a production change, prove compliance, or show that Active Directory, Windows DNS, certificate trust, time, endpoint management, telemetry pipelines, and security operations are healthy. Documented options are review inputs, not universal mandates.

Applicability questions

• For source statement 1 at Custom recovery message, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Recovery key hints > ordered rule 8, which observable configuration, record, or test can confirm applicability here?
• Which deployed instance of Windows security controls, protected identities, audit policy, telemetry, exclusions, administrative roles, and response workflows will be compared with the source, and why that instance?
• How will the review distinguish a source mismatch from a failure in Active Directory, Windows DNS, certificate trust, time, endpoint management, telemetry pipelines, and security operations?
• Who approves the conclusion, exception, test window, and rollback threshold?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Begin by recording scope and current state before deciding whether a change is warranted. Record the source location, examined part of Windows security controls, protected identities, audit policy, telemetry, exclusions, administrative roles, and response workflows, observed and expected states, owner, and reason for deviation.

For an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Active Directory, Windows DNS, certificate trust, time, endpoint management, telemetry pipelines, and security operations in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.

Verification and evidence

A reviewer should be able to retrace the decision from Custom recovery message; Recovery key hints > ordered rule 8 through policy and feature state, security events, test detections, administrative assignments, exception approvals, and response tickets. Record what was collected, where, when, by whom, and which system or role it represents.

Close the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.

Official references

• BitLocker preboot recovery screen — Microsoft