VS Code Workspaces not showing up

[mkholt]

Microsoft PowerToys version

0.55.1

Running as admin

• Yes

Area(s) with issue?

PowerToys Run

Steps to reproduce

1. Update VS Code to a version > 1.64
2. Ensure Visual Studio Code Workspaces is enabled.
3. Trigger PowerToys Run
4. Search for a workspace by triggering (default: {)
5. Notice that no workspaces show up
   

✔️ Expected Behavior

A list of workspaces is shown

❌ Actual Behavior

Nothing is returned

Other Software

VS Code > 1.64

[franky920920]

cc: @ricardosantos9521

[franky920920]

Could you attach a full bug report file?
Right-click on the tray icon and click Report Bug. Then drag-and-drop the generated file into the GitHub comment to upload it. Thanks!

/needinfo

[mkholt]

PowerToysReport_2022-02-13-11-04-45.zip

[ricardosantos9521]

@mkholt can you try to exit powertoys and open it again? Also, close and open vscode. And if you can show me the workspaces that appear on your taskbar here

[suxscribe]

Same with VSCode 1.64 on Windows 10, PowerToys 0.55.2

[mkholt]

@ricardosantos9521, problem seems to be resolved by exiting powertoys and vscode.
I could swear I had done that before.

Attached is screenshot anyway for completeness.

[ricardosantos9521]

Same with VSCode 1.64 on Windows 10, PowerToys 0.55.2

@suxscribe can you try do the same

[suxscribe]

Same with VSCode 1.64 on Windows 10, PowerToys 0.55.2

@suxscribe can you try do the same

Exiting and reopening PowerToys helped, thank you!

[crutkas]

@ricardosantos9521 what caused it to need a restart?

[ziesemer]

Same issue here. Restarting PowerToys only (not VSCode) resolved it - and also curious as to why. The only thing that comes to mind is when it restarted from the 0.55.2 update, that it didn't initialize properly and needed the follow-up restart? (Looks like everyone here other than the OP is reporting being on the 0.55.2 version.)

[FWest98]

I just had this same issue - here too restarting solved it. I also noticed PT Run to be much snappier after the restart (before it would take seconds to load) - maybe that is related? Also on 0.55.2 here.

[mkholt]

After updating to 0.55.2 the issue re-occured until restart of PowerToys.
Something is definitely not getting initialized properly.

[crutkas]

@ricardosantos9521 any idea where the race condition could be?

[ricardosantos9521]

Yes @crutkas it could be the sqlitereader locking the file or something i will try to find sometimes to reproduce and fix the issue.

[ricardosantos9521]

Hi all @crutkas sorry for being too late. I have time today and found the issue and a fixe for it.
There's no concurrency happening.
The issue is with the first time that powertoys is installed or after an updated for some reason the first time we get Environment.GetEnvironmentVariable("PATH") only the system environment variables are obtained and not the user environment variables.
I fixed the issue by including the user variables to. Will do a pull request.
Regards,
Ricardo Santos

[sba923]

@ricardosantos9521 do you confirm that PowerToys Run VScode integration requires to have VScode on the PATH?

I don't, because I have an old habit not to add applications to the PATH at installation time, originally to speed up executable and DLL searches throughout the system, and also to make it easier to have multiple versions installed side-by-side (and choosing on a per-shell basis which one I want to use).

[ricardosantos9521]

@ricardosantos9521 do you confirm that PowerToys Run VScode integration requires to have VScode on the PATH?

I don't, because I have an old habit not to add applications to the PATH at installation time, originally to speed up executable and DLL searches throughout the system, and also to make it easier to have multiple versions installed side-by-side (and choosing on a per-shell basis which one I want to use).

Yes vscode path must be in the environment variables. Ussually during the installation vscode does this.

[sba923]

Yes vscode path must be in the environment variables.

Thanks for the confirmation.

Usually during the installation vscode does this.

It doesn't if you uncheck the box. Which I do, for the reasons described earlier.

[sba923]

Yes vscode path must be in the environment variables.

Thanks for the confirmation.

Ussually during the installation vscode does this.

It doesn't if you uncheck the box. Which I do, for the reasons described earlier.

[ziesemer]

At least for me, this is now working after upgrade, as tested with the 0.57.2 update that was just released.

[Aaron-Junker]

This got implemented/fixed in the 0.58 update.

[marktoman]

BTW the required path is not the root directory, which contains code.exe, but the bin subdirectory.

[golxzn]

Hi. I'm on the version 0.76.2 and still have the same issue. PowerToys reloading doesn't help as well as PATH environment manipulations, like removing the ending / from the VSCode bin directory.

PowerToys opens neither workspaces nor directories. VSCode has 1.85.1 (user setup) version.
I've been dancing with this issue for a 2 month as well. It's with me since few updates of each app.

Here's the bug report: PowerToysReport_2023-12-28-07-06-20.zip

[TheColorman]

Same issue that has been happening to me for a couple weeks now, VSCode insiders bin is on path, nothing shows up, I do have recent folders, all third partly plugins are disabled.
PowerToys v0.78.0.
Visual Studio Code - Insiders Version 1.87.0-insider (user setup).

Restarting neither PowerToys nor vscode does not fix the issue.

PowerToysReport_2024-02-06-21-24-10.zip

EDIT: Removing all "recently opened" in vscode seems to have fixed the issue? New folders I open now show up in PT Run.