Impact of VBScript Deprecation in Windows 11 on PSADT Packages Using RunHidden.vbs

The Toolkit Toolkit Features
1

Hello,
With the recent announcements from Microsoft regarding the deprecation and imminent removal of VBScript support in Windows 11, I have a concern regarding the continued functionality of the PowerShell App Deployment Toolkit V3.10.*, particularly in our production environment.

We have a substantial number of packages deployed that are based on the PSADT V3.10.* template, and most of these make use of the RunHidden.vbs file. As I understand it, this script is utilized, especially when the Execute-ProcessAsUser function is called during the deployment process.

Given the upcoming changes in Windows 11:

  • Will packages relying on RunHidden.vbs encounter errors or failures if installed or executed on new Windows 11 devices where VBScript is no longer supported?
  • Is there a recommended workaround or migration path for environments with many production deployments using packages that reference RunHidden.vbs?
  • Are there any ongoing efforts within the toolkit to replace or rewrite the relevant functionality using technologies still supported by Windows (e.g., all-PowerShell solutions)?

Any advice or documentation references around managing this transition and ensuring application deployment remains seamless would be greatly appreciated.

2

I'm not too sure where you've been, but we're at PSAppDeployToolkit 4.1.0 and there's zero vbscript nonsense in it. I'd be moving all your packages to v4 and ditching the old v3 code ASAP.

1 Like
3

@Maaz1, you'll be fine for now.

VBScript is an optional add-on for Windows 11.
Your PSADT v3 packages should still work but you should stop making more of them

1 Like