-
Notifications
You must be signed in to change notification settings - Fork 511
Failed to start PowerShell Extension VsCode on Mac Ventura 13.3 M1 #4497
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hm, only interesting thing I spy is this:
Can you test if you can open any |
Yes, I can open any pwsh in this path, and I have permission to write and write on it! Leaving only in the user's root the problem also occurs equally. |
Interesting...anyway you can enable more logging and environment information by following these steps? Thanks! I'm especially interested in the server-side (PSES) logs. |
Hi @andschwa , |
Per that link you gotta run the command |
@andschwa |
HUH well, that indicates |
I'm copying this out of your log, what happens if you try to run from a regular terminal (outside of VS Code) the startup command it was trying:
That string is just these arguments encoded as base64:
|
Running the entire command by pwsh (outside VSC), it seems to work correctly, see below! `PS jcstorino > Import-Module '/Users/jcstorino/.vscode/extensions/ms-vscode.powershell-2023.3.3/modules/PowerShellEditorServices/PowerShellEditorServices.psd1'; Start-EditorServices -HostName 'Visual Studio Code Host' -HostProfileId 'Microsoft.VSCode' -HostVersion '2023.3.3' -AdditionalModules @('PowerShellEditorServices.VSCode') -BundledModulesPath '/Users/jcstorino/.vscode/extensions/ms-vscode.powershell-2023.3.3/modules' -EnableConsoleRepl -StartupBanner "PowerShell Extension v2023.3.3
VERBOSE:
DEBUG: Loaded into load context "Default" System.Runtime.Loader.DefaultAssemblyLoadContext #0: Microsoft.PowerShell.Security, Version=7.3.3.500, Culture=neutral, PublicKeyToken=31bf3856ad364e35
VERBOSE:
VERBOSE:
VERBOSE: Updated PSModulePath to: '/Users/jcstorino/.local/share/powershell/Modules:/usr/local/share/powershell/Modules:/usr/local/microsoft/powershell/7/Modules:/Users/jcstorino/.vscode/extensions/ms-vscode.powershell-2023.3.3/modules' https://aka.ms/vscode-powershell |
Even when the ...cause that's strange. If it's starting then it should also be starting when the extension tries the same thing. |
Yes! Even in this folder, the result is the same! It seems to work right! `PS VSC > pwd Path/Users/jcstorino/Library/Mobile Documents/com PS VSC > Import-Module '/Users/jcstorino/.vscode/extensions/ms-vscode.powershell-2023.3.3/modules/PowerShellEditorServices/PowerShellEditorServices.psd1'; Start-EditorServices -HostName 'Visual Studio Code Host' -HostProfileId 'Microsoft.VSCode' -HostVersion '2023.3.3' -AdditionalModules @('PowerShellEditorServices.VSCode') -BundledModulesPath '/Users/jcstorino/.vscode/extensions/ms-vscode.powershell-2023.3.3/modules' -EnableConsoleRepl -StartupBanner "PowerShell Extension v2023.3.3
VERBOSE:
DEBUG: Loaded into load context "Default" System.Runtime.Loader.DefaultAssemblyLoadContext #0: Microsoft.PowerShell.Security, Version=7.3.3.500, Culture=neutral, PublicKeyToken=31bf3856ad364e35
VERBOSE:
VERBOSE:
VERBOSE: Updated PSModulePath to: '/Users/jcstorino/.local/share/powershell/Modules:/usr/local/share/powershell/Modules:/usr/local/microsoft/powershell/7/Modules:/Users/jcstorino/.vscode/extensions/ms-vscode.powershell-2023.3.3/modules' https://aka.ms/vscode-powershell |
I Find some log files today.. But I don't know in what situation they were generated.. |
For information... @andschwa I tried in every way to find the problem, but I was unsuccessful. I had to do a clean installation of my MACOS and reinstall everything... Probably something related to MACOS permissions. Tks ! |
Of the whole OS?! That's so awkward but I'm so glad to hear it fixed things! |
🥹 yes... i maked a clean install... As I am not a specialist in Linux/Unix, search for the right permission that was causing the problem did not seem very simple to me... opting for reinstallation turned out to be more effective ! |
This issue was closed automatically as repro info was indicated as needed, but there has been no activity in over a week. Please feel free to reopen with any available information! |
Prerequisites
Summary
PowerShell extension not load...
`05/04/2023 11:35:44 [NORMAL] - PowerShell Editor Services args: Import-Module '/Users/jcstorino/.vscode/extensions/ms-vscode.powershell-2023.3.3/modules/PowerShellEditorServices/PowerShellEditorServices.psd1'; Start-EditorServices -HostName 'Visual Studio Code Host' -HostProfileId 'Microsoft.VSCode' -HostVersion '2023.3.3' -AdditionalModules @('PowerShellEditorServices.VSCode') -BundledModulesPath '/Users/jcstorino/.vscode/extensions/ms-vscode.powershell-2023.3.3/modules' -EnableConsoleRepl -StartupBanner "PowerShell Extension v2023.3.3
Copyright (c) Microsoft Corporation.
https://aka.ms/vscode-powershell
Type 'help' to get help.
" -LogLevel 'Normal' -LogPath '/Users/jcstorino/Library/Application Support/Code/User/globalStorage/ms-vscode.powershell/logs/1680705343-b7385f7a-9f47-4169-9977-ce5d2963e2861680705342975/EditorServices.log' -SessionDetailsPath '/Users/jcstorino/Library/Application Support/Code/User/globalStorage/ms-vscode.powershell/sessions/PSES-VSCode-66251-378352.json' -FeatureFlags @()
05/04/2023 11:35:44 [NORMAL] - pwsh started.
05/04/2023 11:35:44 [NORMAL] - Waiting for session file...
05/04/2023 11:36:14 [WARNING] - Loading the PowerShell extension is taking longer than expected. If you're using privilege enforcement software, this can affect start up performance.
05/04/2023 11:39:45 [NORMAL] - Timed out waiting for session file to appear!
05/04/2023 11:39:45 [ERROR] - PowerShell process failed to start:
05/04/2023 11:39:45 [ERROR] - Timed out waiting for session file to appear!
05/04/2023 11:39:45 [ERROR] - Unknown session status 'undefined' with reason 'undefined
`
PowerShell Version
Visual Studio Code Version
Extension Version
Steps to Reproduce
Just open VSC and wait for extension load.
Visuals
Logs
vscode-powershell.log
The text was updated successfully, but these errors were encountered: