PingBack from http://www.joyofsetup.com/2007/06/07/when-vbscript-and-jscript-custom-actions-arent-utterly-evil/

This is one the things that should have been taken care of by the instaler already. The instaler team has enhanced MSI for some while, but has not taken care of fixing some of the basic functionality of the product. I have submitted change request after change request for fixes to this since the beginning. Everytime I see posting referring to "this post by Rob Mensching", I completly freak out.  

This is total rubbish. All of his assumption are total bull. IMHO

1.- Robust code is difficult write in script.

This is utterly nonsense, bad code can be writing in any language, but specially C. If the developer of the custom action written in script can not do a simple try{}catch() on his code, changing to C would not make it any better.

2.  Debugging script in the Windows Installer is difficult

Another stupid instaler team mistake and another request of mine. Has anyone on that team heard of "Active Scripting Host debug". Microsoft for some while sold us the idea of scripting debugging, I built several of them. doesn't that team care what their customer want?

3.  Anti-virus products kill them

My anti-virus kills any new code I put in my machine. Many ways exist of fixing this, but the main one is: Just execute the stupid script, do not put it in the file system, get it directly from the binary table and execute it, simple isn't it?

4.- Make sure jscript.dll and vbscript.dll are correctly registered.

So many things that are supposedly part of the base system (ie, media player, etc). Aren't those part of the system too since they are required by and used by the former apps? Shouldn't the system (MSI, etc) make sure they are in the correct state before executing an action which requires it?

This is just the tip of the iceberg. I honestly think that script should be the ONLY allowable way of writing custom action, since they provide sort of a sandbox model to protect the end user from ill-intented code from the part of the producer of the MSI and for the most part (i could say allways) they provide all the functionality you may possible need, besides the fact that script is so easy to write and debug (with the right support, of course)

I will send another set of emails to the Windows Installer Wishes mailto:msiwish@microsoft.com asking for some fixes for the upcoming 4.5 release. Let's hope someone is actually listening............

Recently, while attempting to build a Japanese MSI using WiX v3.0 , I received an error message that

PingBack from http://www.lrthompson.com/ppc/google-adwords-editor-vista-error-2739-fix/

Under Windows 7 x64 I also had to delete this key:

HKEY_CURRENT_USER\Software\Classes\Wow6432Node\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}

Having had to do this more than once (and also for Visual Studio's Wizard issues), and on more than one machine, I wrote a batch file.  Simply copy below to a .bat, and right-click -> Run as administrator

-----RegScriptHosts.bat-----

@ECHO OFF

FOR /D %%I IN (%0) DO CD /d %%~dpI

SET ARCH=x86

rem If either is set to AMD64, we have a 64bit OS

IF /I "x%PROCESSOR_ARCHITECTURE%x" == "xAMD64x" SET ARCH=x64

IF /I "x%PROCESSOR_ARCHITEW6432%x" == "xAMD64x" SET ARCH=x64

FOR %%V IN (VBScript JScript) DO CALL :Register %%V

GOTO :done

:Register

CALL :SetupEnv

IF DEFINED REGSVR32 CALL :RegScript %1

GOTO:EOF

:SetupEnv

SET REGSVR32=

IF "%ARCH%" == "x86" (

CALL :SetupEnv32

) ELSE (

CALL :SetupEnv64

)

GOTO:EOF

:SetupEnv32

SET REGSVR32=%SystemRoot%\System32\regsvr32.exe

SET HKCU=HKCU\SOFTWARE\Classes

SET HKLM=HKLM\SOFTWARE\Classes

GOTO:EOF

:SetupEnv64

SET REGSVR32=%SystemRoot%\SysWOW64\regsvr32.exe

SET HKCU=HKCU\SOFTWARE\Wow6432Node\Classes

SET HKLM=HKLM\SOFTWARE\Wow6432Node\Classes

GOTO:EOF

:RegScript

SET SCNAME=%1

IF NOT DEFINED SCNAME GOTO:EOF

IF %SCNAME% == VBScript (

SET KEY=B54F3741-5B07-11CF-A4B0-00AA004A55E8

) ELSE (

SET KEY=F414C260-6AC0-11CF-B6D1-00AA00BBBB58

)

ECHO Registering ScriptingHost for %SCNAME% (%ARCH%)

reg delete "%HKCU%\CLSID\{%KEY%}" /f >NUL 2>NUL

reg delete "%HKLM%\CLSID\{%KEY%}" /f >NUL 2>NUL

"%REGSVR32%" "%SCNAME%.dll" /s

IF ERRORLEVEL 1 GOTO :error

GOTO:EOF

:error

ECHO Failed to register ScriptingHost for %SCNAME% (%ARCH%)!

ECHO.

GOTO:EOF

:done

ECHO.

PAUSE

Hello all:

Thanks for all the great information, but I have tried ALL of the above methods, many times, and get no further.  The error continues, even when I get positive confirmation of registration.  When I browse through the registry after the positive confirmation, the key that people sometimes had to delete is never there.  I was under the impression that registering it would create that key.

Even if that is a wrong way to double check, things like this batch file, even though giving positive results, I still cannot install my stupid verizon access manager.  I have worked with computers my whole life, and have never felt as helpless about fixing a problem as I do now.  Any further guidance would be greatly appreciated.

Thanks.

thanks man

Vodafone Mobile Connect Lite VMC Lite 9.4.4.19931 causes this problem on my Windows 7 Home Premium (32bit, Lenovo OEM) also. Vodafone could not help me. Regsvr32 I've run, HKCU doesn't contain the key, but problem still arises. I'm digging the net for correct solution. Can anybody help? Thanks a lot!

Mi proble es que tengo windows vista de 64 bits pero al momento de ejeuctar como administrador me sale C.windows \system32> y no C:windows \ SysWow64 > como me deberia salir ya que tengo de 64 bit.

Ayudenme gracias de antemano.............