Meelis Nigols

It might be connected to the Workspace Trust feature (of VS Code) introduced recently. I have added next configuration to my settings.json: ```json "extensions.supportUntrustedWorkspaces": { "ms-vscode.powershell": { "supported": true },...

> @peetrike Can you please clarify: do you have these projects marked "trusted" or "untrusted"? I have to assume "trusted" or the extension wouldn't/shouldn't be starting in the first place...

Yes, VS Code v1.61.1 + PowerShell extension v2021.10.0 still have same issue

The pwsh process that's left running is the one that is started by PowerShell extension to run it's functionality. Every next open of folder with PowerShell files opens next instance...

There will be as many processes as many times the PowerShell extension spawns new instance. It means that every time I open new folder (or open script in new window),...

The captured logs are here. Let me know if You need more. [1634625748-80020a2b-ead1-460a-8497-192267392d681634625746108.zip](https://github.com/PowerShell/vscode-powershell/files/7370904/1634625748-80020a2b-ead1-460a-8497-192267392d681634625746108.zip)

No change with that setting. Maybe because I have in my config: ` "powershell.integratedConsole.showOnStartup": false` I try to avoid using Integrated console as a terminal window. I prefer separate pwsh...

I removed config line `"powershell.integratedConsole.showOnStartup": false` and the problem ceased to exist. And now every time when I close project folder or script file (that triggered loading PowerShell extension), I...

Still the same. When I open folder and one PowerShell file, and then close the folder, the PowerShell Integrated Console protsess still remains in Process explorer. And when I open...

VS Code version 1.65.2, PowerShell Extension Preview version v2022.3.0