Reply to thread

Message

<blockquote data-quote="Andy Ful" data-source="post: 755791" data-attributes="member: 32260">#4. Ransomware protection is the new name of CFA in Windows 10 ver. 1803#5. Use Admin account.#6. <a href="https://malwaretips.com/threads/use-windows-10-build-in-anti-execution-options.85477/page-4" target="_blank">Windows 10 - Use Windows 10 build-in (anti)execution options</a>I do not recommend you using SysHardener, until you will master H_C. Many SysHardener settings can do the same as H_C but in a different way, so if you will disable them in H_C, they will be still enabled by SysHardener, and in many cases, you will not know what to do. Also, SysHardener blocks are silent and there is no LOG to check what was blocked. SysHardener has not the &#039;back to Windows defaults&#039; feature, so you have to know very well Windows to do it. The &#039;back to Windows defaults&#039; feature is important because from time to time something goes wrong with Windows on non-default settings (usually one specific broken Windows Update).Setting UAC to deny elevation of unsigned will prevent using &#039;Run As SmartSreen&#039; which is the important feature of the default-deny H_C setup. [USER=50782]@Windows_Security[/USER] uses &#039;deny elevation of unsigned&#039; + &#039;Run as administrator&#039; for many years - this a good replacement for &#039;Run As SmartScreen&#039; for the advanced and cautious users who know the limitations of SmartScreen.Please, bear in mind that H_C setup is too restrictive for many people, and [USER=50782]@Windows_Security[/USER] setup adds many additional restrictions. Please, do not try to be the master of restrictions from the beginning. The masters like [USER=50782]@Windows_Security[/USER] are doing this for many years.My advice would be - the restrictions should be applied in accordance with the growing knowledge.<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite135" alt=":giggle:" title="Giggle&nbsp; &nbsp; :giggle:" loading="lazy" data-shortname=":giggle:" /><img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite130" alt="(y)" title="Thumbs up&nbsp; &nbsp; (y)" loading="lazy" data-shortname="(y)" /></blockquote>

[QUOTE="Andy Ful, post: 755791, member: 32260"] #4. Ransomware protection is the new name of CFA in Windows 10 ver. 1803 #5. Use Admin account. #6. [URL='https://malwaretips.com/threads/use-windows-10-build-in-anti-execution-options.85477/page-4']Windows 10 - Use Windows 10 build-in (anti)execution options[/URL] [B]I do not recommend you using SysHardener, until you will master H_C.[/B] Many SysHardener settings can do the same as H_C but in a different way, so if you will disable them in H_C, they will be still enabled by SysHardener, and in many cases, you will not know what to do. Also, SysHardener blocks are silent and there is no LOG to check what was blocked. SysHardener has not the 'back to Windows defaults' feature, so you have to know very well Windows to do it. The 'back to Windows defaults' feature is important because from time to time something goes wrong with Windows on non-default settings (usually one specific broken Windows Update). Setting UAC to deny elevation of unsigned will prevent using 'Run As SmartSreen' which is the important feature of the default-deny H_C setup. [USER=50782]@Windows_Security[/USER] uses 'deny elevation of unsigned' + 'Run as administrator' for many years - this a good replacement for 'Run As SmartScreen' for the advanced and cautious users who know the limitations of SmartScreen. Please, bear in mind that H_C setup is too restrictive for many people, and [USER=50782]@Windows_Security[/USER] setup adds many additional restrictions. Please, do not try to be the master of restrictions from the beginning. The masters like [USER=50782]@Windows_Security[/USER] are doing this for many years. My advice would be - the restrictions should be applied in accordance with the growing knowledge.:giggle:(y) [/QUOTE]

Verification