McShield errror message

I got the same error. In the Event Viewer it says: "Faulting application name: mcshieldds.exe, version: 3.0.5.43, time stamp: 0x51103f08 Faulting module name: vbscript.dll, version: 5.812.10240.16384, time stamp: 0xd56d6774 Exception code: 0xc0000005 Fault offset: 0x00027857 Faulting process ID: 0x275c Faulting application start time: 0x01d53ca699cddeca Faulting application path: C:\Program Files (x86)\MCShield\mcshieldds.exe Faulting module path: C:\Windows\System32\vbscript.dll Report ID: d64b6a26-9165-442d-ba8d-0b07e0995bb2 Faulting package full name: Faulting package-relative application ID: " I tried to re-register "vbscript.dll" and update all visual c++ redistributables, but nothing worked.

I've seen other people report getting the vbscript.dll error message.

Unfortunately, it appears that McShield is no longer supported... I'd be shocked if the program gets updated/fixed at this point.

Since the issue is with the McShieldDS.exe file (DS= Drive Scanner), I have to question whether the results generated can be trusted... and more significantly, whether the program can seriously malfunction and cause damage to my system(s). 

On shared systems, I've disabled the program (so that other users won't be confronted with the error message).

On my personal systems, I've likewise --- but reluctantly --- disabled it... since I'm the only one who uses thumb drives here, and so can be very careful about what I'm doing.

"The problem most likely is to update the Malicious Software Removal Tool KB890830 July 2019 or the Cumulative Update for .NET Framework 3.5 and 4.8 KB4506991. After these updates, the mentioned problem appeared in MCShield (OS Windows 10). Since I see from the comments that the same problem appeared and on Win 7, I guess it's just a matter of updating the Malicious Software Removal Tool KB890830 July 2019. Microsoft always likes to screw up something that is excellent and stable." So I guess it should be fixed in the future updates.

problem solved: Cumulative Update for Windows 10 Version 1903 (KB4505903) (18362.267) if you have any other Windows version, just check the July 24 update

Confirming that KB4505903 fixes this issue on Win10 version 1903.

For other versions of Windows, see https://forum.avast.com/index.php?topic=196168.msg1513863#msg1513863