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
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
Security
Guides - Privacy & Security Tips
Software restriction Policies to Windows Home
Message
<blockquote data-quote="Andy Ful" data-source="post: 544914" data-attributes="member: 32260"><p>[USER=50782]@Windows_Security[/USER]</p><p></p><p>I noticed something strange. In Widows 10 Pro I can setup SRP through secpol.msc and choose "BASIC USER", so indeed the value of "DefaultLevel"=dword:00020000 is written to the Registry. It is OK. Yet, the behavior of SRP is different. I can run programs in the User Space that do not require elevation! Programs with elevation are blocked.</p><p>If I choose in secpol "DISALLOWED" then the value of "DefaultLevel"=dword:00000000 is written to the Registry, and SRP works as default deny like in Your Windows Home setup.</p><p>Is it possible to confirm this on one of Yours machines? If so, maybe it would be better to change DefaultLevel value from 00020000 to 00000000 to avoid misconception.</p><p></p><p>There is one little mistake on the list of SRP protected files:</p><p>there is 'WSF should be WSF .</p><p></p><p>I also tested Your SRP for Windows Home on my machine (Win 10 Pro 64Bit) and it works well<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p></blockquote><p></p>
[QUOTE="Andy Ful, post: 544914, member: 32260"] [USER=50782]@Windows_Security[/USER] I noticed something strange. In Widows 10 Pro I can setup SRP through secpol.msc and choose "BASIC USER", so indeed the value of "DefaultLevel"=dword:00020000 is written to the Registry. It is OK. Yet, the behavior of SRP is different. I can run programs in the User Space that do not require elevation! Programs with elevation are blocked. If I choose in secpol "DISALLOWED" then the value of "DefaultLevel"=dword:00000000 is written to the Registry, and SRP works as default deny like in Your Windows Home setup. Is it possible to confirm this on one of Yours machines? If so, maybe it would be better to change DefaultLevel value from 00020000 to 00000000 to avoid misconception. There is one little mistake on the list of SRP protected files: there is 'WSF should be WSF . I also tested Your SRP for Windows Home on my machine (Win 10 Pro 64Bit) and it works well:) [/QUOTE]
Insert quotes…
Verification
Post reply
Top