hmm why go back a decade for tools? defender can be uninstalled just fine online with simple 20ish lines of powershell example guess just setting $name = 'Windows-Defender' above would take care of application-guard stuff as well basically adding a Visibility 1 property and removing Owners subkey it's all it takes to "unlock" it did not test offline images as I no longer waste time doing that, but it should be easier I personally don't see the value in nuking defender completely. lets say using a 3rd party solution - well those often can break, it does not hurt to have a backup plan, specially when it does not waste any resources and does not update when toggled off - via ToggleDefender.bat / copy-pastable in powershell, of course
It's difficult, and beyond my ability. That's why 7Customizer becomes a workaround - zhanglin has the tutorial, I think.
Thank you very much, mate. But I don't know PowerShell, a headache only. Back to topic. We were talking 'bout the Windows Defender infrastructure of 21354.1 (not the old 7Customizer which zhanglin is interested in and asked me to lend him a hand), which has been incorporated in Client-Desktop-Required-Package03, and therefore no more uninstallable. Our conversation started from #2262. https://forums.mydigitallife.net/th...struction-project.80939/page-114#post-1654384
I don't think zhanglin can be of any help since our English level is 'round 50 50. Group policy is appropriate for latest builds I reckon so. Wait for his answer anyway. See you.
alpha builds have defender more splatted, got it. will try it out as well in 1-2 months when it's not as trash as atm
Dear friend @xinso I will wait, anyway, my english is very poor too, because my first language is portuguese, but I count that our good friend "google translator" could help us always... lol... I will try to use the Sophia PS Script to see what happens on my VMWare Win10 19043.906.210323-1515.21H1 ... Great hug and thanks for your good job always. Best computing. Regards @JeepWillys58
I have created Defender.xml, but using xml-Remove.cmd, the following prompt appears, and the result is not removed. (Real-time protection is disabled) These prompts appear in xml-Remove.cmd
Failed https://forums.mydigitallife.net/th...struction-project.80939/page-114#post-1654442 Succeeded https://forums.mydigitallife.net/th...struction-project.80939/page-114#post-1654449 Wildcards "Defender" includes "Windows Defender Application Guard" which is NOT Windows Defender.
Some of SystemApps can be created and removed, and some cannot create XML. It is estimated that it is related to the naming of components in xml-Ceate.txt. Regarding xml-Ceate.txt, what are the requirements for content creation? Such as FileExplorer, FilePicker, etc., I have thought of many methods, but I can't create XML.
xml-Remove.cmd can only remove a single xml at present, how to modify it to remove multiple xmls at once?
Try one by one firstly. Then try all at a time. Finally drag and drop all xml to dnd_merge.cmd to form 1 xml.