Solved CScript Error: Can't find script engine "VBScript" -alternate solution

[NoelDP]

CScript Error: Can't find script engine "VBScript" -alternate solution

I just came across this error in troubleshooting an MGADiag report to solve a non-genuine message on a Vista computer.
It took me a large amount of searching to find the right answer to it - so I thought I'd post my solution here in the hope that it gets a little easier to find for others in the same position


CScript Error: Can't find script engine "VBScript" for script "C:\Windows\system32\slmgr.vbs".

This was preventing the Software Licensing Service in Vista doing what it needs to - and consequently giving rise to the non-genuine message, despite a perfectly genuine install.

The conventional response is to re-register the dll using
regsvr32 vbscript.dll

This works fine in many instances - but in this case, although the registration gave rise to the 'succeeded' message, as it should (thereby showing that the dll was present), there was no change in the response from MGADiag.

The user had been using a registry cleaner - and this was in another forum, and she wasn't the world's most savvy user. All attempts to get her to properly follow reg query instructions failed.

Eventually, I got a clue to the problem from an obscure blog, which mentioned that some AV's blocked a particular registry entry, by substituting their own dll for the vbscript one.

The penny dropped at last - so I created a small reg file to put the default entry there instead.

Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32]
@="C:\\Windows\\system32\\vbscript.dll"
"ThreadingModel"="Both"

with fingers and toes crossed, I sent her instructions to download and merge the file.
.....and it worked! The thread was by that time 45 long, with just the two of us in it.
Huge sighs of relief all round, and she's promised never to use a registry cleaner again.
So two victories for the price of one.

Not a bad result [edit] - and yes, it should also work in Win7 and XP [/edit]

EDIT: (15/12/2012)
In a recent instance of this problem, Avast5 left behind incorrect values in the Classes\WOW64 area of the registry - these required more detailed hand-editing. Please post a NEW thread in the forum requesting assistance with as much detail as you can, and someone will assist.

 

[jayster]

Endured the registration prossess just so I copuld say "thank you". Your registry fix brought much joy. More than six months of searching for a fix ended when I found this registry merge. Thank you muchly!

 

[NoelDP]

Endured the registration prossess just so I copuld say "thank you". Your registry fix brought much joy. More than six months of searching for a fix ended when I found this registry merge. Thank you muchly!

You're welcome - that's why I posted it

 

[havis23]

wait!!! i'm a noob here... but at least i knew that i got the same problem...
can you tell me what to do from the first step to the last one..
or else, i wont understand..
--
thanks for help...

 

[NoelDP]

wait!!! i'm a noob here... but at least i knew that i got the same problem...
can you tell me what to do from the first step to the last one..
or else, i wont understand..
--
thanks for help...

1) Highlight all the stuff in the Code box - then right-click on it and select Copy
2) Open Notepad
3) right-click in Notepad, and select Paste
4) Save the file as 'regfix.reg' to your desktop
5) close Notepad
6) doubleclick on the regfix.reg file - and confirm it when teh IAC box pops up,
7 ) Wait until you get teh Success message, then reboot and test.

 

[NoelDP]

....Second thoughts!
Something has altered the permissions on that registry key. they now require to be modified before using the fix (bother!)

first, let's check that the Key is actually the problem
please run the following command from a COmmand Prompt window, and post the results.

reg query HKEY_CLASSES_ROOT\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32


post the results.

Here are some instructions to make life easier
1) To open an Elevated Command Prompt Window (the CP window), click on Start, All Programs, Accessories – then right-click on Command Prompt, and select Run as Administrator. Accept the UAC prompt.
2) To run the commands easier, highlight the block of commands, and right-click on the highlight – select Copy. In the CP Windows, click on the black/white icon at top left – select Paste. The commands will run but may not complete the last command, so hit the Enter Key once.
3) To copy the results... click on the Black/White icon in the top left, and select Edit... 'Select All', and hit the Enter key - then use Ctrl+V or r-click+Paste to paste it into your response.

 

[Cyroq]

I'm having the same problem, when running the regfix script I get a 'Cannot import' error. I pasted that line into cmd and this is what rolls out:

HKEY_CLASSES_ROOT\CLSID\{B54F3741-5B07-11cf-A4B0-0AA004A55E8}\InprocServer32
(Default) REG_SZ C:\Windows\system32\vbscript.dll
ThreadingModel REG_SZ Both

Still having vbscript.dll errors though.

 

[NoelDP]

In that case, your problem is a different one.
Please start a new thread of your own in the Crashes and Debugging forum here, ancluding your exact error messages and the above results, and someone will assist - certainly me, and probably a few others also.

 

[Fipps]

Hey, found this forum via google and hoped for a fix. following your instructions this is what is stated in cmd after inquiring the regkey:

C:\Windows\SysWOW64> reg query HKEY_CLASSES_ROOT\CLSID\{B54F3741-5B07-11cf-A4B0-
00AA004A55E8}\InprocServer32

HKEY_CLASSES_ROOT\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32
    (Standard)    REG_SZ    C:\Program Files (x86)\Common Files\McAfee\SystemCor
e\ScriptSn.20120926201932.dll
    ThreadingModel    REG_SZ    Both

The idea to simply copy and rename the vbscript.dll into that folder (which doesn't exist anymore since I uninstalled bloody McAfee..) after recreating it did not work.

UPDATE: I had a typo in the dll's name. After registering it via regsvr32 it now seems to work alright. Still it's a very ugly solution - maybe you can figure out a more elaborated way.

 

[NoelDP]

UPDATE: I had a typo in the dll's name. After registering it via regsvr32 it now seems to work alright. Still it's a very ugly solution - maybe you can figure out a more elaborated way.

Why? - this one works!

 

[kohyoubeng]

I have the same problem. After running the code, here is the result:


C:\Windows\system32>reg query HKEY_CLASSES_ROOT\CLSID\{B54F3741-5B07-11cf-A4B0-0
0AA004A55E8}\InprocServer32

HKEY_CLASSES_ROOT\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32
(Default) REG_SZ C:\Program Files\Kaspersky Lab\卡巴斯基安全部队 2011\
scrchpg.dll
ThreadingModel REG_SZ Both
OriginalDll REG_SZ C:\Windows\system32\vbscript.dll

i tried to create and run the regfix.reg, however, i got the following message:

Cannot import C:\...\Desktop\regfix.reg: Not all data was successfully written to the registry. Some keys are open by the system or other processes.

Any suggestion. thanks.

 

[NoelDP]

Are you actually running Kaspersky?
If not, run the Kaspersky cleanup tool Removal tool for Kaspersky Lab products which should correct teh problem.
If you are running Kaspersky, check its security settings and allow VBScripting.

 

[kohyoubeng]

thank for the reply.

I solved the problem. The default value was changed by the antivirus software. After change it back to VBScript, the problem solved.

 

[NoelDP]

That is common - but if the AV software is properly installed, it should forward the request after scanning the script. The fact that it wasn't doing so is what caused your problem and you need to find out why that was happening, rather than blindly switching it off in such a way.

 

[akshaybz]

>reg query HKEY_CLASSES_ROOT\CLSID\{B54F3741-5B07-11cf-A4B0-00AA0
04A55E8}\InprocServer32

HKEY_CLASSES_ROOT\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32
    (Default)    REG_SZ    C:\Windows\system32\vbscript.dll
    ThreadingModel    REG_SZ    Both

Still shows that can't find script engine "VBScript"..
Any help would be appreciated.

 

[NoelDP]

Please start a new thread of your own and post details there.

 

[Twindad97]

Everyone, I am at a loss! I am having the same errors as Cyroq and cannot to no end figure this out.

I am the administrator and the system will not allow me to add the file to said directory, I cannot run the script and to make matters worse, I cannot delete the Registry entry as other posts have satated.

So my question is this! is there any hope out there? someone please guide me through this NIGHTMARE That i cannot seem to get out of. I have lost more time fiddling with this than I care to.

Thanks in Advance,

TD


EDIT: disregard, you will find the answer in this thread. Same Forum! I am sooooooooooooo happy!

http://www.sevenforums.com/general-discussion/162931-cant-find-vbscript-engine.html#post1396118

 

[NoelDP]

Please start a new thread of your own, and post details.

 

[SBrumbelow]

Unsolved: Windows can not find VBScript when needed by applications.

Since my post is about Windows 7 not finding VBScript engine, I fail to see the relevance of the "windows genuine" and "Windows update" links on lines two and three of your "Notices" regarding my question. I downloaded and ran the SystemInfo, and it correctly identified my hardware. I just installed a Seagate SSHD that was not fully identified. The program's interface with your web site did not complete the web site's copy of the information for this system, but I see no reason to do that manually since I assume that SystemInfo normally records that information at your site.
Concerning my problem with VBScript, I have not yet located a solution. Here are some of the steps that have not helped:

• Run REGSVR32 for VBScript.dll.
• Check the values for the CLSID {B54F3741-5B07-11cf-A4B0-00AA004A55E8}|Inprocserver.
• Searched the complete registry to see if there were any obvious problems related to VBScript.
• Searched the internet using multiple search engines for this problem.

As I said, none of these actions helped. Furthermore, my searches of the internet convinced me that there are other Windows users out here that also can't do any new processes that require VBScript and are putting up with an error in Windows support for its own VBScript utility. The error first appeared for me when I wanted to try out the Zimbra email client. The Applications event log has reported other miscellaneous errors that probably occur for the same reason. As for me, the problem will not be fixed until I can run the Zimbra email client. The other error events are not as troublesome as that one for me.
I am not experienced enough on forums like this to know if I am reporting this problem in the proper way, so if I have not done so, I will be grateful if someone will do it properly this time. I can learn by example.

 

[NoelDP]

This sticky was put up because one of the commoner errors resulting in a non-genuine status in Windows Vista and windows 7 was the 'Can't find...' one - possibly as a result of certain registry cleaners' inability to understand the new paradigms involved in Vista/7 compared to XP.

I would be very surprised if you're getting this error without also getting a non-genuine notification, unless you've hacked Windows in some way, as WGA relies on VBS for the bootup license checks.

Please start a new thread of your own and detail your problems there - a look at your event logs would be useful, as well...


Open Event Viewer
click on the Windows logs entry in the left pane to expand it.
Now click on the Application entry - wait while it loads.
Click on 'File' in the menu bar and select Save...
Save the file as Appevt.evtx
Repeat for the System log
then zip both, and upload them to your new thread.