Hello x BlueRobot, Thanks for inviting me to set up this new thread.
Yesterday I used Windows Update in the typical manner, to install Feature Update 1909. Upon completion, I discovered that my Windows 10 Pro (32-bit) Lenovo T400 laptop now has a duplicate login name. The original login ID includes an image in a circular frame, as it always has, the new, duplicate login image is in a square frame.
I have read all of the conversation on thread
duplicate-user-accounts-after-upgrading-to-windows-10.30249, looking for clues, and while I now have one such clue from doing this, none of the suggested methods in that thread have solved my problem. Note that like member Nat, I have never installed a Microsoft account on this machine, and I have never used auto login at any time since Windows 98 was popular. Also, I have never had more than one account on this machine, and I have never attempted to set up auto login, because sometimes I travel with this laptop.
As an experiment, I tried creating a second account, since removed. As I expected, this process also created a duplicate login name, such that there were now four login names on my login screen, so whatever is causing this is now built right into my OS. Ultimately, I would like to not only get rid of the duplicate name that exists, but resolve the issue of having to perform some sort of back end fix every time I create a user account on this or any other similarly-afflicted machine.
As to the clue I found yesterday, I ran
wmic useraccount list full >"%userprofile%\Desktop\UserAccountDetails.txt"
which contained no surprises, then I opened the registry and took a look at
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\Credential Providers
Among the entries there, I noticed that under Credential Provider
{D6886603-9D2F-4EB2-B667-1971041FA96B}
which identifies Microsoft's Multifactor Unlock object,
there was an SID that didn't appear in the 'wmic useraccount' generated file.
The SID associated with my user account is:
S-1-5-21-3277786686-3406506481-3083301811-1000
and under the CLSID above, it shows
LogonCredsAvailable REG_DWORD 0x00000000(0)
There is also an undocumented SID, with no account name and no entry in the 'wmic useraccount' generated file:
S-1-5-21-3277786686-3406506481-3083301811-1005
and under the CLSID above, it shows
LogonCredsAvailable REG_DWORD 0x00000002(2)
At this point, I feel a bit like a patient making diagnosis suggestions to the doctor, but that's the only anomaly that I found after some hours of prowling around and not touching anything. Even if this
is relevant, I am not certain as to what I should do about it. I look forward to your reply and suggestions.
