Could not run VBScript run time for custom action?

[Dan]

I'm attempting to install our version of live drive on a clients computer for real time backups and when I try to run it I get this issue, no matter what. Ive uninstalled all the prior installed programs such as a PDF converter, adobe acrobat, most of the bloat ware. I've also attempted all the basics by google searching such as:

----------------------------------------------------

reg delete "HKCU\SOFTWARE\Classes\Wow6432Node\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f

That previous command removes the incorrect entry for VBScript support on 64-bit Windows 7. Next you need to make sure VBScript is properly registered by typing:

c:\windows\syswow64\regsvr32 vbscript.dll

or simply regsvr32 vbscript.dll if you are already in the syswow64 directory.

After following these steps you should be able to install your program without issue.

*which is bullshit cause i had myself and another employee enter that reg delete command and it says invalid.

--------------------------------------------------------------------------------------------------

regsvr32 c:\Windows\System32\vbscript.dll

all this did was re-register the .dll. didnt solve anything.

I also tried the "microsoft fix-it" and nothing from that either.

Any other idea's? would a fresh install of OEM possibly help this instead of bloat fill lenovo w7?

 

[PTNL]

Try right-click and "Run As Administrator" for installer or doing the same on the Command Prompt, or turning off UAC altogether.

Also, is this machine on a domain? There could be GP counteracting your efforts.

 

[Demon10000]

Do you get an error or something?

That reg command looks valid. If you're getting an invalid command when you're running, your path statement may f'd up. Either way, if you think that will help, use regedit and find the key then rename it to something else. That way you can put it back if it doesn't solve anything.

 

[Dan]

I eneded up doing a restore via Lenovo software, and just installed our livedrive first. No issues. Apparently PDF converters can cause this issue.