Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Security Apps
VoodooShield
DefenderUI by VoodooShield - Turn on Hidden Security Features of Microsoft Defender
Message
<blockquote data-quote="danb" data-source="post: 1087029" data-attributes="member: 62850"><p>Hey Guys,</p><p></p><p>Here is the initial beta of DefenderUI Pro. If anyone is running CyberLock and wants to try this beta, you can always uninstall CyberLock, and just choose to not remove the settings and logs, then uninstall DefenderUI Pro later and reinstall CyberLock. I am curious to see if anyone thinks we should add the WDAC Lockdown feature to CyberLock. It really is not necessary, but it would not hurt to add WDAC Lockdown to CyberLock.</p><p></p><p>I am still not a huge fan of WDAC, but a lot of people swear by it, so I figured we would make a user-friendly, automated version of it. A good kernel mode driver like the one DefenderUI Pro and CyberLock uses is much more flexible, and allows developers to do tons of things they could never do with WDAC.</p><p></p><p>The WDAC Lockdown factory default policies were generated from the Microsoft WDAC Wizard are stored here: C:\Program Files\DefenderUI\Policies. Then there are also user customizable policies that are stored here: C:\ProgramData\DefenderUI\Policies. If any of the factory default policies are modified, then the user customizable policies are automatically deployed. But if there are not user customizable policies, then the factory default policies are deployed.</p><p></p><p>The WDAC Lockdown feature also includes a modified version of the Microsoft WDAC Wizard, and this modified version makes it super simple to create and modify policies for WDAC Lockdown.</p><p>If you do use the WDAC Lockdown feature, it would be best to start in Training mode for a day or so. There are only four folders that are automatically whitelisted by the factory default policies.</p><p></p><p>C:\Program Files\</p><p>C:\Program Files (x86)\</p><p>C:\WindowsApps\</p><p>C:\XboxGames\</p><p></p><p>We could have whitelisted other folders as well, but as you are aware, that can be dangerous. Besides, with the new WDAC Lockdown usability features, anything that needs to be whitelisted is automatically whitelisted, and that way we do not have to whitelist entire potentially dangerous directories. We might end up tweaking the factory policies a little, but it is probably best to stick with the policies that are recommended by Microsoft.</p><p></p><p>There are probably a few things that we need to tweak or fix, so if you guys find anything please let me know!</p><p></p><p>DefenderUIPro 1.18</p><p>[URL unfurl="true"]https://defenderui.com/Download/InstallDefenderUIProbeta118.exe[/URL]</p><p>SHA-256: 7dc488692ccafcca67777a5d72be2b4d6c5eb75f607fe1127200c65622fe198c</p><p></p><p></p><p>Have a great weekend!</p><p></p><p>Dan</p></blockquote><p></p>
[QUOTE="danb, post: 1087029, member: 62850"] Hey Guys, Here is the initial beta of DefenderUI Pro. If anyone is running CyberLock and wants to try this beta, you can always uninstall CyberLock, and just choose to not remove the settings and logs, then uninstall DefenderUI Pro later and reinstall CyberLock. I am curious to see if anyone thinks we should add the WDAC Lockdown feature to CyberLock. It really is not necessary, but it would not hurt to add WDAC Lockdown to CyberLock. I am still not a huge fan of WDAC, but a lot of people swear by it, so I figured we would make a user-friendly, automated version of it. A good kernel mode driver like the one DefenderUI Pro and CyberLock uses is much more flexible, and allows developers to do tons of things they could never do with WDAC. The WDAC Lockdown factory default policies were generated from the Microsoft WDAC Wizard are stored here: C:\Program Files\DefenderUI\Policies. Then there are also user customizable policies that are stored here: C:\ProgramData\DefenderUI\Policies. If any of the factory default policies are modified, then the user customizable policies are automatically deployed. But if there are not user customizable policies, then the factory default policies are deployed. The WDAC Lockdown feature also includes a modified version of the Microsoft WDAC Wizard, and this modified version makes it super simple to create and modify policies for WDAC Lockdown. If you do use the WDAC Lockdown feature, it would be best to start in Training mode for a day or so. There are only four folders that are automatically whitelisted by the factory default policies. C:\Program Files\ C:\Program Files (x86)\ C:\WindowsApps\ C:\XboxGames\ We could have whitelisted other folders as well, but as you are aware, that can be dangerous. Besides, with the new WDAC Lockdown usability features, anything that needs to be whitelisted is automatically whitelisted, and that way we do not have to whitelist entire potentially dangerous directories. We might end up tweaking the factory policies a little, but it is probably best to stick with the policies that are recommended by Microsoft. There are probably a few things that we need to tweak or fix, so if you guys find anything please let me know! DefenderUIPro 1.18 [URL unfurl="true"]https://defenderui.com/Download/InstallDefenderUIProbeta118.exe[/URL] SHA-256: 7dc488692ccafcca67777a5d72be2b4d6c5eb75f607fe1127200c65622fe198c Have a great weekend! Dan [/QUOTE]
Insert quotes…
Verification
Post reply
Top
