Marius Oloeru

Results 6 comments of Marius Oloeru

Extension Fails to start using PowerShell 7 if Windows PowerShell module path is above the PS7 module path in $PSMODULEPATH

![Screenshot 2024-10-04 125638](https://github.com/user-attachments/assets/34bd4447-e7e5-4f08-b6b0-67089ad8db1b) This is how terminal looks like

Extension Fails to start using PowerShell 7 if Windows PowerShell module path is above the PS7 module path in $PSMODULEPATH

![Screenshot 2024-10-04 134407](https://github.com/user-attachments/assets/4343103f-789b-4ac5-a51b-aa07e3182635)

Extension Fails to start using PowerShell 7 if Windows PowerShell module path is above the PS7 module path in $PSMODULEPATH

> Been having the same issue for the past week or so. Seems to only happen when switching the session to PS 5.1. My workaround is to switch the shell...

Extension Fails to start using PowerShell 7 if Windows PowerShell module path is above the PS7 module path in $PSMODULEPATH

> Thanks for the submission! The most common reason we've been seeing this lately is an antivirus program blocking or halting the execution of the PowerShell extension. Do you have...

Extension Fails to start using PowerShell 7 if Windows PowerShell module path is above the PS7 module path in $PSMODULEPATH

Hi, Anyone knows how can I trigger again that popup/dialog with adding a trust publisher when installing an extension? I mean the very first time when you install a extension...

Extension Fails to start using PowerShell 7 if Windows PowerShell module path is above the PS7 module path in $PSMODULEPATH

This is the trust publisher question which never ends when I press A: "Do you want to run software from this untrusted publisher? File C:\Users\MyUserName.vscode\extensions\ms-vscode.powershell-2022.11.0\modules\PowerShellEditorServices\Commands\PowerShellEditorServices.Commands.types. ps1xml is published by CN=Microsoft...