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

Thanks for keeping this topic around! It was just the fix I needed after installing Stardock's DesktopX and scripts would not run causing any theme which contained scripted objects to immediately crash the program. I had to change permissions in the registry before I was allowed to edit the neccessary key, then I applied the your patch and Voila! Thanks Guys and Gals!

Oh and by the way it was avast antivirus that had altered the registry key! And even though I had removed Avast a year prior, it hadn't removed the alteration.

(I purchased OEM not a VL)
How showld I know what version I have, since I have it installed
or from CD Rom?


I read on a forum that one possible solution to the failure to activate was to go into an Office application, go to File, then Account and use the change license button to enter a new key.

Here is what I have done, But fail with out success

Write-Host “Enter your Office 2013 License key, then press enter”
$Key = Read-Host
Set-Location “C:\Program Files (x86)\Microsoft Office\Office15”
CScript OSPP.vbs /InpKey:$Key
CScript OSPP.vbs /act

From what little I can make out of your problem, it is that you have a version of Office, which fails to activate.

Which version of Office? If it's not Office 2013 then you're on a loser anyhow.

What EXACT error message do you get when you attempt to activate?

Thank you for your response I dint receiver email of you post!


Which version of Office? If it's not Office 2013 then you're on a loser anyhow
==========================
Microsoft Office Professional Plus 2013
==========================

What EXACT error message do you get when you attempt to activate?

I have posted Image.. If you wanted to run different code please let me know!
by changing from:

OEM to VL

The problem here is that the script file itself (ospp.vbs) is missing (or at least, can't be found) - not that the engine is disabled.

Are you sure that you have the right folder?
Open the Command Prompt Window and type the following commands one at a time:

DIR "C:\Program files\ospp.vbs" /S
DIR "C:\Program Files (x86)\ospp.vbs" /S

These should return with the proper location for the vbs file.

here are photo images, posted

I don't have a copy of Office 2013 installed anywhere, so I can't check he proper locations for the files, but that doesn't appear right to me.
In My Office 2010, the ospp file is in the main 64-bit Office folder, rather than the 32-bit one.

In the Command Prompt window, you neglected to type the command DIR prior to the location and switch - which is what caused the error messages.

It looks to me as if you have a schizophrenic installation of Office - part thinks it's 32-bit, and part thinks its 64-bit!

A repair install of Office is required - use the option to repair the install from within Programs & Features.

Q1. In My Office 2010, the ospp file is in the main 64-bit Office folder, rather than the 32-bit one.

I would like to think I have installed 32bit version

Q2. Command DIR prior to the location and switch - which is what caused the error messages.
Becaus of : ospp file

Q3. schizophrenic installation of Office - part thinks it's 32-bit, and part thinks its 64-bit
what does mean schizophrenic?
Yes, I agree because as you know it show file: 32-64_Bite's

Q4. Repair install of Office is required
I would reinstall from CD Room. I though was better by download from a website because it was lighter, the think is I dont know if is OEM nor VL

looking forward for your response

Thanks again

Note:

Where is good site to download it, since I dont need all features from CD Rom?
My goal is to download "VL" Version

I have Office 2013 Pro 32 bit version & files appear in both the 32 bit Program Files & the 64 bit Program Files.

As far as I know Office 2013 came in 2 installation types, one came as full install DVD which I thought was Office 2013 Professional Plus & was mainly for schools & institutions for multi installations.

The other was a retail version of Office 2013, which was a Click to Run version & while an installation DVD was supplied, most of the installation occurred from MS via the internet.

Ranger 4
are you compatible / available to change to Volume license, once installed?

Do you know the pat from:
ospp file



Thank!