Microsoft Family Safety not updating: what to check and fix
If Microsoft Family Safety is not updating, the usual cause is a sync delay or a mismatch between the child’s account and the device you’re checking. Start by confirming the child is signed into the right Microsoft account on the right device, then make sure the device is online and give Family Safety time to refresh before you change settings. If the family link looks wrong or the app stays stale after those checks, re-add the child account or contact Microsoft support.
What you’ll usually see
You may notice old screen-time totals, activity reports that stop changing, or app and website limits that look as if they never took effect. On the child’s device, the old status can stay visible even after you changed a setting in the family dashboard.
In many cases, nothing is actually missing. Screen time, app limits, and activity reports can arrive late, especially if the device was offline, recently restarted, or just changed networks. The key is to tell the difference between delayed reporting and a broken account link before you make bigger changes.
Before you start
- Confirm the child is signed into the Microsoft account that belongs to your family group, not a school account, guest profile, or another personal account.
- Confirm the child is using the right device, since Family Safety changes only show up on the account and device that are actually linked.
- Make sure the device is online before you expect new activity or limit changes to appear.
- Keep in mind that the Family Safety app or web dashboard may need a brief refresh before it shows current information.
If the child was recently handed a different device, signed in under another account, or moved between accounts, check that relationship first. A mismatch there can make it look as if Family Safety is broken when the problem is really the account you’re watching.
Try these fixes in order
- Check the child’s Microsoft account on the device.
Open the child’s device and confirm that the signed-in Microsoft account is the one you manage in the family group. If the device is using a different Microsoft account, switch to the correct one first.
After the account is corrected, wait a little while for the device to reconnect and report back.
- Confirm the device is online.
Open a webpage or another online app on the child’s device. If it cannot reach the internet, fix the connection before expecting Family Safety to update.
A device that is offline, or only partly connected, can leave the dashboard showing old limits or stale activity.
- Refresh Family Safety and wait briefly.
Close the Family Safety app completely, reopen it, and refresh the web dashboard if you use the browser version. If the parent side still shows stale data, sign out and sign back in so it can pull fresh information.
Then wait a short time before checking again. Screen-time totals, activity reports, and limit changes can lag behind the moment you set them.
- Restart the child’s device if the data still hasn’t moved.
If the account is correct and the device is online but the dashboard still shows old information, restart the child’s device. That can clear a stuck sync state without changing your family settings.
After the restart, open the device normally and check whether the new status appears.
- Check whether the family group is still linked correctly.
If the dashboard and device still disagree after the earlier steps, the child may no longer be linked to the family group the way you expect. Recheck the family relationship before you assume the limits themselves failed.
If the child account no longer appears to be linked correctly, re-adding the child can fix the connection. Only do that after you have confirmed you are working with the right Microsoft account, since removing and re-adding the wrong one can add more confusion.
Re-adding the child account can change the family relationship and may require you to set up limits again. Stop there and contact Microsoft support if you’re not sure which account is linked or if settings keep reverting after you restore the link.
How to tell whether it’s actually working
The fix has likely worked when the dashboard and the child’s device start agreeing again.
Look for these signs:
- New activity appears with a current timestamp instead of stopping at an older time.
- Screen-time totals move forward after the child uses the device.
- App or website limits take effect on the child’s device instead of showing the previous setting.
- The family dashboard matches what you see on the device after a refresh.
If you changed a limit, give it a reasonable amount of time to sync before testing it. If the dashboard still shows old status after the device is online, on the right account, and refreshed, the problem is more likely the account link than the setting itself.
When to stop troubleshooting and ask for help
If the child is signed into the right Microsoft account, the device is online, the app or dashboard has been refreshed, and the family link still looks wrong, it’s time to escalate. Contact Microsoft support if limits keep reverting, activity never appears, or you can’t tell which account is tied to the family group.
If the family group and child account do not look linked correctly, re-adding the child is the last self-service step worth trying. If that still doesn’t restore current status, stop there and let Microsoft support check the account and sync side from their end.
Conclusion
If Family Safety still isn’t updating after those checks, don’t keep changing settings at random. Confirm the account link, then contact Microsoft support.
Frequently Asked Questions
Should I remove and re-add the child account right away?
No. First confirm the child is signed into the right Microsoft account, the device is online, and the app or dashboard has had time to refresh. Re-adding the child is a later step when the family link itself looks wrong.
Why do limits show on the dashboard but not on the child’s device?
That usually means the device hasn’t synced yet, is offline, or is signed into a different Microsoft account. Check those basics before assuming the limit failed.