compiled exe dependency on powershell locally

Use this forum to ask questions after your subscription maintenance expires or before you buy. Need information on licensing or pricing? Questions about a trial version? This is the right place for you. No scripting questions, please.
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.
vsammeta
Posts: 1
Last visit: Fri May 27, 2022 12:59 pm

compiled exe dependency on powershell locally

Post by vsammeta »

Hi,

We are considering buying Powershell Studio for compiling exe's for deployment on our customer endpoints. For security purposes, they want to disable powershell locally on those same end points. Once compiled, do the exe's still rely on powershell on the endpoint in order to run?

Thanks in advance for reading and replying!

-Vijay
User avatar
Alexander Riedel
Posts: 8042
Last visit: Wed Aug 10, 2022 8:15 pm
Answers: 12
Been upvoted: 25 times

Re: compiled exe dependency on powershell locally

Post by Alexander Riedel »

There is no compiler for PowerShell. That is why we call it 'Packager'.
So of course there is a dependency, the packaged code still requires a PowerShell engine to run.
Depending on the PowerShell version we are talking about, the executables can load a runtime containing a PowerShell version without the actual console.
That applies to PowerShell 7.x and above. For Windows PowerShell, it needs to be there. You could however just disable powershell.exe itself, thus preventing users from accessing the console.
Alexander Riedel
SAPIEN Technologies, Inc.