Can’t install program on 2004 build

Topic

New Reply

Hi,
we have a program that sends emergency messages among workers and trying to install on a win10, 22004 build machine but the program won’t install on a bare bones, new computer with no AV.

Running the Sentinel logging program – log attached.

the first error states:
FullyQualifiedErrorId : UnauthorizedAccess
MSI (s) (A4!E8) [14:29:07:067]: PROPERTY CHANGE: Adding POWERSHELL_EXECUTION_LOG property. Its value is ‘File C:\Users\john.couey\AppData\Local\Temp\pssC41C.ps1 cannot be loaded.

The file C:\Users\john.couey\AppData\Local\Temp\pssC41C.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.

any ideas much appreciated.
thank you in advance

Reply | Quote

Replies

W10 2004 with no AV? it’s on by default IIRC after setup.
I’d check over the settings within Windows/Microsoft Defender, there may be something in there that’s preventing the PS execution.

Windows - commercial by definition and now function...

Reply | Quote

It looks like the default PowerShell execution policy needs to be changed.

Reply | Quote

thank you. I was thinking that too but the user states that the Powershell feature was turned off.

Reply | Quote

epanicbutton wrote:

thank you. I was thinking that too but the user states that the Powershell feature was turned off.

Given that PowerShell is baked in, I don’t know how to ‘turn it off’ unless you mean PowerShell 2.o (which can be removed from Windows 10 as a ‘feature’).

The error shows a PowerShell script (which looks like a temporary file created by a program installer) has not been allowed to run because it is unsigned. With no third-party AV involved as a blocking agent then that’s solely a PowerShell execution policy issue.

The program vendor’s support should be able to tell you what needs to be done to correct the ‘unsigned’ issue. This would be far safer than trying to amend the execution policy yourself.

Hope this helps…

Reply | Quote

epanicbutton wrote:

For more information about running scripts and setting execution policy, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.

Which execution policy is set, when you follow the instructions at that link to check?

Reply | Quote