The language service could not be started

[J0ska]

The language service doesn't start due to "-ExecutionPolicy Bypass" command line option is prohibited by antivirus policy.

vscode-powershell.log

Removing the code below fixed the problem

vscode-powershell/src/process.ts

Lines 79 to 82 in e45fd25

	// Only add ExecutionPolicy param on Windows
	if (utils.isWindows) {
	powerShellArgs.push("-ExecutionPolicy", "Bypass");
	}

vscode-powershell.log

Cheers

[corbob]

🤔 I wonder if there should be a setting to configure what Execution Policy is sent on startup? Naturally it might be difficult to build and debug locally if you're not locally signing code and you pick an Execution Policy other than Unrestricted or Bypass.

Out of curiosity @J0ska what anti-virus are you running?

[J0ska]

Right, softcoding the Execution Policy would be indeed ideal.

We use McAfee Endpoint Security. It is blocked by Exploit Prevention rule ID 6073 "Exection Policy Bypass in Powershell". By default it is disabled but in out set-up it's not :(

[SydneyhSmith]

Thanks @J0ska we may need to introduce a configuration setting for execution policy, it would great to know what you saw before taking that code out? A screenshot or GIF is even better--thanks!

[eskonr]

since the bypass is not allowed in the org and is being blocked by McAfee or Symantec or other AV tools, it is hard to get approval from security to byass and use visual studio code app.

Are there any progress made on this to fix the issue?

we have large number of users complaining on this.

[SydneyhSmith]

Thanks @eskonr we do plan to investigate this issue further in the next 6 months or so, and will have a better idea then, how/if we may be able to work around these AV tools...unfortunately these AV tools can be quite complex and unpredictable...in the meantime if you do have specifics about your environment and what you are seeing that you can share that is helpful.

[andyleejordan]

Whoops sorry this took so long to get it, it was a 5 minute fix to give you the option.

[andyleejordan]

Hi @J0ska @corbob @eskonr v2024.2.0 was just released that has the option powershell.developer.setExecutionPolicy you can use to workaround this! So sorry that this fell off our radar for so long, but we got it fixed!