Toast notifications enabled give Windows Script Host Error

The Toolkit General Discussion
1

I’m doing some testing to deploy apps with PSADT via Intune.
For certain apps we want to offer user interaction.

I’m now running into an issue.
When using PSADT v3.10 and having the option “Toast_Disable” set to “False” within the “AppDeployToolkitConfig.xml” to enable toast messages for the install process.
I’m getting an WSH error.
When “Toast_Disable” is set to “True” the issue doesn’t occur and the apps deploy like a charm, yet less fancy.

I can reproduce this by running the app deployment in “System Context” with ServiceUI.
i.e. “ServiceUI.exe -process:explorer.exe Deploy-Application.exe”

Is this a known limitation?

wsherror

2

I’m interested in what others come back with the solution to this (I have compared my PSADT 3.9.3 and 3.10.0 repos and it looks like Runhidden.vbs is new in v3.10.0)

As a side note; we too use Intune, but we would always want the Toast notifications disabled because we prefer to see just the Intune messages (Toast Notifications) appear in the notification area - the display of which can also be defined within each Intune deployment:

image
image1377×209 4.6 KB

If we had both Intune and PSADT Toast notifications enabled we found this was too much messaging for our users.

3

In another thread, it was determined that this bug was caused by the use of a certain function in RunHidden.vbs that required .NET 3.5. So, you can install .NET Framework 3.5 to address it, or you can upgrade to the new version of PSAppDeployToolkit (currently v3.10.2) where the VBScript has been updated to use a different approach that doesn’t require .NET 3.5.

1 Like
4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.