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
Operating Systems
Windows 11
Windows 11 22H2 no longer supports Software Restriction Policies (SRP)
Message
<blockquote data-quote="ForgottenSeer 98186" data-source="post: 1026471"><p>That is true no matter what method is used to block a process. You disable the blocking mechanism, install the software, then re-enable the protection. It cannot get any more simple. Like a light switch. "On-Off-On." The process of installs is no different than using other methods to block such as SRP, any of the hardening utilities available, anti-executables, Group Policy and so on.</p><p></p><p>Lots of people who have managed Windows systems and enterprises block 150+ processes globally and they have zero troubles. Then there are those unmanaged users (home users) that block the entire LOLBin list (e.g. using Hard_Configurator) without a single issue. They can sort out any "blocks" and they find it perfectly trouble-free.</p><p></p><p>Microsoft created S Mode - deliberately to prevent users from downloading stuff from non-Microsoft sources - like drivers. It was, and remains, the most secure version of Windows.</p><p></p><p>I get that lots of users cannot resolve issues based solely on block event logs nor do they want a system that prevents them from installing stuff. Not everybody has the inclination, the aptitude nor the desire. For those users, they are best served by a default allow solution such as F-Secure or Kaspersky.</p><p></p><p>That said, every user has to decide for themselves what works best for them personally.</p></blockquote><p></p>
[QUOTE="ForgottenSeer 98186, post: 1026471"] That is true no matter what method is used to block a process. You disable the blocking mechanism, install the software, then re-enable the protection. It cannot get any more simple. Like a light switch. "On-Off-On." The process of installs is no different than using other methods to block such as SRP, any of the hardening utilities available, anti-executables, Group Policy and so on. Lots of people who have managed Windows systems and enterprises block 150+ processes globally and they have zero troubles. Then there are those unmanaged users (home users) that block the entire LOLBin list (e.g. using Hard_Configurator) without a single issue. They can sort out any "blocks" and they find it perfectly trouble-free. Microsoft created S Mode - deliberately to prevent users from downloading stuff from non-Microsoft sources - like drivers. It was, and remains, the most secure version of Windows. I get that lots of users cannot resolve issues based solely on block event logs nor do they want a system that prevents them from installing stuff. Not everybody has the inclination, the aptitude nor the desire. For those users, they are best served by a default allow solution such as F-Secure or Kaspersky. That said, every user has to decide for themselves what works best for them personally. [/QUOTE]
Insert quotes…
Verification
Post reply
Top