Where this project stands, and the safety work behind it #1
SysAdminDoc
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
DisableDefender does what the name says: disables or removes Microsoft Defender on Windows 10 and 11, with the firewall left alone. CLI and a WPF GUI, and everything it does is built to be reversible.
Reversibility is where the recent releases went. Safe Mode removal is now transactional, so an interruption mid-operation leaves you in a recoverable state instead of a half-removed one. ACL recovery fails consistently instead of half-succeeding. The artifacts the tool persists for restoration are now versioned and hardened, because a restore file you can't trust is worse than none.
Two roadmap items worth knowing about: releases will be built and gated from a clean checkout, and declared PowerShell 7 compatibility is getting restored rather than quietly dropped.
A tool like this lives and dies by Windows edition coverage, and LTSC, Home, and domain-joined machines all behave differently. The pinned thread next to this one is for reporting what edition and build you ran it on and whether disable and restore both held. That map is worth more than any feature.
All reactions