VBScript deprecation: Timelines and next steps

We recommend migrating to PowerShell if you:

• Have websites or applications dependent on VBScript for automating tasks.

• Use VBScript custom actions as a feature in installer packages. During setup process, these custom actions can use the installation session and perform complex tasks. These custom actions may stop working after deprecation.

Windows Installer does not support PowerShell custom actions. Yes, you can call powershell.exe and pass a script, but there are 2 major hurdles:

1. Execution policy may not allow, and by default most Enterprise environments would have this disabled.
2. You cannot pass the installer session handle to another process. This installer handle is critical to read or update state in an installer. You basically, cannot create an effective custom action without the Session handle.

So, no PowerShell is not a viable alternative to VBscript for Windows Installer CAs.