Family Link - unable to add child PC. Error: "Oops, something went wrong..."

Tim091 0 Reputation points
2026-09-14T08:53:10.6333333+00:00

I have two devices added to Family Link for my son and can view activity etc. perfectly well.

I am trying to add a third following the instructions (on my PC):

  1. Settings - Accounts - Family - Your Family - Sign in
  2. Sign in with my Microsoft account is Okay
  3. Next dialogue is:
    230kxu2z
  4. I assume that this means the password I use to sign in to my PC (?? If not then I don't have a "Windows password").
  5. Entering my "Windows password" results in:
    04pdym4o

I raised it with Microsoft Support who told me it was a problem with the child's Microsoft account, which is obviously rubbish as 1) I can view his other devices okay, and 2) his account has no relevance on the above steps.

I don't sign into my PC with a Windows account, it is a local admin account, but that didn't stop me adding his previous devices. I have no intention of using my Microsoft account to log in to a PC.

Any ideas welcome!

Windows for home | Windows 11 | Family and online safety
0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-09-14T08:53:32.01+00:00

    For Family Safety, the child’s device must be connected through the child’s Microsoft account on that Windows PC. The supported path is not to convert the parent’s local admin sign-in to a Microsoft account.

    Use this setup on the child’s PC:

    1. Sign in on the PC with the child’s profile.
    2. Open Start > Settings > Accounts.
    3. Check whether the child is signing in with a Microsoft account.
      • If not, select Sign in with a Microsoft account instead and use the child’s Microsoft account.
      • If an email address is already shown, that is the account that should be in the family group.
    4. On the parent/admin side of that PC, go to Settings > Accounts > Family & other people.
    5. Under Your family, select the child and then select Allow.
    6. Make sure the child account is a Standard user, not Administrator.
    7. Have the child sign in. After that, the device should appear in the child’s connected devices.

    If Family Safety still does not recognize the device:

    1. Re-check that the child is still listed under Settings > Accounts > Family / Family & other users.
    2. In the child profile, complete any Microsoft account verification prompt if shown.
    3. Sign out of the child profile, restart the PC, and sign back in with the child account.
    4. Allow time for sync. A registered device can take up to 24 hours to appear.

    Important limits from Microsoft:

    • Non-Surface Windows 11 devices are added automatically when signed in; they are not manually added by serial number.
    • If the PC is managed by a company or organization, it cannot be registered to a personal account.
    • Family features may not work properly if the child account is set as administrator.

    The dialog shown is trying to switch that Windows sign-in to a Microsoft account on the current PC. That is separate from the documented Family Safety device-connection flow, which is based on the child account being added to the PC and signing in there.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Kai-H 26,840 Reputation points Microsoft External Staff Moderator
    2026-09-14T14:03:38.17+00:00

    Hi, Tim091

    The screenshots show that Windows is trying to convert the current local administrator profile into a Microsoft account. The “Current Windows password” means the local account password, not the Microsoft account password or Windows Hello PIN.

    Here are some suggestions you can try:

    If the local account has never had a password and Windows normally signs in using only a PIN, leave Current Windows password completely blank and select Next. This has resolved the same prompt for other local-account users.

    If the error remains and the PC runs Windows Pro, press Windows key + R, enter secpol.msc, then open Local Policies > Security Options > Accounts: Block Microsoft accounts. Set it to This policy is disabled, restart Windows, and try again. It is recommended that you check this because the policy can block Microsoft-account authentication while showing only the generic “Oops” message.

    Also try the process from a newly created local administrator profile. If it works there, the original Windows profile’s saved account credentials are likely damaged.

    None of these steps requires using the Microsoft account as the normal Windows login.

    Thank you for your patience in reading, I hope this information has been helpful to you. 

    If the answer is helpful, please click "Yes" and kindly upvote it. If you have extra questions about this answer, please click "Comment."    

    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.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.