Reply to thread

Message

<blockquote data-quote="ForgottenSeer 107474" data-source="post: 1077382">I have not yet (ever) used the reset Windows option, but to me it seemed to much hassle to configure mail and your apps again (and slimming down Windows11&#039;s telemetry and bloat again).I always felt a bit punished by Microsoft, having moved to Windows11 as one of the first and being rewarded by being excluded of SAC. Luckily [USER=32260]@Andy Ful[/USER]&nbsp; <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)" /> made WHHL and changed his mind to enable ISG so all early WIndows11 users can enjoy something similar to SAC (WDAC-ISG) but with the added bonus of being able to manage exclusions and blocking execution of risky file extensions (the Software Restriction Policies part of WHHL). The latter (&#039;harmless&#039; rich content files with embedded code/scripts triggering Lolbins) are the achilles heel of many antivirus solutions (as often showed by [USER=7463]@cruelsister[/USER]).IMO there are only two whitelisting strategies: blocking non-whitelisted in user space (e.g. WHHL) or containing them in a sandbox (e.g. Comodo Firewall with CS rules). There are of course more implementations possible (e.g. Cyberlock and Sandboxie with forced folders). To me blocking makes more sense than allowing them in a sandbox (with the risk of breaking out of the sandbox). Blocking is easier than containing for PC users with a simple software setup like I have (browser, office,&nbsp; media player)</blockquote>

[QUOTE="ForgottenSeer 107474, post: 1077382"] I have not yet (ever) used the reset Windows option, but to me it seemed to much hassle to configure mail and your apps again (and slimming down Windows11's telemetry and bloat again). I always felt a bit punished by Microsoft, having moved to Windows11 as one of the first and being rewarded by being excluded of SAC. Luckily [USER=32260]@Andy Ful[/USER] (y) made WHHL and changed his mind to enable ISG so all early WIndows11 users can enjoy something similar to SAC (WDAC-ISG) but with the added bonus of being able to manage exclusions and blocking execution of risky file extensions (the Software Restriction Policies part of WHHL). The latter ('harmless' rich content files with embedded code/scripts triggering Lolbins) are the achilles heel of many antivirus solutions (as often showed by [USER=7463]@cruelsister[/USER]). IMO there are only two whitelisting strategies: blocking non-whitelisted in user space (e.g. WHHL) or containing them in a sandbox (e.g. Comodo Firewall with CS rules). There are of course more implementations possible (e.g. Cyberlock and Sandboxie with forced folders). To me blocking makes more sense than allowing them in a sandbox (with the risk of breaking out of the sandbox). Blocking is easier than containing for PC users with a simple software setup like I have (browser, office, media player) [/QUOTE]

Verification