This user wasn't added to this PC. Code: 0xd0000225

Anonymous
2012-11-08T03:24:30+00:00

I am trying to add a new user and it says "We're sorry, but something went wrong. This user wasn't added to this PC. Code: 0xd0000225

Windows for home | Windows 11 | Settings

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2013-05-10T05:02:47+00:00

So, found the root cause of my particular problem. For some reason, the Security Packages that Microsoft Accounts use were not registered on my brand new (okay, refurbished) Lenovo laptop.  For the record, that's really, really unexpected, and I bet a re-install from shiny media, or a reset on a machine whose reference image is good, would fix this.  Oh, well, that's not an option for everyone.

Still, I've experienced this on two separate Lenovo laptops within a month, so there's probably something in common there.  Maybe the Windows image Lenovo customized got corrupted, maybe it's the AV trial s/w that comes with it is removing the regkeys, who knows?

Anyway, I just added "pku2u" and "livessp" to the Security Packages REG_MULTI_SZ key under regkey HKLM\System\CurrentControlSet\Control\Lsa. 

Immediately, I was able to add Microsoft Accounts. :)

(If you already have pku2u and livessp in the list of Security Packages, of course, then this isn't your problem, and just move on. ;)

CAUTION: Don't remove *anything* from the existing list in this key, and type very, very carefully.  If you really blow it when you edit this key, you can probably brick your PC, since the Local Security Authority (LSA) is core to the system.  There's a reason Microsoft tells you not to monkey with the registry.  You've been warned. ;)

Would be great if Microsoft could provide a Fix-It script that could safely fix this and eliminate the human factor of typing in regedit...

In the meantime, if you are comfortable with regedit, this might be something to check if you hit this problem.

Was this answer helpful?

0 comments No comments

56 additional answers

Sort by: Most helpful
  1. Anonymous
    2013-08-26T20:51:27+00:00

    Awesome fix, thank you!

    Was this answer helpful?

    0 comments No comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  3. Anonymous
    2013-08-15T20:50:34+00:00

    So, found the root cause of my particular problem. For some reason, the Security Packages that Microsoft Accounts use were not registered on my brand new (okay, refurbished) Lenovo laptop.  For the record, that's really, really unexpected, and I bet a re-install from shiny media, or a reset on a machine whose reference image is good, would fix this.  Oh, well, that's not an option for everyone.

     

    Still, I've experienced this on two separate Lenovo laptops within a month, so there's probably something in common there.  Maybe the Windows image Lenovo customized got corrupted, maybe it's the AV trial s/w that comes with it is removing the regkeys, who knows?

     

    Anyway, I just added "pku2u" and "livessp" to the Security Packages REG_MULTI_SZ key under regkey HKLM\System\CurrentControlSet\Control\Lsa. 

     

    Immediately, I was able to add Microsoft Accounts. :)

    (If you already have pku2u and livessp in the list of Security Packages, of course, then this isn't your problem, and just move on. ;)

     

    CAUTION: Don't remove *anything* from the existing list in this key, and type very, very carefully.  If you really blow it when you edit this key, you can probably brick your PC, since the Local Security Authority (LSA) is core to the system.  There's a reason Microsoft tells you not to monkey with the registry.  You've been warned. ;)

     

    Would be great if Microsoft could provide a Fix-It script that could safely fix this and eliminate the human factor of typing in regedit...

     

    In the meantime, if you are comfortable with regedit, this might be something to check if you hit this problem. 

    Derek, THANK YOU so much. Worked as well for my new refurbished Lenovo. Just had to restart my computer after the change (also put them in the same order as user maximumcap, just in case)...

    I recommend this for everyone else to try - you can always restore your system afterwards, so give it a shot. ;)

    Yeah .  . worked for me too!  Thanks for the help.  Both Lenovo and Microsoft wanted to charge me $100 for that little bit of info.  And I just bought the Yoga as a refurb.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2013-07-31T16:19:04+00:00

    Derek,

    Thank you for this post. This information was helpful. I had the same issue on a refurbished Lenovo IdeaPad Yoga 13 and your suggestion corrected the problem.

    -Steve

    Was this answer helpful?

    0 comments No comments