A laptop displays Windows settings for switching to a local account, with a warning to back up the BitLocker recovery key.
Microsoft is testing a Windows 11 change that should save some people from losing their files. In a new Insider build, switching from a Microsoft account (MSA) to a local account brings up a prompt to back up your BitLocker recovery key first. Most people never knew they had that key, and they won't think about it until the day the recovery screen asks for it.

The change is small, and it is still experimental. It targets a real way people lose data, so it's worth knowing how it works now, whether or not it ever reaches your PC.

A laptop displays Windows settings for switching to a local account, with a warning to back up the BitLocker recovery key. What Microsoft Is Testing​

The feature is in Windows 11 Insider Preview Build 26340.10013. Microsoft released it to the Experimental channel on November 16. In Microsoft's release notes, the entry is called "Secure switch from MSA to Local account." The notes say users who switch from MSA to local account from settings would be always prompted to back up their BitLocker recovery key with updated instructions in order to prevent any data loss.

The key points:

  • Build: 26340.10013. Microsoft says the build is based on Windows 11, version 26H2 and delivered through an enablement package.
  • Channel: Experimental. The official November 16 Insider blog post also announced Beta build 26320.10003, but the MSA-to-local reminder appears only in the Experimental build's release notes.
  • Trigger: switching from an MSA to a local account from inside Settings.
  • Behaviour: a prompt to back up the BitLocker recovery key, plus updated instructions.

Pureinfotech read the notes the same way. It reported that switching from a Microsoft account to a local account through Settings now includes a prompt to back up the BitLocker recovery key.

What we don't know yet​

Microsoft hasn't published a screenshot of the dialog. The release notes don't answer several questions:

  • Whether you can dismiss or skip the prompt
  • Whether it appears on PCs where encryption is off
  • What the "updated instructions" say

The usual Insider warning applies too. Microsoft says Experimental features may change, be removed, or never ship. Many are also delivered through Controlled Feature Rollout, so only some Insiders see them at first. If you're on the right build and don't see the prompt, it may not have reached your machine yet.

Windows Latest reported this change first. It says the prompt doesn't stop you from switching to a local account, and it doesn't turn off encryption. That fits the release notes, which only mention a backup prompt. The notes don't say either thing outright, though, so treat it as a reasonable reading rather than confirmed behaviour.

In short: this is an Experimental-channel test of a backup reminder. It doesn't block local accounts or change encryption, and it may never ship.

Why It Matters​

Changing how you sign in doesn't lock you out. The problem shows up later.

Microsoft's Device Encryption support page explains how it starts. Device Encryption turns on BitLocker automatically for the operating-system drive and fixed drives. When you first sign in or set up a device with a Microsoft account, or a work or school account, it is switched on and a recovery key is attached to that account. If you set up with a local account, Device Encryption isn't turned on automatically. Unlike full BitLocker Drive Encryption, which needs Pro, Enterprise or Education, Device Encryption also runs on Windows 11 Home.

So the usual path for a home user looks like this:

  1. Buy a laptop and set it up with a Microsoft account, which most people can't avoid without a workaround.
  2. Windows encrypts the drive quietly and saves the key to that account.
  3. Months later, the user switches to a local account for privacy or out of habit.
  4. Years later, they've forgotten the old account's password, or lost access to it.
  5. A firmware change sends the PC to the BitLocker recovery screen.

At step 5, Microsoft's find-your-recovery-key page offers no rescue. Microsoft Support can't retrieve, provide or recreate a lost BitLocker recovery key. If you can't find the key and can't undo the change that triggered recovery, you have to reset the device, and that removes all your files.

People on Microsoft's own Q&A forum have hit this. In one thread about devices set up with local accounts, an answer says there is no documented workaround to bypass BitLocker recovery or extract a clear key via WinRE/Command Prompt once the device is in recovery and the key is unavailable.

What triggers the recovery screen​

Normally the TPM unlocks the drive at boot without asking you anything. Microsoft's BitLocker FAQ and recovery documentation list changes that can make BitLocker ask for the key instead:

  • Moving the protected drive to another computer
  • A new motherboard with a new TPM
  • Turning off or clearing the TPM
  • Changes to boot configuration or BIOS/UEFI firmware

Boot order matters as well. The FAQ says a change in boot order affects the measurements BitLocker checks and will cause a recovery prompt. It also advises that laptops used with docking stations keep the internal disk first in the boot order, whether docked or not.

These are possible causes, not guarantees. Most BIOS updates go through without trouble. When one doesn't, though, you need the key right away and there is no fallback.

In short: the account switch is harmless on its own. The risk is losing track of where the key lives before you ever need it.

What Switching Doesn't Do​

Windows Latest makes a reassuring point: switching to a local account doesn't delete your Microsoft account or the key stored in it. As long as you can still sign in, you can get the key from another device, and since 24H2, the recovery screen even shows a hint of which account holds it.

Microsoft's support page confirms the hint. Starting with Windows 11, version 24H2, the recovery screen shows a hint of the Microsoft account linked to the key. That page also covers a common household catch: if someone else set up the PC or turned on BitLocker, the key may be in their Microsoft account. If the family's resident tech helper set up your laptop, check their account before you panic.

How to Back Up Your Key Before Switching​

You don't need the Insider build to do this. These steps follow Microsoft's documentation.

Step 1: Check whether your drive is encrypted​

Go to Settings > Privacy & security > Device encryption. Microsoft says that if this page doesn't appear, Device Encryption is either unavailable on the device or you're signed in with a standard user account. You need an administrator account.

To see why encryption might be unavailable, Microsoft suggests this check:

  1. Run System Information as administrator.
  2. Look for Automatic Device Encryption Support or Device Encryption Support in the System Summary.
  3. "Meets prerequisites" means Device Encryption is available. Other values point to a missing or disabled TPM, an unconfigured Windows Recovery Environment, or Secure Boot and PCR7 binding problems.

Step 2: Confirm the key exists where you think it does​

On another device, go to aka.ms/myrecoverykey and sign in with the Microsoft account you used to set up the PC. Find the entry for your device. Each key has a key ID, and on a locked machine you match it against the first eight digits of the recovery key ID shown on the recovery screen. Microsoft's guidance stresses that it's important to verify the backup exists and is accessible. Don't assume it was saved.

Step 3: Make a copy that doesn't depend on your Microsoft account​

  • Pro, Enterprise, Education: search Start for Manage BitLocker. Microsoft's BitLocker Drive Encryption page describes this Control Panel tool, which you can use to back up the recovery key. It's not available on Home.
  • Any edition, while Windows is running: from an elevated Command Prompt, manage-bde -protectors -get C: displays the recovery password for a drive. It needs admin rights and the correct drive letter. Copy the 48-digit number and its ID. As iTechify points out, this only works if you can already reach Windows, so do it now, not after the recovery screen appears.
  • Home users: copy the key from your Microsoft account's recovery page into a file stored on a different device, or print it.

Step 4: Keep the copy away from the PC​

A key saved only on the encrypted drive is no use when that drive is locked. Use a printout in your important-papers folder, a USB stick stored separately, or a password manager.

Step 5: Decide whether the cloud copy should stay​

If you're leaving the MSA for privacy, remember that the cloud copy stays on Microsoft's servers unless you delete it. Delete it only after you've confirmed your offline copy is correct, character for character.

Work and school PCs​

If your PC is managed by an organization, the key may be stored with that organization instead. Microsoft points users to the work-or-school recovery page or their IT department. Don't treat your personal account's recovery page as the final answer for a managed machine.

The Rest of the Build​

The same Experimental build includes two other BitLocker-related items for IT admins. Neither is part of the account-switch prompt.

  • TPM+PIN for standard users. Users without admin rights on managed devices can now set a BitLocker preboot PIN after a notification asks them to. Microsoft's release notes warn admins to target the required policies only at an Insider test group. Standard users without the feature can't add the TPM+PIN protector, so encryption fails, or already-encrypted TPM-only devices are reported as noncompliant.
  • Intune Remote Lock. IT can lock a lost or compromised device without wiping it. Nothing is erased: the device stays enrolled and managed; BitLocker stays on, and user data stays in place.

Analysis​

There are two ways to look at this. The cynical one is that the MSA push created the problem in the first place: Windows encrypted drives on its own, put the key in an account many people never wanted, and now adds a warning on the way out. Microsoft's own page on switching to a local account still says it recommends using a Microsoft account.

The practical view is that automatic encryption with a cloud-stored key is a sensible default for people who would never set up BitLocker themselves. The weak point was always the moment a user cut the link to the place their key was stored, and this prompt covers that moment. It doesn't stop anyone leaving, and it may stop someone wiping a laptop over a firmware update.

What would make it better? Showing the key's ID and location in the dialog itself, and making the prompt hard to click through without reading it. Until a screenshot appears, we don't know whether Microsoft has done either.

Bottom line: whether or not the prompt ships, back up your recovery key today, test that you can actually find it, and keep a copy away from the PC.

 

References

  1. Build 26340.10013 for Windows 11 26H2 adds Remote Lock and Taskbar upgrades pureinfotech.com
  2. BitLocker Recovery Key Without Microsoft Account: Where to Look itechify.com
  3. Windows 11 Insider Experimental Preview Build 26340.10013 - Windows Insider Program | Microsoft Learn learn.microsoft.com