I have been having trouble with my computer starting so slowly it about puts me to sleep. Indications are that this is due to Avast. Please see screenshot. I did set things so that Windows starts before Avast and it helped some, but not totally.
Also, and more importantly right now, I think one of these latest updates has messed with something on my computer called VBScript. Out of the blue I’m getting windows constantly telling me it “can’t find script engine “VBScript” for script.” I have done everything I could find to remedy this. I have re-registered the script and it says these have been successful. I have run sfc /scannow and it tells me no errors were found. Then I stumbled across something that I think might be important. My Avast, which always ran so smoothly, hasn’t been so smooth and predictable with these last program updates. I found the following and I would like one of the experts to tell me if this is what is happening with the Avast on my computer. Below is one of the things I found pointing to this VBScript problem being caused by the resident AV.
Looking at a Procmon trace taken while an attempt was made to run a script we noticed that cscript.exe was in fact being called but when the value defining which scripting engine to use for .vbs files was being read (HKCR\CLSID{B54F3741-5B07-11CF-A4B0-00AA004A55E8}\InprocServer32(Default)) we saw that the default vbscript.dll value had been replaced with a DLL from an antivirus vendor.
This is typical behavior when the antivirus application wants to scan the scripts before handing it over to the script engine, i.e. the AV application first scans the script and then passes it down to the actual scripting engine when it’s done scanning.
Fair enough, but something seems to have gone wrong with the chaining from the antivirus vendors scanning DLL after MS10-020…which results in it not finding the vbscript.dll file and this in turn results in the error Can’t find script engine “VBScript” for script.
I hope I get some help with this because it is really messing things up for me and I sure hate to have to uninstall Avast to see if that is the problem and then go with some other protection program in order to solve this. I haven’t been having real good luck in getting responses from the forum like I used to.
Is this really the best help anyone from this forum is willing to give me? You want me to go through the process of uninstalling Avast, then reinstalling something else.
I paid for this program for 3 years and I’d like to have some help with this problem. I’d like someone who knows about issues such as this to address this issue with me and walk me through how to fix it.
THEN … If no solution can be found I’ll look at uninstalling Avast and maybe going with something else.
The way I understand this, Avast may overwrite this key, which changes the key’s value to Avast script scanning DLL. I think that value has to be reverted back but I don’t know how to do this.
In theory this shouldn’t matter what avast version free/pro/ais is used.
The avastSvc.exe is the main avast service and controls all of the shields. At boot it (file system shield) will be scanning files that are being opened. Now this on a half decent system shouldn’t have any real performance impact.
The delay avast services until after system services is likely to have little effect as we are talking of only waiting for windows system services. This option is really only used if a particular system service that avast requires is slow to start, this would hang avast waiting for that to start. But is should be fractions of a second not huge amounts.
The question has to be asked what is responsible for this .vbs file being run, c:\users\cindy\appdata\local\temp\tmpaad5.vbs (and when do you get the error) ?
The reason I ask is it seems strange to be running a .vbs file from a temp folder.
I don’t believe avast changes the .vbs access the script shield would presumably intercept .vbs (Windows Scripting Host) to scan scripts to ensure they aren’t infected. But I don’t believe it modifies files to be able to do this, my copy of vbscript.dll in the system32 folder appears unchanged since 04 March 2011, no doubt after a windows update.
When did the VBScript error start ?
When did the slow start up issue first happen ?
So no recent changes, I also don’t believe that has anything to do with a slow start though.