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
How to Protect and Harden a Computer against Ransomware
Message
<blockquote data-quote="509322" data-source="post: 579698"><p>Virtually nothing.</p><p></p><p>I've only seen Windows use Powershell a single time. The Windows 10 Upgrade Utility - GWX - used it.</p><p></p><p>Once in a great while, Windows Update will use wscript.exe (Windows Script Host). I have seen it on W7 only.</p><p></p><p>Powershell is a menace that 99.99999 % of typical users do not need on their system. Both wscript.exe and cscript.exe should be disabled as well. If you need them, you enable them, do what you need, then promptly disable them. It is that simple.</p><p></p><p>If something gets blocked, noting is permanently broken. Blocks are no big deal - even during a Windows Update. Just re-enable, update Windows again, then promptly disable. Simple.</p><p></p><p>Renaming vssadmin.exe shouldn't affect anything. It's a command line utility. Once again, 99.99999 % of typical users don't use it.</p><p></p><p>There's a lot of stuff shipped with Windows that a user does not need. Disabling what you do not need reduces attack surface and prevents many attacks.</p><p></p><p>There's a reason that the industry calls many Windows processes - well - vulnerable processes.</p><p></p><p>If people would just put a little bit of effort into learning more about the topic, then they could increase their system protection significantly.</p></blockquote><p></p>
[QUOTE="509322, post: 579698"] Virtually nothing. I've only seen Windows use Powershell a single time. The Windows 10 Upgrade Utility - GWX - used it. Once in a great while, Windows Update will use wscript.exe (Windows Script Host). I have seen it on W7 only. Powershell is a menace that 99.99999 % of typical users do not need on their system. Both wscript.exe and cscript.exe should be disabled as well. If you need them, you enable them, do what you need, then promptly disable them. It is that simple. If something gets blocked, noting is permanently broken. Blocks are no big deal - even during a Windows Update. Just re-enable, update Windows again, then promptly disable. Simple. Renaming vssadmin.exe shouldn't affect anything. It's a command line utility. Once again, 99.99999 % of typical users don't use it. There's a lot of stuff shipped with Windows that a user does not need. Disabling what you do not need reduces attack surface and prevents many attacks. There's a reason that the industry calls many Windows processes - well - vulnerable processes. If people would just put a little bit of effort into learning more about the topic, then they could increase their system protection significantly. [/QUOTE]
Insert quotes…
Verification
Post reply
Top