Installer for 1.1.48 uses unsigned powershell script during installation

[b00rya]

Is there a way to sign it? Or avoid calling powershell whatsoever? Our security guidelines require DCs to have AllSigned execution policies.

Action start 15:44:15: CreateEventSource.
[INFO] PowerShell script preferred invocation folder: 
Dumping PowerShell invoke log ...
--> Found PowerShell path: C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe
--> PowerShell Script Execution Result Code: 1
--> PowerShell Script Execution log: 
File C:\Users\user\AppData\Local\Temp\pss869.ps1 cannot be loaded. The file 
C:\Users\user\AppData\Local\Temp\pss869.ps1 is not digitally signed. You cannot run this script on the current 
system. For more information about running scripts and setting execution policy, see about_Execution_Policies at 
https:/go.microsoft.com/fwlink/?LinkID=135170.
    + CategoryInfo          : SecurityError: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : UnauthorizedAccess
CustomAction CreateEventSource returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

[ryannewington]

Hi @b00rya, thanks for reporting this.

We've addressed this issue in v1.1.51