-BlockedExecution pop-up does not show when Toolkit_TempPath is set to $envTemp

[LuHKae]

Describe the bug
Due to the fixes made for the security issue in 3.8.2 [Reserved CVE-2020-10962], the BlockedExecution-Window will not open, when a User tries to open a blocked app. Instead you will see an Error-Message from Windows Script Host.

To Reproduce
Steps to reproduce the behavior:

1. Deployment-Script with -BlockedExecution and -CloseApps in Show-InstallationWelcome
2. Open one of the blocked apps as user without admin rights
3. Run the Deploy-Script with admin rights
4. Close the blocked app, when prompt asks you to do
5. Try to reopen the blocked app as user without admin rights, while the script is still running
6. you will get an error message from Windows Script Host
7. Change <Toolkit_TempPath> in 'AppDeployToolkitConfig.xml' to $envSystemDrive\Users\Public
8. Redo Steps 2 - 4
9. Now the pop-up will be shown

Toolkit Version:
3.8.2

[luki1412]

Thank you for the report. Will look into it.

[luki1412]

This will be fixed in the next release.