[ERR] PowerShell script content integrity check failed

[rmoc]

I installed the latest version 23.5.1 today and get the following error when running a PowerShell script.

MSI (s) (BC:98) [08:19:34:120]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI150B.tmp, Entrypoint: RunPowerShellScript
[INFO] PowerShell script preferred invocation folder:
Dumping PowerShell invoke log ...
--> Found PowerShell path:
--> PowerShell Script Execution Result Code: -1
--> PowerShell Script Execution log:
[ERR] PowerShell script content integrity check failed. The script may have been tampered with.
CustomAction UpdateSchedulerServiceParameter returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (BC:0C) [08:19:34:192]: Note: 1: 2265 2: 3: -2147287035
MSI (s) (BC:0C) [08:19:34:192]: User policy value 'DisableRollback' is 0
MSI (s) (BC:0C) [08:19:34:192]: Machine policy value 'DisableRollback' is 0


I tried to revert to version 23.4, but unfortunately I can't find a download link for this version. This is currently blocking my production pipeline.

[Liviu]

Hello,

To facilitate a more in-depth investigation of this issue, could you please email the .AIP (setup project) file and a download link to your setup package (built with v23.5.1) to support at advancedinstaller dot com?

You can download older versions from the bottom of your Customer Information web page:

https://www.advancedinstaller.com/custo ... ation.html

Best regards,
Liviu

[rmoc]

Hello Liviu

Attached is a test project with Powershell CustomAction.

PowerShell.zip

(6.65 KiB) Downloaded 11 times

Regards
René

[Liviu]

Hello René,

I have tested this and I can confirm that this indeed is a bug on our side.

I've forwarded this to our development team and a fix for this will be available as soon as possible. We will notify you when version 23.5.2 is released, either today or tomorrow.

Thank you for bringing this to our attention!

Best regards,
Liviu

[Liviu]

Hello René,

It appears that the bug is related to special character encoding used in a comment.

Can you please remove the "→" character or replace it with "->":

character.png (21.85 KiB) Viewed 1383 times

As this is not urgent we will hold the release for now.

Let me know if that helped.

Best regards,
Liviu

[rmoc]

Hello Liviu

The workaround seems to be working.

Kind regards
René,

[Liviu]

Hello René,

Thank you for your followup.

Best regards,
Liviu