MicrosoftAccount login issues with RDP and second email

Hi Scott Anderson,

I just wanted to follow up and see if you had the opportunity to run through the account consolidation steps provided above. Were you able to successfully remove that duplicate profile and force Windows to sync your new Gmail credentials locally? Most importantly, did using the strict MicrosoftAccount\******@gmail.com username format finally allow you to connect to the laptop via RDP? If the system is still stubbornly rejecting your password, or if you are still running into roadblocks trying to recreate your Windows Hello PIN, please do not hesitate to let me know. I am here to help you get this fully resolved so you can actually enjoy that Pro upgrade!

Tracy.

Hi Scott Anderson,

I honestly understand your frustration. Getting locked out of RDP after a simple email alias change is a notorious quirk of how Windows handles Microsoft Account (MSA) authentication.

Here is the technical reality of what happened: When you changed your primary alias from Comcast to Gmail, your underlying Microsoft Account remained exactly the same. However, RDP relies on the local security cache of the host laptop. By adding the Gmail address as a new user, Windows got confused. It now sees two local profiles trying to claim the exact same Microsoft Account identity, which completely breaks remote authentication and prevents the system from generating a new Windows Hello PIN.

To fix this identity conflict and restore your RDP access, you need to consolidate the account and force a local security sync. Here is the exact path forward:

1. Remove the Duplicate Account Physically log into the laptop using your original user profile. Go to Settings > Accounts > Other users and completely remove the "new" user profile you created for the Gmail address. You only need your original profile, as it is still tied to your MSA.

2. Force a Local Credential Sync While still logged into your original profile (and connected to the internet), go to Settings > Accounts > Your info. If you see a "Verify" link, click it and follow the prompts. Next, lock the computer (Win + L) and unlock it by typing your actual Microsoft Account password (do not use your PIN). This forces the Windows local security authority to reach out to Microsoft's servers and update its internal cache with your new Gmail alias.

3. Use the Strict RDP Username Format When you attempt to connect via RDP from your other machine, do not just type your email address. You must explicitly tell the RDP client to use the Microsoft Account authentication provider. In the username field, type exactly this format: MicrosoftAccount\******@gmail.com (Note: Literally type the word "MicrosoftAccount", a backslash, and then your new Gmail address). Then, enter your standard Microsoft Account password.

I hope this technical breakdown clarifies the conflict and gets you successfully connected. If this resolves your RDP issue, please click "Accept Answer". Should you run into any errors during the sync process, feel free to leave a comment!

Tracy.

The sign-in issues are caused by the Microsoft account identity (email/alias) changing while the device and RDP are still expecting the original account identifier.

Key points from the context that apply:

1. A Microsoft account can have multiple aliases, and one of them is the primary alias. The account itself is the same; only the sign-in name changes. RDP and Windows sign-in are tied to the underlying account, not just the visible email.
2. When the primary alias is changed, the old alias can still exist on the account, or it can be removed. If removed, it cannot be added back and is permanently deleted as an alias.
3. If an alias matches a work/school account or conflicts with other identities, sign-in problems can occur until the primary alias and sign-in preferences are corrected.

From the context, the supported remediation steps are:

1. Verify and adjust aliases on the Microsoft account
   • Go to the Microsoft account profile and open Manage how you sign in to Microsoft.
   • Under Account aliases, ensure there is a personal email address that is valid and accessible.
   • If needed, add another alias (email or phone) and verify it.
   • Set the desired address as primary alias using Make primary.
2. Avoid using a work/school-style alias as primary
   • If the primary alias matches a work or school account (or similar), change it to a different personal alias to avoid conflicts, as described in the ADDriverStoreAccessNonLocalException guidance.
3. Do not remove the old alias if it is still needed for sign-in
   • If the old email is removed as an alias, it becomes permanently deleted as an alias and cannot be re-added. This can affect sign-in expectations on devices configured with that alias.
4. If there are multiple accounts with the same email
   • If a “Which account do you want to use?” prompt appears (work or school vs personal), it indicates two separate accounts using the same email. In that case, renaming the personal Microsoft account (changing its primary alias) is the supported way to avoid conflicts.
5. If sign-in verification or backup security info is wrong or outdated
   • When prompted for verification codes or backup methods that are no longer accessible, use I don't have any of these and follow the prompts to update security info.

Applied to the scenario:

• Ensure the Microsoft account used on the laptop has a valid, working primary alias and at least one additional alias (email or phone) configured and verified.
• If the old Comcast address was removed as an alias, it cannot be used again; rely on the new primary alias for sign-in.
• Confirm that the account is not conflicting with a work/school identity by making a clearly personal alias the primary.
• After fixing aliases and sign-in preferences on the Microsoft account, sign in locally on the laptop with that same Microsoft account identity, then retry RDP using the same account and updated alias.

If the password itself is incorrect or the account is locked due to multiple attempts, the context indicates that the appropriate next step is to use account recovery and, if necessary, wait for the lockout to clear before trying again.

References:

• "Something went wrong" with error ADDriverStoreAccessNonLocalException
• Add another alias to your account and make it the primary alias
• Which account do you want to use?
• Common problems with two-step verification for a work or school account
• Get to know the new Microsoft sign-in