Forum Discussion

kptZima's avatar
kptZima
Copper Contributor
Sep 30, 2026

Family Safety: child PC registered but not connected (Event ID 454, 0x86000002)

Hello,

I am reporting a persistent Microsoft Family Safety device-association issue on a newly configured Windows 11 Home PC.

Microsoft Support case reference: 7109577064

Microsoft Support has confirmed that the standard consumer-support troubleshooting path has been exhausted and specifically advised me to post the full technical scenario in Microsoft Tech Community.

Environment

  • Windows 11 Home 25H2
  • OS Build: 26200.9550
  • Update: KB5124010
  • Newly configured PC
  • Child uses a Microsoft consumer account based on an external email domain: OP.pl

No email addresses or personal account identifiers are included in this public post.

Problem

The PC is correctly registered under the child’s Microsoft account and is continuously visible at:

account.microsoft.com/devices

However, Microsoft Family Safety still shows:

No connected Windows device

So the Microsoft Account device registration works, but the Family Safety device association does not.

Configuration already verified

  • Child account is a Standard User, not Administrator.
  • Child is correctly added to the Microsoft Family group.
  • Parent account is the Family Organizer.
  • Parental consent is correctly granted.
  • Windows activity reporting is enabled.
  • Windows Settings → Accounts → Family shows that the child can sign in.
  • FamilySafetyRefreshTask exists and completes successfully with result 0x0.
  • Manual execution of:

schtasks /run /tn "\Microsoft\Windows\Shell\FamilySafetyRefreshTask"

returns SUCCESS.

  • WpcMonSvc is running.
  • wlidsvc is running.
  • AppIDSvc is running.
  • dsregcmd /status reports:

WamDefaultSet : YES

WamDefaultAuthority : consumers

and the Microsoft consumer account is correctly detected.

Troubleshooting already completed

  • Child Windows profile was switched temporarily to a local account and then reconnected to the same Microsoft account.
  • Child Windows profile was later completely removed from the PC and recreated from scratch.
  • Microsoft Family Safety for Windows was installed.
  • Microsoft.Windows.CloudExperienceHost was reset with PowerShell.
  • DNS cache was flushed.
  • PC was tested using a different Internet connection / mobile hotspot.
  • Windows was fully updated to 25H2 build 26200.9550.
  • Child was completely removed from the Microsoft Family group.
  • Parental consent was revoked.
  • Child was invited again to the Family group.
  • Parental consent was granted again.
  • The recreated family relationship synchronized immediately between the Family Safety web interface and the mobile app.
  • FamilySafetyRefreshTask was run again after recreating the family relationship.

The issue persists.

Additional symptom

Under:

Settings → Accounts → Connected devices

the child profile behaves inconsistently.

The PC appeared there once after recreating the Windows profile, but after restarting Windows the local Connected devices list became empty again.

However, the PC remains continuously visible under the child account at account.microsoft.com/devices, which indicates that the cloud device registration itself is persistent.

Event Viewer findings

In:

Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin

historical events from 27 September 2026 show:

Event ID: 454

Enrollment Type: FamilySafety

CSP: AppLocker

Path:

./Vendor/MSFT/AppLocker/FamilySafety/FamilySafetyGroup

Error:

0x86000002

After recreating the Microsoft Family relationship, granting parental consent again, and manually running FamilySafetyRefreshTask, no new FamilySafety-related events are generated in this log.

What is confirmed to work

  • Microsoft account authentication
  • Windows user profile
  • Microsoft Family group membership
  • Parental consent
  • Windows device registration under the child’s Microsoft account
  • Family Safety activity reporting configuration
  • Synchronization between Family Safety on the web and the mobile app

The remaining failure appears to be specifically:

child Microsoft account → Microsoft Family group → registered Windows device → Family Safety device association

Microsoft Support could not escalate the case further through the consumer-support channel and instructed me to post the issue here.

Microsoft Support case reference: 7109577064

I would appreciate input from Microsoft engineers, moderators, or anyone who has encountered this exact issue, especially in relation to:

  • Event ID 454
  • error 0x86000002
  • AppLocker/FamilySafety/FamilySafetyGroup
  • device visible in account.microsoft.com/devices but missing from Microsoft Family Safety

I can provide additional Event Viewer logs, screenshots, dsregcmd /status output, or other diagnostic information if required.

 

3 Replies

  • LIUV's avatar
    LIUV
    Copper Contributor

    Same here, very interested by the answer

  • rafalek_pl's avatar
    rafalek_pl
    Copper Contributor

    I have the same Microsoft Family Safety device-association issue.

    Current system: Windows 11 Pro, version 26H2, OS build 26300.9711 (October 13, 2026 update, KB5127648).

    My child's PC (ANT-PC) is visible under the child's Microsoft account at account.microsoft.com/devices, but Family Safety still reports "No connected devices".

    Event Viewer logs Event ID 454 with error 0x86000002:

    • Enrollment Type: FamilySafety
    • CSP: AppLocker
    • URI: ./Vendor/MSFT/AppLocker/FamilySafety/FamilySafetyGroup
    • Command: Clear (first phase of Delete)

    Troubleshooting already performed:

    • Confirmed the child is a standard Windows user and a member of the Microsoft family group.
    • Enabled activity reporting.
    • Recreated the family relationship as instructed by Microsoft support.
    • Installed the Microsoft Family Safety app from the Microsoft Store.
    • Reset Microsoft.Windows.CloudExperienceHost successfully.
    • Ran FamilySafetyRefreshTask and FamilySafetyMonitor; both completed with LastTaskResult = 0.
    • Started AppIDSvc and WpcMonSvc; both run successfully.
    • Verified that the PC is visible on the child's Microsoft account devices page.
    • Checked the local AppLocker policy; it contains zero rule collections, and the AppLocker folder is empty.

    The issue persists after restarting the PC and repeating the connection steps.

    Has anyone found a confirmed fix for this specific error? Could Microsoft investigate whether the FamilySafetyGroup policy configuration or device association is failing?

    I would appreciate a reproducible fix rather than the standard instructions to sign in, restart, or re-add the child account.