Powershell extension has not finished starting up yet. Please try again...

[TESTER-sec]

Prerequisites

• I have written a descriptive issue title.
• I have searched all open and closed issues to ensure it has not already been reported.
• I have read the troubleshooting guide.
• I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
• I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
• If this is a security issue, I have read the security issue reporting guidance.

Summary

When launching the PowerShell: Command Explorer, a notice appears every single time in the lower right corner and remains there until the user manually closes it...

"Powershell extension has not finished starting up yet. Please try again..."

This is a very long-standing issue that you people have never fixed. It has been reported countless times over the years. So maybe one of you should take us users who take the time to report this recurring stuff ad nauseum seriously and definitely solve this issue permanently once and for all? Hmmm?

If someone does not like my tone, well I'm not going to apologize for it. The team responsible for VSCode PowerShell extension has a very long tradition of dismissing user reports and not fixing stuff. What credibility it once had has long since been wasted due to the long list of things never fixed.

PowerShell Version

Name                           Value
----                           -----
PSVersion                      7.3.6
PSEdition                      Core
GitCommitId                    7.3.6
OS                             Microsoft Windows 10.0.22621
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Visual Studio Code Version

Version: 1.81.1 (system setup)
Commit: 6c3e3dba23e8fadc360aed75ce363ba185c49794
Date: 2023-08-09T22:22:42.175Z
Electron: 22.3.18
ElectronBuildId: 22689846
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Windows_NT x64 10.0.22621

Extension Version

v2023.6.0

Steps to Reproduce

1. Launch VSCode
2. Launch the PowerShell: Command Explorer

Visuals

No response

Logs

No response

[andyleejordan]

Hi @TESTER-sec, this is a warning that you must abide by our Code of Conduct to participate in this project. Thanks!

[andyleejordan]

There does not appear to be a bug here. It looks like the intended message is showing up when the Command Explorer button is used to activate the extension. Since it can take several seconds for the PowerShell process to initialize (mostly due to PowerShell startup time and users' profile activation, neither of which we have any control over) the message you see is displayed to inform the user why the Command Explorer is blank for a little bit. It can just be dismissed as you found with the X button. Your extension did start up correctly and the commands were populated, as indicated by your screenshot.

This is a very long-standing issue that you people have never fixed. It has been reported countless times over the years. So maybe one of you should take us users who take the time to report this recurring stuff ad nauseum seriously and definitely solve this issue permanently once and for all? Hmmm?

This is simply not the case (I struck through the unnecessary CoC violation here and am just responding to the first part). In fact, no prior issues have been reported about the (by design) display of this message, so this is not a long-standing issue. And as I explained above, there is no bug either. I think you are confused because there are a myriad of issues reporting bugs with "startup" nearly all of which are distinct and caused by unique issues, and we do our best to diagnose and fix each one.

Thanks! Marking this as resolved now. Please take the time to review the linked Code of Conduct before any further participation in Microsoft open source projects. Appreciate it!

[github-actions]

This issue has been marked as resolved and has not had any activity for 1 day. It has been closed for housekeeping purposes.

[mgabbard-lbce]

What does "Please try again" mean?

[allenhuffman]

I just installed PowerShell for Mac to try it out (using brew) and I am seeing this message as well. If I dismiss it, it comes right back when I try to click on the "PowerShell" (looks like a DOS prompt icon) on the left. ("PowerShell: Command Explorer")

I also get the message if I try to go to the commands and open "PowerShell: Show Addition Commands from PowerShell ..."

Does this extension not have any Settings panel, or is it truly just not loading up like the message says?

[modusCell]

Power-shell extension is not working "PowerShell extension has not finished starting up yet. Please try again in a few moments."

M3 Silicon Mac
macOS Sonoma 14.2.1 (23C71)
VScode Version: 1.85.1 (Universal)
Extension: v2024.0.0

[TESTER-sec]

There does not appear to be a bug here. It looks like the intended message is showing up when the Command Explorer button is used to activate the extension. Since it can take several seconds for the PowerShell process to initialize (mostly due to PowerShell startup time and users' profile activation, neither of which we have any control over) the message you see is displayed to inform the user why the Command Explorer is blank for a little bit. It can just be dismissed as you found with the X button. Your extension did start up correctly and the commands were populated, as indicated by your screenshot.

This is a very long-standing issue that you people have never fixed. It has been reported countless times over the years. So maybe one of you should take us users who take the time to report this recurring stuff ad nauseum seriously and definitely solve this issue permanently once and for all? Hmmm?

This is simply not the case (I struck through the unnecessary CoC violation here and am just responding to the first part). In fact, no prior issues have been reported about the (by design) display of this message, so this is not a long-standing issue. And as I explained above, there is no bug either. I think you are confused because there are a myriad of issues reporting bugs with "startup" nearly all of which are distinct and caused by unique issues, and we do our best to diagnose and fix each one.

Thanks! Marking this as resolved now. Please take the time to review the linked Code of Conduct before any further participation in Microsoft open source projects. Appreciate it!

I am not misunderstanding anything.

This ridiculous, vague notification has caused user confusion ad nauseum since it was introduced ages ago. What I do know is that reports, complaints, and questions about it have deliberately not been addressed over the years.

Just look at the responses here above: "What does 'Please try again.' mean?"

The person making the post does not know what the notification means. 99.999% of users don't know what it means. Now whether it is by design or not is irrelevant. It is poor design in the first place. It should be removed or the message given greater detail and phrased in a way that makes the intent/purpose of the notification clear.

LOL

[TESTER-sec]

Power-shell extension is not working "PowerShell extension has not finished starting up yet. Please try again in a few moments."

M3 Silicon Mac macOS Sonoma 14.2.1 (23C71) VScode Version: 1.85.1 (Universal) Extension: v2024.0.0

This issue was closed. Nobody from VSCode team is going to look at your comment. You have to create a new bug report. If you do I will add my comment above to it.

You will get the same response - that it is by design, and there is something wrong with us because we're confused and can't figure it out. Then they will close the report.

[TESTER-sec]

I don't know how I was put on the CC for this message, but please remove me. From: TEST @.> Sent: Friday, January 12, 2024 10:58 AM To: PowerShell/vscode-powershell @.> Cc: MATTHEW GABBARD @.>; Comment @.> Subject: Re: [PowerShell/vscode-powershell] Powershell extension has not finished starting up yet. Please try again... (Issue #4699) You don't often get email from @.@.>. Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification Security Checkpoint: External Email. There does not appear to be a bug here. It looks like the intended message is showing up when the Command Explorer button is used to activate the extension. Since it can take several seconds for the PowerShell process to initialize (mostly due to PowerShell startup time and users' profile activation, neither of which we have any control over) the message you see is displayed to inform the user why the Command Explorer is blank for a little bit. It can just be dismissed as you found with the X button. Your extension did start up correctly and the commands were populated, as indicated by your screenshot. This is a very long-standing issue that you people have never fixed. It has been reported countless times over the years. So maybe one of you should take us users who take the time to report this recurring stuff ad nauseum seriously and definitely solve this issue permanently once and for all? Hmmm? This is simply not the case (I struck through the unnecessary CoC violation here and am just responding to the first part). In fact, no prior issues have been reported about the (by design) display of this message, so this is not a long-standing issue. And as I explained above, there is no bug either. I think you are confused because there are a myriad of issues reporting bugs with "startup" nearly all of which are distinct and caused by unique issues, and we do our best to diagnose and fix each one. Thanks! Marking this as resolved now. Please take the time to review the linked Code of Conduct before any further participation in Microsoft open source projects. Appreciate it! I am not misunderstanding anything. This ridiculous, vague notification has caused user confusion ad nauseum since it was introduced ages ago. What I do know is that reports, complaints, and questions about it have deliberately not been addressed over the years. Just look at the responses here above: "What does 'Please try again.' mean?" The person making the post does not know what the notification means. 99.999% of users don't know what it means. Now whether it is by design or not is irrelevant. It is poor design in the first place. It should be removed or the message given greater detail and phrased in a way that makes the intent/purpose of the notification clear. LOL - Reply to this email directly, view it on GitHub<#4699 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AYRW6V72EELA3HXESQOJ2FLYOFMSBAVCNFSM6AAAAAA3PB4KOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBZGU2TOMJWHA. You are receiving this because you commented.Message ID: @.@.>> Re-THINK BEFORE YOU PRINT
…
________________________________ LINK-BELT IS COMMITTED TO REDUCE-REUSE-RECYCLE This e-mail is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. Any review, dissemination, copying, printing or other use of this e-mail by persons or entities other than the addressee is prohibited. If you have received this e-mail in error, please contact the sender immediately and delete the material from any computer.

If you post here, then you will receive an email notification. You have to go into to your own GitHub and configure it not to receive response notifications. Nobody can remove the CC for you. Only you can do that.

[mgabbard-lbce]

Oh, ok thanks. From: TEST ***@***.***> Sent: Friday, January 12, 2024 11:09 AM To: PowerShell/vscode-powershell ***@***.***> Cc: MATTHEW GABBARD ***@***.***>; Comment ***@***.***> Subject: Re: [PowerShell/vscode-powershell] Powershell extension has not finished starting up yet. Please try again... (Issue #4699) You don't often get email from ***@***.******@***.***>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> I don't know how I was put on the CC for this message, but please remove me. From: TEST @.> Sent: Friday, January 12, 2024 10:58 AM To: PowerShell/vscode-powershell @.> Cc: MATTHEW GABBARD @.>; Comment @.> Subject: Re: [PowerShell/vscode-powershell] Powershell extension has not finished starting up yet. Please try again... (Issue #4699<#4699>) You don't often get email from @.@.>. Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification Security Checkpoint: External Email. There does not appear to be a bug here. It looks like the intended message is showing up when the Command Explorer button is used to activate the extension. Since it can take several seconds for the PowerShell process to initialize (mostly due to PowerShell startup time and users' profile activation, neither of which we have any control over) the message you see is displayed to inform the user why the Command Explorer is blank for a little bit. It can just be dismissed as you found with the X button. Your extension did start up correctly and the commands were populated, as indicated by your screenshot. This is a very long-standing issue that you people have never fixed. It has been reported countless times over the years. So maybe one of you should take us users who take the time to report this recurring stuff ad nauseum seriously and definitely solve this issue permanently once and for all? Hmmm? This is simply not the case (I struck through the unnecessary CoC violation here and am just responding to the first part). In fact, no prior issues have been reported about the (by design) display of this message, so this is not a long-standing issue. And as I explained above, there is no bug either. I think you are confused because there are a myriad of issues reporting bugs with "startup" nearly all of which are distinct and caused by unique issues, and we do our best to diagnose and fix each one. Thanks! Marking this as resolved now. Please take the time to review the linked Code of Conduct before any further participation in Microsoft open source projects. Appreciate it! I am not misunderstanding anything. This ridiculous, vague notification has caused user confusion ad nauseum since it was introduced ages ago. What I do know is that reports, complaints, and questions about it have deliberately not been addressed over the years. Just look at the responses here above: "What does 'Please try again.' mean?" The person making the post does not know what the notification means. 99.999% of users don't know what it means. Now whether it is by design or not is irrelevant. It is poor design in the first place. It should be removed or the message given greater detail and phrased in a way that makes the intent/purpose of the notification clear. LOL - Reply to this email directly, view it on GitHub<#4699 (comment)<#4699 (comment)>>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AYRW6V72EELA3HXESQOJ2FLYOFMSBAVCNFSM6AAAAAA3PB4KOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBZGU2TOMJWHA. You are receiving this because you commented.Message ID: @.@.>> Re-THINK BEFORE YOU PRINT ...

…

________________________________ LINK-BELT IS COMMITTED TO REDUCE-REUSE-RECYCLE This e-mail is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. Any review, dissemination, copying, printing or other use of this e-mail by persons or entities other than the addressee is prohibited. If you have received this e-mail in error, please contact the sender immediately and delete the material from any computer. If you post here, then you will receive an email notification. You have to go into to your own GitHub and configure it not to receive response notifications. Nobody can remove the CC for you. Only you can do that. - Reply to this email directly, view it on GitHub<#4699 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AYRW6V77HFCYYVDJCP2ORYLYOFN2DAVCNFSM6AAAAAA3PB4KOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBZGU3TIMBYGE>. You are receiving this because you commented.Message ID: ***@***.******@***.***>>

[AScriver]

I've been running into this issue for the past week as well after VSCode crashed while the debugger was active. Honestly not sure what was causing it, but setting the extension to use Powershell Core (pwsh) instead of Desktop seems to have cleared it up on my end.

settings.json:

{
    "powershell.powerShellDefaultVersion": "pwsh",
    "powershell.powerShellAdditionalExePaths": {
        "pwsh": "\"C:\\Program Files\\PowerShell\\7\\pwsh.exe\""
    },
}