Installing and removing GuardianBlock.
Setup is an ordinary signed Windows wizard — no terminal, no scripts to paste. Turning protection off goes through the same accountability you set up, so this is the honest model for both, including what a local administrator can still do.
A signed wizard, not a script.
GuardianBlock installs the way any normal Windows app does. You never open a terminal, run PowerShell, or hand-edit the registry to set it up.
Download the signed installer
You get a single signed setup file, GuardianBlockSetup.exe — not a command to copy or a script to run.
Run the guided wizard
A standard Windows setup wizard walks you through it. There are no config files to edit and no registry steps to follow by hand.
Approve the normal Windows prompt
Setup uses the same Windows permission prompt any installer does. We never ask for or store your Windows administrator password.
Choose your accountability partner
During setup you pick the keyholder who authorizes sensitive changes later. Protection is something you opt into with someone you trust.
Downloads are invite-only during the private beta. Joining the waitlist is how you request access.
Turning protection off is accountable, not a hidden switch.
There is a supported way to stop protection — and it runs through the accountability you chose, rather than a quiet toggle you can flip alone in a weak moment.
An approved, single-use authorization
Deactivation happens through an approved deactivation authorization that works once. It is a signed, local authorization — not a setting you switch on your own.
Partner-accountable
Your keyholder is part of the loop, so turning protection off is a change someone you trust can see — the way you set it up to work.
Cooling-off and recovery
The model includes a deliberate cooling-off period and a recovery path, so no one ends up permanently locked out and no decision is purely in-the-moment.
What a local administrator can still do.
GuardianBlock is built on durable friction and accountability, not an impossible lock. If you keep local administrator rights on your PC, the honest truth is simple: a local administrator can ultimately remove or bypass installed software, including GuardianBlock.
Removing it outside the supported path isn't silent
Force-removing protection outside the supported authorization can weaken your device's protection health rather than cleanly end it.
Your partner can see protection health change
Because your accountability partner sees protection health and tamper signals — never your browsing — a removal like that is designed to surface as a partner-visible alert.
Two honest postures
GuardianBlock is strongest when an administrator installs it and the protected adult runs day to day without local admin. If you keep local admin, you get friction and accountability rather than a hard lock.
No remote control over your machine.
The Windows service is a local protection engine. It is built so that no one — including us — can quietly reach into your computer.
No remote uninstall
There is no server-side command that removes GuardianBlock from your machine.
No remote shell or server scripts
The service does not accept remote commands or server-provided scripts to run on your PC.
No reusable unlock secret
A deactivation authorization is single-use. There is no master password or reusable code that quietly switches protection off.
How the rest of the model fits together.
How GuardianBlock works →
The mechanism end to end — the app, your keyholder, and asking for an exception.
GuardianBlock on Windows 11 →
Windows scope, the two honest postures, and what the installer does.
Privacy summary →
What your accountability partner can and can never see.
Frequently asked questions →
Common questions about setup, removal, and accountability.
Last reviewed: 2026-06-28