Harden Windows Safely, Securely using Official Supported Microsoft methods and proper explanation | Always up-to-date and works with the latest build of Windows | Provides tools and Guides for Personal, Enterprise, Government and Military security levels | Read The Rationale https://github.com/HotCakeX/Harden-Windows-Security/blob/main/Rationale.md
Added a new policy to the Microsoft Defender Category, called BruteForceProtectionLocalNetworkBlocking. It Extends brute-force protection coverage in Microsoft Defender Antivirus to block local network addresses.
Removed Controlled Folder Access Exclusion List display from the Compliance checking results. Its Compliant property was always set to N/A since it never participated in the final security score and its only purpose was to show the file paths that exist in the exclusion list, nothing else. The exclusions list can be viewed in the Microsoft Defender's GUI or on the command line with PowerShell, if needed. With this change, there is no longer any items in the compliance check results with N/A Compliant value, they are either True or False.
Improved the auto-updating mechanism.
Changed the History for the PIN Complexity policy from 3 to 1. Related
Empty log messages that only have timestamps are no longer displayed on the console or on the GUI.
Fixed a visual issue where you would start the compliance check, then switch to another tab such as protection page, and while in there, the compliance check would finish, but after switching back to Confirmation page, the total count of the items wouldn't be shown. Related
Added 2 toggle buttons to the compliance checking page in the GUI to filter the displayed results based on Compliant/Non-Compliant status.
Added an area in the confirmation page's GUI to display the live number of displayed results. Updated in real time during filter application and keyword searches.
Overall code optimization and categorization.
Increased minimum OS build requirement from 22621.3155 to 22621.3880. As already explained numerous times throughout this repo, keeping your OS up to date is the most important thing. The main reason for this change is the new Microsoft Defender features added in this update.
What's New
Added a new policy to the Microsoft Defender Category, called BruteForceProtectionLocalNetworkBlocking. It Extends brute-force protection coverage in Microsoft Defender Antivirus to block local network addresses.
Removed Controlled Folder Access Exclusion List display from the Compliance checking results. Its
Compliantproperty was always set toN/Asince it never participated in the final security score and its only purpose was to show the file paths that exist in the exclusion list, nothing else. The exclusions list can be viewed in the Microsoft Defender's GUI or on the command line with PowerShell, if needed. With this change, there is no longer any items in the compliance check results withN/ACompliant value, they are either True or False.Improved the auto-updating mechanism.
Changed the History for the PIN Complexity policy from 3 to 1. Related
Empty log messages that only have timestamps are no longer displayed on the console or on the GUI.
Fixed a visual issue where you would start the compliance check, then switch to another tab such as protection page, and while in there, the compliance check would finish, but after switching back to Confirmation page, the total count of the items wouldn't be shown. Related
Added 2 toggle buttons to the compliance checking page in the GUI to filter the displayed results based on Compliant/Non-Compliant status.
Added an area in the confirmation page's GUI to display the live number of displayed results. Updated in real time during filter application and keyword searches.
Overall code optimization and categorization.
Increased minimum OS build requirement from 22621.3155 to 22621.3880. As already explained numerous times throughout this repo, keeping your OS up to date is the most important thing. The main reason for this change is the new Microsoft Defender features added in this update.