Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build

Re:Microsoft Replaces Command Prompt with PowerShell in Late... by Corrado on Friday November 18, 2016 @10:00PM (#12991820)

I think the problem is that when you chmod a file it stays chmoded. With the Set-ExecutionPolicy I find that I have to do it every time I start a shell. I also run a lot of headless scripts (AWS cloud-init, services, etc.) and it's always a pain resetting everything every time. With Unix, I know that a script is executable or not, with PS I don't.

Also, I might not want every script to be executable. With Unix I can choose which ones are executable and by whom. With PS it's all or nothing. :/

[ Parent | on HN ]

Re:Microsoft Replaces Command Prompt with PowerShell in Late... by JeffreySnover on Friday November 18, 2016 @10:40PM (#12991946)

Yikes! - you shouldn't have to do Set-ExecutionPolicy every time you start a shell. Something is definitely wrong there.

Try doing a: Get-ExecutionPolicy -List to see what is setting it.

Then use -SCOPE on Set-ExecutionPolicy.

BTW - I hear you on the "only chmod the scripts you want" - that is a nice benefit of the Unix model.

Jeffrey Snover [MSFT]

[ Parent | on HN ]