Powershell Execution Policy not "Remotesigned"?

Support for all customers who have purchased a PrimalScript product license. This forum does not offer a response time guarantee.
Forum rules
DO NOT POST SUBSCRIPTION NUMBERS, LICENSE KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.

Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
User avatar
jens.kalski@gv.hamburg.de
Posts: 13
Joined: Wed May 23, 2012 6:38 am

Powershell Execution Policy not "Remotesigned"?

Post by jens.kalski@gv.hamburg.de » Tue Jul 10, 2018 1:57 am

To help you better we need some information from you.

*** Please fill in the fields below. If you leave fields empty or specify 'latest' rather than the actual version your answer will be delayed as we will be forced to ask you for this information. ***

Product, version and build:
32 or 64 bit version of product:
7.4.114 64Bit

Operating system:
32 or 64 bit OS:
Windows 10 1803 64Bit

*** Please add details and screenshots as needed below. ***

DO NOT POST SUBSCRIPTIONS, KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM

Primalscript shows following in Tool Output, but Executionpolicies are "Remotesigned"

** Your Microsoft Windows PowerShell Script execution policy is set to "Restricted" on 32 bit and 64 bit **
For the PowerShell cache building process to execute, your execution policy must be at least set to "RemoteSigned"
Please exit and restart the application after changing the PowerShell execution policies for 32 and 64 bit

User avatar
Alexander Riedel
Posts: 6671
Joined: Tue May 29, 2007 4:43 pm

Re: Powershell Execution Policy not "Remotesigned"?

Post by Alexander Riedel » Tue Jul 10, 2018 6:23 am

Please provide the value of the property "ExecutionPolicy" in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell on your machine.
Alexander Riedel
SAPIEN Technologies, Inc.

User avatar
jens.kalski@gv.hamburg.de
Posts: 13
Joined: Wed May 23, 2012 6:38 am

Re: Powershell Execution Policy not "Remotesigned"?

Post by jens.kalski@gv.hamburg.de » Wed Jul 11, 2018 12:04 am

Hi,
there is no such value in the registry.

User avatar
Alexander Riedel
Posts: 6671
Joined: Tue May 29, 2007 4:43 pm

Re: Powershell Execution Policy not "Remotesigned"?

Post by Alexander Riedel » Wed Jul 11, 2018 7:48 am

According to Microsoft's documentation that should mean it is "Restricted"
Do you have a per user setting for the execution policy?
Alexander Riedel
SAPIEN Technologies, Inc.

User avatar
jens.kalski@gv.hamburg.de
Posts: 13
Joined: Wed May 23, 2012 6:38 am

Re: Powershell Execution Policy not "Remotesigned"?

Post by jens.kalski@gv.hamburg.de » Sat Jul 14, 2018 1:40 am

There was

Code: Select all

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Confirm:$False -Force -Scope CurrentUser
missing for the non-administrative Administratoraccount (UAC). After that it works. :roll:

User avatar
Alexander Riedel
Posts: 6671
Joined: Tue May 29, 2007 4:43 pm

Re: Powershell Execution Policy not "Remotesigned"?

Post by Alexander Riedel » Sat Jul 14, 2018 9:24 am

Where did you add that?
Alexander Riedel
SAPIEN Technologies, Inc.