Prism installation issue on Windows 11 24H2 due to missing VBScript dependencies
The problem
Prism cannot be installed and the following error is presented:
"Windows Script Host: 'there is no script engine for file extension *.vbs'"
Why does this issue occur?
The core reason for this issue is that VBScript has been phased in as an optional feature in Windows 11 24H2. While it is generally included by default, it may be disabled in cetrtain environments, particularly in managed or locked-down enterprise settings. The GraphPad Prism installer relies on VBScript for certain actions, and if it is unavailable, the installation cannot proceed.
Additional Context on VBScript
Microsoft is phasing in VBScript as a feature on demand (FOD) starting with Windows 11 version 24H2. Although VBScript is pre-installed by default to minimize disruption for existing applications, it can be disabled or removed in managed environments. this means that while most clean installations will have the VBScript engine available, it may not be enabled or accessible in all cases due to security policies or configurations.
What are workarounds?
To address this issue, users can temporarily enable VBScript by following these steps:
- Go to Start > Settings > System > Optional features.
- Select View features next to "Add an Optional feature".
- Type "VBSCRIPT" in the search dialog and check the box next to the result.
- Press Next to enable the feature.
If you have power users or system administrators, they can use PowerShell to check whether VBScript is enagled or disabled, enable or reinstall VBScript in that specific machine / image or temporarily enable VBScript only for installation, then disable.
More details on the issue in the Microsoft "VBScript deprecation: Timelines and next steps" blog.
Is there a fix?
GraphPad plans to address this issue in future versions of Prism by replacing the use of VBScript in the installer with alternatives like JavaScript and PowerShell. No specific timeline for this fix is available. However, the team will fix this problem before VBScript FODs is disabled by default.