Change the way Script Runner calls pre/post scripts so they are not blocked by WDAC

Maybe the issue could be solved by simply implementing the solution mentioned here:

Using the -file parameter to run a script, such as powershell.exe -file ./yourscript.ps1, also puts the script in interactive mode and under WDAC restriction. However, if you omit the -file parameter and run a script like this: powershell.exe ./yourscript.ps1, the script runs in non-interactive mode and full-language mode.

https://patchmypc.com/wdac-intune

Currently, the Cloud solution run the pre-install scripts like this: powershell.exe -file ./yourscript.ps1

This would be very useful for compliance with certain cybersecurity standards.