Family safety doesn't work after upgrading to Windows 11

Hello! I had this problem and figured out a simple solution!

• Open Task Scheduler
• On the right sidebar go to Task Scheduler Library > Microsoft > Windows > Shell
• Inside of shell, there should be a task called “FamitySafetyMonitor” and “FamilySafetyRefresh”
• Right click on FamilySafetyMonitor and click run.
• Right click on FamilySafetyRefresh and click run.
• Double check the properties on each so that they run when the user logs in. I’m not sure why, but for me, running each one manually seemed to jumpstart the process and it now works on log on.

Hope this helps!

Michael

This is just outright shameful and should be prosecuted. Family safety features used to work just fine for my family as far back as 2 years ago. Since then I've been experimenting with different things like linux & small domain based on samba at home (I have 4 kids so managing their logins across 4 devices they were using for the so called remote schooling was a chore, let alone other things). Finally after having broken that setup recently I decided to go back to M$, buy licenses for the linux machines, install windows 10 on them and go back to family safety. Boy, how wrong was I to imagine a feature that worked perfectly fine 2 years ago will still work today. Here's things/combinations I have tried on two of my kids' computers:

1. freshly installed windows 10: 1 account got linked to both PCs, 1 account got linked to only 1 PC, 2 accounts didn't get linked to any of the PCs despite having followed the exact same set of steps for each of them, and that includes the somewhat acrobatic workaround that goes on about logging on, disabling access, failing to log on, enabling access, then logging back on succesfully and going to account.microsoft.com
2. upgraded win 10 to win 11 & repeated the above
3. installed win 11 fresh & repeated the above
4. removed all child accounts from family by removing consent, removed wife's account, then started family anew from her account by adding mine and one of the kids.

This is beyond ridiculous - either the product team behind Family Safety is the worst, most inane dev team in the world, or they're deliberately causing this situation to force people to pay for a product that used to be free & built into windows, but now they're asking money for it as part of 365 subscription. Frankly, I will sooner go back to linux & fix my samba domain than pay another penny to M$

Same issue here, I'm reverting to win 10.

Hello! I had this problem and figured out a simple solution!

• Open Task Scheduler
• On the right sidebar go to Task Scheduler Library > Microsoft > Windows > Shell
• Inside of shell, there should be a task called “FamitySafetyMonitor” and “FamilySafetyRefresh”
• Right click on FamilySafetyMonitor and click run.
• Right click on FamilySafetyRefresh and click run.
• Double check the properties on each so that they run when the user logs in. I’m not sure why, but for me, running each one manually seemed to jumpstart the process and it now works on log on.

Hope this helps!

Michael

+1 This worked for me!

It seems like there may be an issue with the "Custom Trigger" for the FamilySafetyRefresh task that causes it to not run, resulting in stale rules on the machine.

I am still having issues with this and rolling back to windows 10 is now an option. How can this be resolved?