PC alternate start recovery email corrupted?

Question

This happened weeks ago. I found a simple work around, but I was curious as to why the problem could even occur to begin with.

I was trying to update my AMD graphics drivers and Bitlocker became involved somehow. I thought that I was using the AMD control panel.
Anyway I downloaded the new drivers and restarted my PC.
The startup screen declares that something went wrong and my pin had been lost.
I type in my password but the system does not recognize it.
I try sending a password reset to my recovery email, but nothing seems to happen.
Eventually I notice that my recovery email listed in the alternate start method is missing the last letter of the email address.
I panic for a bit.
Then I make a new email account with the same email address minus the last letter.
I have the PC send the password reset and it arrives to this email address that has only existed for a few seconds.
So I go into outlook and add this brand new email address to my recovery options, right below my regular account recovery email... which is still there, properly written.
I tried to change the recovery email in my PC settings to the proper recovery email address, but the system told me that I would have to make a new profile if I wanted to do that.

How did my password reset email on my PC lose a character off of the end? I know that I had to confirm the email when I set up the PC so it can't be that I had miss-typed the email from the start.

I is like if my recovery email changed from (example) ******@gmail.com to ******@gmail.com but only for my PC.

I have no desire to mess with it further, I am simply curious.
What happened, and why?

Answer 1

Hi Zebulous,

Thank you for sharing the details of your experience.

Based on how Windows sign-in and security features work, this behavior can occur when the system temporarily falls back to a local recovery method after a security-related change, such as a driver update or restart. In these situations, Windows may rely on cached sign‑in information stored on the device rather than pulling live details from the Microsoft account. If that local data becomes incomplete, the recovery screen may display an abbreviated recovery email address, even though the Microsoft account itself remains unchanged.

Importantly, this does not indicate an issue with your Microsoft account or that the recovery email was originally entered incorrectly. The full and correct recovery information continues to exist online and remains secure.

Here are some practical workarounds that you can try (if encountered again)

• Use an alternate sign-in option on the lock screen (Password instead of PIN), then re‑create the PIN after signing in.
• Confirm account security info online by signing in at Microsoft Account from another device.
• Suspend device encryption temporarily before major driver or firmware updates, then resume it after the update completes.
• Create a new local profile only if necessary to refresh locally stored sign‑in data.

I appreciate you taking the time to understand what happened, and I'm glad you were able to regain access successfully.

Let me know if you need further assistance, feel free to ask me by clicking "Add Comment" or "Add Answer" if you cannot add comment so your response will be visible. Thanks for your effort.

---

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Windows stores multiple, separate pieces of information that can look like “recovery email addresses,” and they don’t all come from the same place:

1. The Microsoft account security info (email/phone used for account recovery)
2. The sign-in options and “alternate” sign-in methods on the local device (Windows Hello PIN, password reset options, etc.)

The key points from the described behavior:

• The Microsoft account itself still had the correct recovery email address (and that’s what showed correctly when checking account recovery options in Outlook/online).
• Only the local Windows sign-in flow on that PC showed a truncated address and sent mail to that truncated address.
• Creating a new mailbox that exactly matched the truncated address immediately started receiving the reset mail, which proves the PC was consistently using that shortened string.

This means the corruption was local to the device’s stored sign-in configuration, not to the Microsoft account in the cloud.

The most likely explanation, based on how Windows sign-in and BitLocker recovery behave, is:

• During a change that affected secure startup (for example, driver or firmware/boot configuration changes that triggered BitLocker/Windows Hello protection logic), Windows revalidated or re-read the locally cached sign-in and recovery configuration.
• That cached configuration contained a malformed or partially written email string (missing the last character). This could be the result of:
  • A one-time write or sync error when the device originally stored the email locally.
  • A local profile or credential store corruption event (for example, caused by a crash, power event, or other system issue) that truncated the stored value.
• Because the Microsoft account backend still had the correct address, only the device’s local sign-in UI and logic were affected. That is why the online account recovery options remained correct.

Windows requires creating a new profile to change that specific locally bound recovery identity because:

• Certain sign-in and recovery bindings (PIN, Hello, local recovery contact) are tied to the original identity and security keys created when the profile was first set up.
• Changing those bindings in-place would weaken the guarantee that the device is still associated with the same original identity and secure state, so Windows treats it as a “new identity” scenario and requires a new profile.

In short:

• The email address in the Microsoft account was never changed or corrupted.
• A local copy of that address, used only by that PC’s sign-in/recovery flow, was stored incorrectly or became corrupted (truncated by one character).
• When the system needed to use that local value (after the driver/boot change that involved BitLocker/Windows Hello), it sent the reset mail to the truncated address.
• Fixing it fully at the OS level would require creating a new Windows profile because that local recovery identity is part of the profile’s security configuration.

---

References:

• BitLocker recovery overview
• BitLocker recovery process
• BitLocker recovery: known issues
• Fix a corrupted user profile
• My username and password have stopped working