We have 5 Custom Action VBscripts which do small tasks, but are a necessary part of the install process. The install program has worked fine for several years. As soon as we moved to Windows 7 (64 bit) we ran into permissions issues. See
http://www.advancedinstaller.com/forums ... =2&t=11719
Today, I ran our install MSI program on a Windows 7 machine. The install failed, the error message was, "Could not access VBScript run time for custom action" This same install had worked fine previously. The following web site
http://www.nitropdf.com/kb/article.aspx?id=10106
suggested deleting the registry for vbscript.dll and registering vbscript.dll. This solved the problem. I never figured why I needed to register the DLL.
While researching the problem could not access VBScript problem, I came across this blog
http://blogs.msdn.com/b/robmen/archive/ ... 36530.aspx
The blog says to avoid using VBScript or Jscript for custom actions.
With the problems we have had with Windows 7 and our custom actions, I wonder if you should move away from custom actions. What do you think? What are the alternatives?
What about a vbs script like Session.DoAction("ResolveSource")?
Thanks
Bob
FOLLOW US
Get the latest news in Application Packaging