Every Way to Remove the Ctrl Alt Del Requirement and How to Undo Each One
There are three doors to the same switch: a checkbox, a security policy and a registry value. This page lays them side by side, tells you which ones your edition of Windows actually has, and gives the exact undo for each — before you change anything.
✍️ Technical Anshu🪟 Windows 10 / 11⏱️ 7 minute read
🎥 Watch the video for the visual walkthrough, then use this page as the checklist
Guides usually show one method and disappear. That is fine until the method is missing on your PC — no secpol.msc on Windows Home, a greyed-out checkbox under a domain policy — or until you want to undo the change six months later and cannot remember how it was made. So this page documents all three routes completely, with their reversals, and the honesty rule that matters most: whichever route you use to switch it off, use the same route to switch it back on, because each writes the same underlying setting and mixing routes is how PCs end up in confusing half-states.
Domain Group PolicySet by IT, wins over all local routes
Undo = walk the same route backwardsRule
👆 Pick the first route your edition offers. If a domain policy exists, none of the local routes will hold — see the note at the end.
1
Route One — netplwiz (Works on Every Edition)
Press Windows + R, type netplwiz, press Enter
Select the Advanced tab
Under Secure sign-in, untick Require users to press Ctrl+Alt+Delete → Apply → OK
Undo: open netplwiz again, tick the same box, Apply, OK
If the Advanced tab section is missing or greyed out, a policy is controlling this PC — skip to the last section of this page before forcing anything
2
Route Two — Local Security Policy (Pro, Enterprise, Education)
Press Windows + R, type secpol.msc, press Enter
Navigate to Local Policies → Security Options
Open Interactive logon: Do not require CTRL+ALT+DEL and set it to Enabled — read it twice, because the setting is named from the opposite direction: Enabled means the requirement is removed
Undo: set it to Disabled to force the requirement on, or Not Configured to hand control back to the Windows default for that machine type
Windows Home does not include this console. That is normal, not a fault — use route one or three
3
Route Three — The Registry Value (Every Edition, Most Direct)
First, protect yourself: open regedit, select the key below, and use File → Export to save a backup of it
Undo: set the value to 0, or delete DisableCAD completely to return to default behaviour. Restart after registry changes so you test a clean sign-in
4
When None of the Routes Stick — a Policy Is Above You
If your change works for an hour and then the requirement returns, the PC is almost certainly domain-joined or managed. Group Policy refreshes roughly every 90 minutes and re-applies the setting from above
Check what is being applied: run gpresult /r in a Command Prompt and look at the computer policies listed
On such a machine the honest answer is that the change is not yours to keep. The administrator set it deliberately, and a separate page in this series covers why it should stay on there
Fighting a domain policy with local tricks wastes your time and can breach your organisation's rules — ask IT if you have a genuine need, for example an accessibility reason, which IT departments handle routinely
🔴 One warning about registry downloads: never import a ready-made .reg file from a random site to make this change. The value above is one line you can type and verify yourself — a downloaded file can change ten other things you never see. Type it, check it, keep your own backup.
🎥 Watch the Complete Process in the Video
The video demonstrates the removal on screen — match its steps against the routes listed here.
The netplwiz checkbox, because it needs no registry editing and undoes itself with the same tick. If the checkbox is unavailable, the DisableCAD registry value is the fallback. Windows Home has no secpol.msc console, so the policy route simply does not exist there.
I set DisableCAD to 1 but the PC still asks for Ctrl Alt Del. Why?
Two usual causes: the PC was not restarted or signed out after the change, so the old behaviour is still loaded; or a domain or local policy is set to require it and overrides the plain registry value. Check with gpresult /r whether a policy is applying, and check the security option in secpol.msc if your edition has it.
Does it matter if I turn it off with one route and back on with another?
It can leave you confused, because all three routes write related settings and the effective result is whatever Windows resolves last. Pick one route, note it down, and reverse that same route. If the state is already muddled, set the security policy explicitly to Disabled, which states the requirement plainly, then test.
This guide is based on a Technical Anshu video • Stuck on a step? Ask in the video comments — answers happen there 🙏