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
General Security Discussions
Windows script host
Message
<blockquote data-quote="Andy Ful" data-source="post: 788368" data-attributes="member: 32260"><p>There is an incomplete information in the article. The reg tweak will block only Windows Script Host on the 32-bit system. If you have 64-bit Windows then the same value must be changed/added in the key:</p><p>HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows Script Host\Settings'</p><p></p><p></p><p>It is worth mentioning, that most of the methods explained in the article do not disable Windows Script Host, but only change file extension associations, so <span style="color: rgb(85, 57, 130)"><strong>the user cannot run </strong></span>the script files (.js, .jse, .vbs, .vbe, .wsf, .wsh). But, the <span style="color: rgb(184, 49, 47)"><strong>malware can still run</strong></span> those scripts.</p><p>The right way of blocking Windows Script Host is available via activating the right Windows policy, or using the reg tweaks in the below keys (which is also explained in the article):</p><p>HKLM\SOFTWARE\Microsoft\Windows Script Host\Settings'</p><p>HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows Script Host\Settings'</p></blockquote><p></p>
[QUOTE="Andy Ful, post: 788368, member: 32260"] There is an incomplete information in the article. The reg tweak will block only Windows Script Host on the 32-bit system. If you have 64-bit Windows then the same value must be changed/added in the key: HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows Script Host\Settings' It is worth mentioning, that most of the methods explained in the article do not disable Windows Script Host, but only change file extension associations, so [COLOR=rgb(85, 57, 130)][B]the user cannot run [/B][/COLOR]the script files (.js, .jse, .vbs, .vbe, .wsf, .wsh). But, the [COLOR=rgb(184, 49, 47)][B]malware can still run[/B][/COLOR] those scripts. The right way of blocking Windows Script Host is available via activating the right Windows policy, or using the reg tweaks in the below keys (which is also explained in the article): HKLM\SOFTWARE\Microsoft\Windows Script Host\Settings' HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows Script Host\Settings' [/QUOTE]
Insert quotes…
Verification
Post reply
Top