How FamilyProtect repairs itself if protection stops

FamilyProtect does not assume a device is safe because an installer ran once. It verifies four independent conditions around the clock, and if any one fails, it re-runs the full setup and repairs itself, usually within minutes, with nobody touching the PC. The scariest thing about any safety tool is not knowing whether it is still on. Here is how we take that worry off you.

Why does protection stop in the first place?

Software is not static. A Windows update restarts services. A well-meaning cleanup tool disables something. A background service crashes. None of it is dramatic, and none of it announces itself. On most parental tools, the result is the same: the thing you set up in March quietly stopped working in June, and you had no way to know.

That silent gap is the real risk. A tool that is off but looks on is worse than no tool, because you have stopped watching.

What does FamilyProtect check?

On every protected Windows PC, FamilyProtect continuously verifies four separate conditions, not just one:

1. The protection software is installed.
2. Its background service is running right now.
3. The locked configuration that forces filtered DNS is in place.
4. The certificate that lets block pages display cleanly is trusted.

Only when all four pass does your dashboard show the device as protected. If even one fails, the device shows as not protected. You see the true state per device, not a green tick left over from an install you ran last month. The full detail of what each check does is in how DNS Protection works on Windows.

What happens when a check fails?

It heals itself. When any of the four checks fails, FamilyProtect automatically re-runs the full deployment on that PC: it repairs the configuration, restarts the service, and reinstalls anything missing. The sequence is safe to run over and over, so a healthy device is never disturbed and a broken one is simply put back together.

In our live testing, a device we deliberately broke went from not protected back to protected within minutes, with no one touching it. That verify, detect, repair loop runs the whole time the protection is switched on.

Why not just tell me it broke and let me fix it?

Because a notification that says “protection stopped, please reinstall” puts the job back on you, at the exact moment you are least likely to act on it. Real repair means the default outcome is protected, not a to-do item in your inbox. You should not have to babysit a safety tool for it to keep working.

You can still see everything. When a device drops to not protected and comes back, that is visible in your dashboard, so you are informed without being made responsible for the fix.

Can my child use this to get around it?

No. The repair loop closes the exact gap a child might try to open. Turning the service off does not disable protection for long, because the next check notices and turns it back on. And a standard (non-admin) account cannot reach the settings that would stop it in the first place. The steps for keeping your child on a standard account are in installing FamilyProtect on a Windows PC.

What does this mean for me day to day?

Nothing to do, which is the point. You switch protection on once. After that, it is not a thing you maintain. It watches itself, fixes itself, and shows you the honest state if you ever want to look. When the toggle is off, the protection is removed just as cleanly.

Want protection that stays on without you checking? Get started.