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
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: 934798" data-attributes="member: 91050"><p>Thank you both for your answers.</p><p></p><p>I agree with Andy that even if my request of "false positive" was accepted, this would have only effect on <strong>TrojanDownloader:HTML/Adodb.gen!A,</strong> not on AMSI detection which is, as far as I have understood, a "live detection" based on behaviour.</p><p>Moreover, raising such a request needs a Microsoft account, and for different reason, I do not have, and prefer to do not create one.</p><p>So I give up wit this "solution".</p><p></p><p>About the "mini script" I showed, on my Pc also, a script limited to these 4 lines works fine, and is not detected by Defender.</p><p>It's actually consistent with the fact that the second script I mention (and that is limited to launching jhead) is OK</p><p></p><p>But these four lines are inside a more complete script that is running fine without them (except the fact it do not make the full job, not creating the EXIF).</p><p>It is only when I add these lines to the main script that Defender raises in it :</p><p>- as a Trojan downloader</p><p>- and a AMSI threat at run....</p><p></p><p>I think I'll try to reorganize completely once again my script. Maybe I'll be lucky...</p><p>Otherwise, <strong>except if some other proposal are done</strong> on this forum (or some other where I post the same issue), I'll finish in giving up wiith Defender and returning to Avast or similar... </p><p>Too bad, since I was convinced that to add extra softs (like Avast) when (almost) the same in available in Windows is always a bad idea and should be avoided (as far as we can....)</p></blockquote><p></p>
[QUOTE="LaurentG, post: 934798, member: 91050"] Thank you both for your answers. I agree with Andy that even if my request of "false positive" was accepted, this would have only effect on [B]TrojanDownloader:HTML/Adodb.gen!A,[/B] not on AMSI detection which is, as far as I have understood, a "live detection" based on behaviour. Moreover, raising such a request needs a Microsoft account, and for different reason, I do not have, and prefer to do not create one. So I give up wit this "solution". About the "mini script" I showed, on my Pc also, a script limited to these 4 lines works fine, and is not detected by Defender. It's actually consistent with the fact that the second script I mention (and that is limited to launching jhead) is OK But these four lines are inside a more complete script that is running fine without them (except the fact it do not make the full job, not creating the EXIF). It is only when I add these lines to the main script that Defender raises in it : - as a Trojan downloader - and a AMSI threat at run.... I think I'll try to reorganize completely once again my script. Maybe I'll be lucky... Otherwise, [B]except if some other proposal are done[/B] on this forum (or some other where I post the same issue), I'll finish in giving up wiith Defender and returning to Avast or similar... Too bad, since I was convinced that to add extra softs (like Avast) when (almost) the same in available in Windows is always a bad idea and should be avoided (as far as we can....) [/QUOTE]
Insert quotes…
Verification
Post reply
Top