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
Any real-time software that uses non-traditional ways to find malware?
Message
<blockquote data-quote="mazskolnieces" data-source="post: 916900" data-attributes="member: 88422"><p>You are not providing any compelling evidence here that suggests it "is a VERY bad idea" to block Windows Script Host full-time.</p><p></p><p>Intel's task.vbs script was blocked. And it was the OP end user that figured it out for themselves after being sent on a wild goose chase by you and others.</p><p></p><p>This matter was trivial. And it remains trivial. Intel's QueenCreek task.vbs is not required to run. Blocking it breaks nothing. So the notion that it "is a VERY bad idea...." to block WHS based upon blocking a non-essential, intrusive .vbs file is ludicrous. Millions block WHS without anything more than a minor example. Not to mention that allowing WHS to run exposes abuse of Microsoft's own scripts to do a number of things on either workstation or server.</p><p></p><p>Other default-allow vendors block Intel task.vbs as well. Here are a few examples:</p><p></p><p><a href="https://community.norton.com/en/forums/queen-creek-taskvbs-detection" target="_blank">Norton Blocks Task.vbs</a></p><p></p><p><a href="https://support.emsisoft.com/topic/27829-malicious-code-detected/" target="_blank">Emsisoft Blocks Task.vbs</a></p></blockquote><p></p>
[QUOTE="mazskolnieces, post: 916900, member: 88422"] You are not providing any compelling evidence here that suggests it "is a VERY bad idea" to block Windows Script Host full-time. Intel's task.vbs script was blocked. And it was the OP end user that figured it out for themselves after being sent on a wild goose chase by you and others. This matter was trivial. And it remains trivial. Intel's QueenCreek task.vbs is not required to run. Blocking it breaks nothing. So the notion that it "is a VERY bad idea...." to block WHS based upon blocking a non-essential, intrusive .vbs file is ludicrous. Millions block WHS without anything more than a minor example. Not to mention that allowing WHS to run exposes abuse of Microsoft's own scripts to do a number of things on either workstation or server. Other default-allow vendors block Intel task.vbs as well. Here are a few examples: [URL='https://community.norton.com/en/forums/queen-creek-taskvbs-detection']Norton Blocks Task.vbs[/URL] [URL='https://support.emsisoft.com/topic/27829-malicious-code-detected/']Emsisoft Blocks Task.vbs[/URL] [/QUOTE]
Insert quotes…
Verification
Post reply
Top