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
Security Apps
Hard_Configurator Tools
Hard_Configurator - Windows Hardening Configurator
Message
<blockquote data-quote="Andy Ful" data-source="post: 770950" data-attributes="member: 32260"><p>In Windows 10, using PowerShell 2.0 is not possible until the user will install Net Framework 3.5 . PowerShell 2.0 requires both installed Net Framework 2.0 and ticked option "Windows PowerShell 2.0" in Windows optional features.</p><p>In Windows 8.1 and prior versions the PowerShell interpreters are blocked by recommended H_C settings.</p><p>So, most users are protected against bypassing "Constrained Language Mode" via PowerShell 2.0.</p><p>Yet, the users with installed Net Framework 3.5 on Windows 10 have to block PowerShell interpreters.</p><p>The idea of removing PowerShell 2.0 is worth rethinking.</p></blockquote><p></p>
[QUOTE="Andy Ful, post: 770950, member: 32260"] In Windows 10, using PowerShell 2.0 is not possible until the user will install Net Framework 3.5 . PowerShell 2.0 requires both installed Net Framework 2.0 and ticked option "Windows PowerShell 2.0" in Windows optional features. In Windows 8.1 and prior versions the PowerShell interpreters are blocked by recommended H_C settings. So, most users are protected against bypassing "Constrained Language Mode" via PowerShell 2.0. Yet, the users with installed Net Framework 3.5 on Windows 10 have to block PowerShell interpreters. The idea of removing PowerShell 2.0 is worth rethinking. [/QUOTE]
Insert quotes…
Verification
Post reply
Top
