GPO which sets "Bypass" execution policy causes extension to fail startup.

[cobdev]

Please fill in these details so that we can help you!

System Details

• Operating system name and version: Windows 10 CBB v1607
• VS Code version: 1.8.1
• PowerShell extension version: 0.9.0
• Output from $PSVersionTable:
  Name Value

---

PSVersion 5.1.14393.576
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.14393.576
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

Issue Description

"PowerShell could not be started, click 'Show Logs' for more details."

CapturedLogFiles.zip

Attached Logs

Follow the instructions in the README
about capturing and sending logs.

[daviwil]

Thanks for the report! I'll get this fixed for the patch update next week.

[daviwil]

@ftischhauser originally reported this in issue #119 so I'm sure he'll want to know when it's fixed.

[cobdev]

Thank you! You guys are awesome! From: David Wilson [mailto:notifications@github.com] Sent: Friday, January 20, 2017 9:01 AM To: PowerShell/vscode-powershell <vscode-powershell@noreply.github.com> Cc: Smith, Daniel P. <dpsmith@cob.org>; Author <author@noreply.github.com> Subject: Re: [PowerShell/vscode-powershell] GPO which sets "Bypass" execution policy causes extension to fail startup. (#454) Thanks for the report! I'll get this fixed for the patch update next week. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#454 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AKEC2sHYwtoxCMmH8OxdalSknUYBaxKOks5rUOhAgaJpZM4LphDs>.