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
Microsoft Defender
How to prevent efficiently Defender from considering a given VBS script as containing a threat
Message
<blockquote data-quote="LaurentG" data-source="post: 934785" data-attributes="member: 91050"><p>My problem is that my script do not launch any dangerous code</p><p></p><p>Here is the part of the script that generate the issue :</p><p></p><p>The threat is raised while on the WshShell.run</p><p></p><p>So clearly, I'm not looking for</p><p></p><p>I'm only looking for a way to inform Defender that there is <strong>no dangerous code in THIS script.</strong></p><p></p><p>FYI, here is another (also "home made") script that has NEVER been blocked by Defender, neither at loading, nor at run</p><p></p><p>Very similar, isn't t ?</p><p></p><p>So why the first script and not this one ?</p><p>I already tried to replace JHeadcmd by its value in WshShell.run, as it is in the 2nd script, but without any success</p><p></p><p><strong>So I still need community's help !</strong></p><p></p><p>PS : What I just read about AMSI-paired machine models (I never heard about before) make me even less favourable to make <strong>Trojan:VBS/Mountsi.A!ml</strong> an "authorized threat" !!!</p><p>But I nevertheless need to be able to run my script....</p></blockquote><p></p>
[QUOTE="LaurentG, post: 934785, member: 91050"] My problem is that my script do not launch any dangerous code Here is the part of the script that generate the issue : The threat is raised while on the WshShell.run So clearly, I'm not looking for I'm only looking for a way to inform Defender that there is [B]no dangerous code in THIS script.[/B] FYI, here is another (also "home made") script that has NEVER been blocked by Defender, neither at loading, nor at run Very similar, isn't t ? So why the first script and not this one ? I already tried to replace JHeadcmd by its value in WshShell.run, as it is in the 2nd script, but without any success [B]So I still need community's help ![/B] PS : What I just read about AMSI-paired machine models (I never heard about before) make me even less favourable to make [B]Trojan:VBS/Mountsi.A!ml[/B] an "authorized threat" !!! But I nevertheless need to be able to run my script.... [/QUOTE]
Insert quotes…
Verification
Post reply
Top