Classic ASP very slow when Windows Defender is turned on

Question

Hi everyone.

I've noticed that when Windows Defender is turned on my Classic ASP applications get very very very slow. Something like 80% slower.

We can find some information about it on the internet, about people complaining about the same thing.

The issue occurs on Windows 10 1809 / 1903 and also on Windows Server 2019 1809.

This problem does not occur on Windows Server 2016 1607.

Some say that the problem is with vbscript.dll, but even if I add this on the exclusion list the problem still occurs.

The only way to make my applications running fast again is to disable the Real Time Protection, which is obviously not what I wanted to do.

I really need Microsoft to explain what has changed and what is the best way to address this issue and solve the problem definitely.

Thanks in advance.

Cezar

Answer 1

Its likely a bug the engineers are not aware of. Send me the link to the bug report so I can vote on it and bring it to the attention of the engineers.

Answer 2

Hello again Andre.

I have a Windows Server 2016 up and running. I've copied it's vscript.dll and placed it on my local computer for testing before applying on my Windows Server 2019, but it didn't work.

Any other idea?

Thanks

Answer 3

Unfortunately, I don't have access to a Server running Server 2016.

You could maybe download an eval copy and spin it up in a VM them then copy it from it.

https://www.microsoft.com/en-us/evalcenter/eval...

Answer 4

Hello Andre, thanks for your feedback.

I've create the bug report as recommended, and I also tried to replace the vbscript.dll with the Windows Server 2016 version, but, no success.

Can you please send me the link of a working vbscript.dll?

Thanks

Cezar

Answer 5

Hi Cezar

My name is Andre Da Costa; an Independent Consultant, Windows Insider MVP and Windows & Devices for IT MVP. I'm here to help you with your problem.

This is explaination I found on the following thread:

As explained above this is a system level script engine (vbscript.dll) problem which affects *ALL* Classic ASP scripts written in VBScript. You can find other similar reports for other scripts on the internet. It is a script engine issue NOT related to database schema or database provider. Before Microsoft releasing a good vbscript.dll, all Classic ASP users (including us) have no choice but to use an old one.

Source: http://www.hkvforums.com/viewtopic.php?f=1&...

The recommendation is the replace the vbscript.dll with one from Windows Server 2016 if you have access to that version.

I would also recommend you file a bug report; send me the short link so I can vote on it and bring it to the attention of the Windows engineers in my capacity as a Windows Insider MVP.

See instructions how to file the bug report.

https://windows10.help/blogs/entry/54-how-to-su...

Information in the above link is sourced from a trusted Microsoft MVP blog.