{"id":293,"date":"2026-10-05T01:06:19","date_gmt":"2026-10-04T23:06:19","guid":{"rendered":"https:\/\/hands-on-security.com\/new-site-asdfbvi\/?p=293"},"modified":"2026-11-18T20:40:41","modified_gmt":"2026-11-18T19:40:41","slug":"bitlocker-microsoft-account-hint","status":"publish","type":"post","link":"https:\/\/hands-on-security.com\/index.php\/2026\/10\/05\/bitlocker-microsoft-account-hint\/","title":{"rendered":"The locked laptop already knows whose account holds the key"},"content":{"rendered":"<p>Since Windows 11 24H2, BitLocker&#8217;s recovery screen can show a masked Microsoft-account hint when a recovery key has been saved to that account. I went looking for where Windows stores it. It is in plain volume metadata, readable from a disk image without unlocking the drive.<\/p>\n<p>In January 2026, <a href=\"https:\/\/www.forbes.com\/sites\/thomasbrewster\/2026\/01\/22\/microsoft-gave-fbi-keys-to-unlock-bitlocker-encrypted-data\/\" target=\"_blank\" rel=\"noopener noreferrer\">Forbes reported that Microsoft supplied BitLocker recovery keys to the FBI<\/a> after a search warrant in a Guam fraud case involving three laptops. Microsoft said it provides keys in response to valid legal orders when it holds them. Nothing was broken here; someone else was simply holding the key.<\/p>\n<p>For law-enforcement readers: preserve the <strong>full recovery-key identifier<\/strong> and include it in your request to Microsoft. It uniquely identifies the recovery-password protector. The account hint helps you match accounts you have lawful access to; it is not a substitute for the full identifier in the request.<\/p>\n<h2>The clue on the recovery screen<\/h2>\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/hands-on-security.com\/wp-content\/uploads\/2026\/10\/recovery-account-hint-editorial.jpg\" target=\"_blank\" rel=\"noopener noreferrer\"><img class=\"wp-image-302\" src=\"https:\/\/hands-on-security.com\/wp-content\/uploads\/2026\/10\/recovery-account-hint-editorial.jpg\" alt=\"BitLocker recovery instructions with the example account hint p***l@h****y.com outlined in red.\" width=\"1731\" height=\"909\" loading=\"lazy\" decoding=\"async\" srcset=\"https:\/\/hands-on-security.com\/wp-content\/uploads\/2026\/10\/recovery-account-hint-editorial.jpg 1731w, https:\/\/hands-on-security.com\/wp-content\/uploads\/2026\/10\/recovery-account-hint-editorial-300x158.jpg 300w, https:\/\/hands-on-security.com\/wp-content\/uploads\/2026\/10\/recovery-account-hint-editorial-1024x538.jpg 1024w, https:\/\/hands-on-security.com\/wp-content\/uploads\/2026\/10\/recovery-account-hint-editorial-768x403.jpg 768w, https:\/\/hands-on-security.com\/wp-content\/uploads\/2026\/10\/recovery-account-hint-editorial-1536x807.jpg 1536w\" sizes=\"auto, (max-width: 1731px) 100vw, 1731px\" \/><\/a><figcaption>Edited close-up of our test system&#8217;s recovery screen.<\/figcaption><\/figure>\n<p>Microsoft documents the hint in its <a href=\"https:\/\/learn.microsoft.com\/en-us\/windows\/security\/operating-system-security\/data-protection\/bitlocker\/preboot-recovery-screen\" target=\"_blank\" rel=\"noopener noreferrer\">preboot recovery guidance<\/a>. On my own test machine, a masked version of my address was staring back at me before I had unlocked the volume.<\/p>\n<p>Windows stores the hint outside the encrypted key payload. My tests confirmed it can be read from the stored metadata without unlocking the volume&#8217;s contents: an account clue available during an offline examination.<\/p>\n<h2>What you can read from a locked volume<\/h2>\n<p>The records belong to a specific recovery-password protector, the one associated with the familiar 48-digit recovery key. Together, they can provide:<\/p>\n<ul>\n<li>A masked account hint, when present.<\/li>\n<li>The full protector GUID.<\/li>\n<li>Recorded backup destinations: Microsoft account, Entra ID, Active Directory, save-to-file and print.<\/li>\n<li>Status flags and timestamps for each category.<\/li>\n<\/ul>\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/hands-on-security.com\/wp-content\/uploads\/2026\/10\/bitlocker-backup-records-tool-capture.png\" target=\"_blank\" rel=\"noopener noreferrer\"><img class=\"wp-image-309\" src=\"https:\/\/hands-on-security.com\/wp-content\/uploads\/2026\/10\/bitlocker-backup-records-tool-capture.png\" alt=\"Actual tool output showing one recovery-password protector, successful file and Microsoft-account backup records, their timestamps and the stored masked account hint.\" width=\"1176\" height=\"424\" loading=\"lazy\" decoding=\"async\" srcset=\"https:\/\/hands-on-security.com\/wp-content\/uploads\/2026\/10\/bitlocker-backup-records-tool-capture.png 1176w, https:\/\/hands-on-security.com\/wp-content\/uploads\/2026\/10\/bitlocker-backup-records-tool-capture-300x108.png 300w, https:\/\/hands-on-security.com\/wp-content\/uploads\/2026\/10\/bitlocker-backup-records-tool-capture-1024x369.png 1024w, https:\/\/hands-on-security.com\/wp-content\/uploads\/2026\/10\/bitlocker-backup-records-tool-capture-768x277.png 768w\" sizes=\"auto, (max-width: 1176px) 100vw, 1176px\" \/><\/a><figcaption>Our tool reading a test image: file and Microsoft-account backup records, with the stored account hint below. <a href=\"https:\/\/hands-on-security.com\/wp-content\/uploads\/2026\/10\/bitlocker-backup-records-tool-capture.png\" target=\"_blank\" rel=\"noopener noreferrer\">View full-size capture<\/a>.<\/figcaption><\/figure>\n<p>Keep the full GUID in your report. Our tooling displays it in full; Microsoft&#8217;s <a href=\"https:\/\/support.microsoft.com\/en-us\/windows\/security\/encryption\/find-your-bitlocker-recovery-key\" target=\"_blank\" rel=\"noopener noreferrer\">recovery guidance<\/a> uses the first eight characters to help match an account entry.<\/p>\n<h2>Three things to check<\/h2>\n<h3>A destination is not proof of success<\/h3>\n<p>The cloud callers I examined disable pre-upload attempt recording: they record a backup only after the upload reports success. That is a record of a past backup, not the account&#8217;s current contents: the user may later delete the key from their Microsoft account. Check this lead before reaching for the soldering iron.<\/p>\n<h3>The hint and timestamp can move separately<\/h3>\n<p>Windows can update the account hint while skipping a repeat status update. A new hint can sit beside an older <strong>recorded success time<\/strong>. Don&#8217;t treat them as a matched pair when building a timeline.<\/p>\n<h3>&#8220;Printed&#8221; might mean a PDF<\/h3>\n<p>Microsoft Print to PDF and a physical printer use the same category, with no printer name or output path stored. On a fresh Windows installation, a physical printer may not yet be configured. Print to PDF offers a convenient workaround when BitLocker refuses to save the key file to an encrypted drive. Look for a PDF on the desktop, in a sync folder or on another device.<\/p>\n<h2>For the defenders in the room<\/h2>\n<p>Personal-account backup on a corporate laptop puts a recovery key outside the organisation&#8217;s managed process. Ask where keys are backed up, who controls those accounts and who can access the copies. Volume metadata provides local evidence of backup handling; compare it with your managed recovery records.<\/p>\n<p>To rotate a recovery password, use Microsoft&#8217;s <a href=\"https:\/\/learn.microsoft.com\/en-us\/windows-server\/administration\/windows-commands\/manage-bde-protectors\" target=\"_blank\" rel=\"noopener noreferrer\"><code>manage-bde<\/code><\/a> in an elevated Command Prompt. Note the old recovery-password IDs, then add a replacement:<\/p>\n<pre class=\"wp-block-code language-text\"><code>manage-bde -protectors -get C: -type RecoveryPassword\nmanage-bde -protectors -add C: -RecoveryPassword<\/code><\/pre>\n<p>Back up the new password to your organisation&#8217;s recovery store and verify it can be retrieved. Only then remove each old recovery-password protector by its ID:<\/p>\n<pre class=\"wp-block-code language-text\"><code>manage-bde -protectors -delete C: -id \"{OLD-GUID}\"<\/code><\/pre>\n<p>Protector rotation does not re-encrypt the data; older disk images may still accept the old password.<\/p>\n<h2>Where the public tools stop<\/h2>\n<p>I checked Dissect and dislocker source on 4 October 2026. <a href=\"https:\/\/github.com\/fox-it\/dissect.fve\/blob\/0b3caf20c1e95136cb2eb4494303604e7629616b\/dissect\/fve\/bde\/information.py#L834-L858\" target=\"_blank\" rel=\"noopener noreferrer\">Dissect reads the backup record<\/a>, including its category, timestamps and flags, but the inspected revision has no account-hint parser. The <a href=\"https:\/\/github.com\/Aorimn\/dislocker\/blob\/0706462db88efe8df88150e4c3e4332b808f4581\/include\/dislocker\/metadata\/datums.h#L45-L71\" target=\"_blank\" rel=\"noopener noreferrer\">dislocker revision<\/a> parses neither record. As far as we have seen, public tooling does not yet surface the account hint.<\/p>\n<div class=\"callout\"><strong>Breaking BitLocker<\/strong><\/p>\n<p>Alongside TPM-bus attacks, we cover key custody, recovery paths and the evidence they leave.<\/p>\n<p><a href=\"\/index.php\/training\/breaking-bitlocker\/#dates\">View training dates<\/a> &middot; <a href=\"\/index.php\/contact\/#private-training\">Arrange a private class<\/a><\/p>\n<\/div>\n<h2>How I looked at this<\/h2>\n<p>I traced the BitLocker user-mode code into the kernel driver&#8217;s metadata write path, then tested the print workflow and account-hint recovery on my own system. The component versions and implementation details are below.<\/p>\n<p>My <a href=\"https:\/\/github.com\/Aorimn\/dislocker\/issues\/294\" target=\"_blank\" rel=\"noopener noreferrer\">related dislocker issue from 2022<\/a> concerned tools accepting different recovery-material formats. This is the same practical question, a few years on.<\/p>\n<div class=\"curriculum\">\n<details id=\"bitlocker-technical-appendix\">\n<summary>Part 2: The record, bit by bit<\/summary>\n<h3>Where the hint comes from<\/h3>\n<p>Windows obtains a username from the local identity system through <code>PKEY_Identity_UserName<\/code> and masks it before upload. After the upload reports success, the recording path can store that text against the same protector and Microsoft-account backup category.<\/p>\n<p>It is the local identity string, not an account ID returned by Microsoft&#8217;s server. Windows stores the masked text, not the full address. An update replaces the existing hint for that category. The Entra helper I inspected records backup status but does not call the account-hint setter.<\/p>\n<h3 id=\"backup-status-detail\">Status bits<\/h3>\n<p>The helpers use <code>0x0001<\/code> as an optional attempt marker. After a successful upload, they request success, <code>0x0002<\/code>, and clear the attempt bit. If attempt recording is enabled and a new record is written before upload, an ordinary upload-error exit leaves that record in place. The direct callers I examined do not enable this branch.<\/p>\n<p>With deferred writes, a borrowed workset can leave a memory-only change for its owner to commit later. A helper-owned deferred workset is closed before upload without writing the attempt record. A disk record requires a completed write.<\/p>\n<p>A failed retry preserves an earlier success-only record. The validator accepts both bits set, <code>0x0003<\/code>, but the inspected cloud transitions do not produce it from the normal states. It does not mean &#8220;success followed by a failed retry&#8221;.<\/p>\n<p>The category reader includes records without the success bit, so a listed destination needs its status checked.<\/p>\n<h3>Two timestamps<\/h3>\n<p>Both use Windows FILETIME: 100-nanosecond units since 1 January 1601 UTC.<\/p>\n<ul>\n<li><strong>Current record created:<\/strong> set when the category record is created and kept through updates. Deleting and recreating the record resets it.<\/li>\n<li><strong>Recorded success time:<\/strong> set when a success update is applied. It can be older than the latest upload. Zero means no success time was recorded.<\/li>\n<\/ul>\n<h3 id=\"backup-time-detail\">The timestamp-update rule<\/h3>\n<p>For an existing record, a success update leaves the whole backup-information record unchanged when all these conditions hold:<\/p>\n<ul>\n<li>No currently set flag is requested to be cleared.<\/li>\n<li>The previous recorded success time is nonzero.<\/li>\n<li>The current time is not later than the previous time, or is less than <code>864000000000<\/code> ticks (24 hours) later.<\/li>\n<\/ul>\n<p>At exactly that interval, the check permits the update. New records and requests clearing an existing set flag bypass it, including the cloud transition from attempt to success. The rule is category-independent and skips the whole backup-information replacement. Uploads and the separate account-hint update can still proceed.<\/p>\n<h3>Print category<\/h3>\n<p>The print handler uses category <code>0x10<\/code> without checking the printer type. A print result does not establish that the paper or PDF was retained. Printing and writing metadata are separate steps: Windows can report a successful print even if the later metadata commit fails. Where policy allows, Print to PDF also provides a setup workaround when Save to file rejects an encrypted destination.<\/p>\n<h3>Caller names<\/h3>\n<ul>\n<li>Wizard: <code>CFveuipManagerWizardData::<wbr>SavePasswordCloudAccount<\/code><\/li>\n<li>WMI: <code>CWin32_EncryptableVolumeProvider::<wbr>BackupRecoveryInformationToMicrosoftAccount<\/code><\/li>\n<li>Entra, a separate path: <code>CFveApi::<wbr>AttemptAADBackup<\/code><\/li>\n<\/ul>\n<h3>Components examined<\/h3>\n<div class=\"wp-block-table\">\n<table>\n<caption>Windows components and their role in this analysis<\/caption>\n<thead>\n<tr>\n<th scope=\"col\">Component<\/th>\n<th scope=\"col\">Role<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>manage-bde.exe<\/code><\/td>\n<td>Command-line front end<\/td>\n<\/tr>\n<tr>\n<td><code>fveapi.dll<\/code><\/td>\n<td>Backup\/account readers, setters and metadata updates<\/td>\n<\/tr>\n<tr>\n<td><code>fveapibase.dll<\/code><\/td>\n<td>Base-API backup-record reader<\/td>\n<\/tr>\n<tr>\n<td><code>fveskybackup.dll<\/code><\/td>\n<td>Personal Microsoft-account and Entra paths; account-name masking<\/td>\n<\/tr>\n<tr>\n<td><code>fvewiz.dll<\/code><\/td>\n<td>Save to file and Print handlers<\/td>\n<\/tr>\n<tr>\n<td><code>Win32_<wbr>Encryptable<wbr>Volume.dll<\/code><\/td>\n<td>WMI provider and caller arguments<\/td>\n<\/tr>\n<tr>\n<td><code>win32_<wbr>encryptable<wbr>volume.mof<\/code><\/td>\n<td>WMI method schema<\/td>\n<\/tr>\n<tr>\n<td><code>fvevol.sys<\/code><\/td>\n<td>Kernel-side validation, serialization and metadata I\/O<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p>The six user-mode binaries report <code>10.0.26100.9278<\/code>; <code>fvevol.sys<\/code> reports <code>10.0.26100.9444<\/code>. These are component file versions. The MOF supplies the WMI schema.<\/p>\n<h3 id=\"backup-call-paths\">From backup action to metadata<\/h3>\n<p><a href=\"https:\/\/hands-on-security.com\/wp-content\/uploads\/2026\/10\/bitlocker-backup-call-paths.png\" target=\"_blank\" rel=\"noopener noreferrer\">Open the full-resolution diagram<\/a><\/p>\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/hands-on-security.com\/wp-content\/uploads\/2026\/10\/bitlocker-backup-call-paths.png\" target=\"_blank\" rel=\"noopener noreferrer\"><img class=\"wp-image-299\" src=\"https:\/\/hands-on-security.com\/wp-content\/uploads\/2026\/10\/bitlocker-backup-call-paths-scaled.png\" srcset=\"https:\/\/hands-on-security.com\/wp-content\/uploads\/2026\/10\/bitlocker-backup-call-paths-417x1024.png 417w, https:\/\/hands-on-security.com\/wp-content\/uploads\/2026\/10\/bitlocker-backup-call-paths-768x1887.png 768w, https:\/\/hands-on-security.com\/wp-content\/uploads\/2026\/10\/bitlocker-backup-call-paths-scaled.png 1042w, https:\/\/hands-on-security.com\/wp-content\/uploads\/2026\/10\/bitlocker-backup-call-paths.png 2220w\" sizes=\"auto, (max-width: 780px) calc(100vw - 40px), 740px\" alt=\"Static BitLocker call paths: wizard and WMI calls disable attempt recording; status and account hint update separately before a conditional disk commit.\" width=\"740\" height=\"1818\" loading=\"lazy\" decoding=\"async\"><\/a><figcaption>Microsoft-account backup path reconstructed from static analysis. The account-hint update can run even when the status record stays unchanged. The dashed branch is an optional helper capability disabled by the inspected direct callers.<\/figcaption><\/figure>\n<\/details>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>A locked BitLocker drive can reveal a masked Microsoft-account hint. We traced where Windows stores it and tested what an examiner can read without unlocking the volume.<\/p>\n","protected":false},"author":1,"featured_media":305,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"hos_description":"BitLocker can expose a masked Microsoft-account hint on a locked drive. Our research traces the metadata, backup records and their forensic meaning.","hos_image":"","hos_social_image":303,"hos_byline":"Pascal","hos_author_ids":"","hos_author_type":"Person","hos_author_url":"https:\/\/hands-on-security.com\/index.php\/about\/","hos_related_course":145,"hos_references":"Microsoft Learn: BitLocker preboot recovery screen | https:\/\/learn.microsoft.com\/en-us\/windows\/security\/operating-system-security\/data-protection\/bitlocker\/preboot-recovery-screen\r\nMicrosoft Support: Find your BitLocker recovery key | https:\/\/support.microsoft.com\/en-us\/windows\/security\/encryption\/find-your-bitlocker-recovery-key\r\nMicrosoft Learn: BitLocker recovery process | https:\/\/learn.microsoft.com\/en-us\/windows\/security\/operating-system-security\/data-protection\/bitlocker\/recovery-process\r\nThomas Brewster, Forbes, 23 January 2026: Microsoft Gave FBI Keys To Unlock Encrypted Data | https:\/\/www.forbes.com\/sites\/thomasbrewster\/2026\/01\/22\/microsoft-gave-fbi-keys-to-unlock-bitlocker-encrypted-data\/\r\nDissect parser, revision 0b3caf2 | https:\/\/github.com\/fox-it\/dissect.fve\/blob\/0b3caf20c1e95136cb2eb4494303604e7629616b\/dissect\/fve\/bde\/information.py\r\nDissect record and category definitions, revision 0b3caf2 | https:\/\/github.com\/fox-it\/dissect.fve\/blob\/0b3caf20c1e95136cb2eb4494303604e7629616b\/dissect\/fve\/bde\/c_bde.py\r\ndislocker datum definitions, revision 0706462 | https:\/\/github.com\/Aorimn\/dislocker\/blob\/0706462db88efe8df88150e4c3e4332b808f4581\/include\/dislocker\/metadata\/datums.h\r\nPascal Gujer, dislocker issue 294, 28 October 2022 | https:\/\/github.com\/Aorimn\/dislocker\/issues\/294","footnotes":""},"categories":[5],"tags":[],"class_list":["post-293","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-system-security"],"_links":{"self":[{"href":"https:\/\/hands-on-security.com\/index.php\/wp-json\/wp\/v2\/posts\/293","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/hands-on-security.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/hands-on-security.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/hands-on-security.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/hands-on-security.com\/index.php\/wp-json\/wp\/v2\/comments?post=293"}],"version-history":[{"count":17,"href":"https:\/\/hands-on-security.com\/index.php\/wp-json\/wp\/v2\/posts\/293\/revisions"}],"predecessor-version":[{"id":409,"href":"https:\/\/hands-on-security.com\/index.php\/wp-json\/wp\/v2\/posts\/293\/revisions\/409"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/hands-on-security.com\/index.php\/wp-json\/wp\/v2\/media\/305"}],"wp:attachment":[{"href":"https:\/\/hands-on-security.com\/index.php\/wp-json\/wp\/v2\/media?parent=293"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/hands-on-security.com\/index.php\/wp-json\/wp\/v2\/categories?post=293"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/hands-on-security.com\/index.php\/wp-json\/wp\/v2\/tags?post=293"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}