Hello Mahmudul Haque Adnan,
Thanks for the detailed follow-up. Let me try to address each point.
First of all, yes, it IS an administrator account that I'm using right now.
An administrator account and the special built-in Administrator account are different.
A normal account can have administrator privileges, while the built-in Administrator is a separate Windows account identified by a SID ending in -500. Please run: whoami /userOnly a SID ending in -500 confirms that the current account is the built-in Administrator.
You said that Windows treats this account differently; how exactly? How does that affect the usage of Microsoft accounts?
The built-in Administrator is intended primarily for system administration and recovery. It runs with elevated behaviors; Windows Setup normally disables it and creates a separate local account that belongs to the Administrators group.
That is why I wanted to identify the account type before interpreting the missing Microsoft-account option. If the SID does not end in -500, this distinction does not explain the problem.
“The locked account under Email & accounts can be stored only for Microsoft apps, so it does not necessarily mean you use that account to sign in to Windows.”
Windows maintains two separate relationships:
- Settings > Accounts > Your info identifies the account used to sign-in to the Windows profile.
- Settings > Accounts > Email & accounts can contain additional accounts used by Microsoft Store, Mail, OneNote, and other applications.
Therefore, Windows can display Local Account under Your info while retaining a Microsoft account under Email & accounts for application sign-in. The presence of the locked account there did not necessarily mean that it was being used to sign in to Windows.
“If the Microsoft account connects correctly in the new profile, the original profile’s account linkage is likely damaged." If this statement is true, how come the login worked?
That statement was conditional: if the account worked in a new profile but failed only in the original profile, profile-specific damage would have been likely. However, the account also failed in the new profile, so that condition was never met.
Since sign-in worked after you removed the passkey and reset the password, the evidence now points more toward an authentication or sign-in-method issue than Windows profile corruption. However, I cannot confirm whether the passkey itself, the previous password, or the temporary sign-in restriction was the exact cause.
Based on the successful sign-in, I do not see evidence of a remaining profile problem or a threat to the working account. The missing “Sign in with a Microsoft account instead” option appears to be a separate issue.