|
08-11-2015, 10:36 PM
|
#6 |
|
Junior Member
Join Date: Aug 2015
Posts: 3
|
OK...confirmed for my case, this was our Powershell security policy (setting Powershell Execution Policy to "AllSigned"). After getting the guys to security exclude me from the policy (reverting default Execution policy of "Remote Signed") - this installed no problem.
=steve |
|
|
|
|
Threaded Mode