Update does not allow IIS vbscript to eval or evaluate

Thank you for writing back, Rex.
We request you to submit a sample ( http://samplesubmit.avg.com/false-detection ) for us to analyze and make the necessary changes in the coming updates. Thank you.

Rex,

Here is some info that I would appreciate you trying.

Go into ADVANCED settings —> Computer Protection –> AntiVirus and DISABLE "Enable Windows Antimalware Scan Interface (AMSI) for deeper software scans". If I do that, I no lontger get the error.

So . . .  Does this mean that it is not an AVG problem at all, but a Microsoft problem? Because if AVG just blindly uses the AMSI interface (available with windows 8 and windows 10) and if AMSI is detecting a problem and telling AVG about it, then AVG is blameless.

Let me know what you find. I think the KB update adds more stuff that AMSI checks including not allowing JSCRIPT/VBSCRIPT Eval and Execute.

Hello Rex and Steve,

We request you to attach the screenshot of the error that you received so that we can escalate it to our concern team and confirm whether the issue with AVG or is it with Windows.
To take a screenshot please follow the instructions mentioned in this link: http://avgread.me/1aZxsAV and attach the image to this thread and do let us know.
Thank you.

Hello Rex,
We regret for the inconvenience caused. We request you to disable each component of AVG ( http://support.avg.com/SupportArticleView?urlname=How-to-disable-individual-AVG-components ) and check upon disabling which component the website is loading fine. Then please add the website to AVG's exception list ( http://support.avg.com/SupportArticleView?urlname=How-to-exclude-file-folder-or-website-from-AVG-scanning ). Thank you.

Hi Rex. I just posted more information in "AVG Free Giving False Positive on ASP IIS Server". Have you received any further info from AVG?

The 1st image is with AMSI disabled – all OK
The 2nd image is with AMSI enabled – the issue

A recent update (Free edition) seems to have caused website vbscript code to no longer allow the evaluate function without producing the error

ASP 0115

followed by

A trappable error (C0000005) occurred in an external object

I infer this by vitue of disabling AVG protection – all works,
Re-enabling protection – stops working again.
Has some funny combination of Windows 10 updates combined with AVG updates caused this I wonder. Or is there some AVG solution.

User Steve D has posted their own topic (https://support.avg.com/answers?id=906b0000000bpHvAAI).
AVG Guru

Thank you for providing the screenshot, Rex.
We have escalated the issue to our concern team and awaiting for a reply.
Once we get a suggestion will post it here.
Your patience is much appreciated.

Yes thank you. I did try everything you suggested before my previous reply. Ie adding the website to avg's exception list does not solve the issue, I believe I have no choice but to disable computer protection. But running a localhost asp website with code using the eval function might be outside the capabilities of the current avg version. I'll keep a lookout for the next update.

Thanks Avinash,
The component that needed to be disabled was Computer protection. Leaving the other components active    while I use this website is a MUCH better option than my original acton of just disabling the entire product.
Thank you.

Hi Steve D,
AVG basically suggested disabling the url and/or the relevant file/folder from scrutiny. That wasn't relevant. The current only solution is to disable Computer Protection. A snippet of code that produces the error is at http://rexwhitford.com/test_avg.asp
This runs fine everywhere I've tried it, except when run on an IIS server (in my case localhost)
Suggestions that it is a recent Microsoft update look promising…

Rex,
Thank you for checking it and we appreciate your efforts. It is not recommended to disable computer protection. Please try to add the website to AVG's exception list as suggested in our last post. Thank you.

When I disable AMSI the issue vanishes. So Windows is detecting something to which AVG reacts badly.
And Windows Defender doesn't kill web servers.