"Recent Folders & Workspaces" shows named workspaces as "Untitled (Workspace)"

[LeCyberDucky]

Hi, I'm experiencing some trouble with using workspaces. When I save a workspace with a specific name, I used to be able to open it again from the "Recent Folders & Workspaces" section when righ-clicking VS Code or just searching for it in the Windows start menu. Now, however, any such workspaces that I create just show up as "Untitled (Workspace)". This behavior has only started within the last couple of weeks, I would say. I liked using this for launching VS Code in a specific workspace. This happens on the normal stable build of VS Code, but to be sure, I also downloaded a fresh copy of the newest insider build and managed to recreate the issue directly after installing it, without changing any settings or installing any extensions.

• VS Code Version: 1.54.3 (also tested on 1.55.0-insider)
• OS Version: Windows 10 build 19042.868

Steps to Reproduce:

1. Open VS Code as a New Window
2. File --> Save Workspace As...
3. Specify a name and save the workspace
4. Right-click VS Code in the task bar or search for it in the Windows start menu
5. See that a workspace with the name specified isn't listed under "Recent Folders & Workspaces". Instead, it is listed as "Untitled (Workspace)"

Does this issue occur when all extensions are disabled?: It occurs with a completely fresh insider build without any extensions installed.

I tired searching for similar issues, but I wasn't able to find anything similar, so I hope somebody can help me out with this, as this issue has turned out to be quite annoying. I'm happy to provide more information or perform further steps if needed.

[vscodebot]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• Consistency with the use of "workspace" (#77718)
• Can't start extension host process from duplicate workspace windows (#117269)
• Allow to open multiple workspaces in the same window (#43188)
• Set different versions of an extension by workspaces. (#117838)
• Leading slash on implicitly saved WSL workspace path (#117514)

[bpasero]

Can you try to run code-insiders --disable-extensions --user-data-dir <directory> where <directory> is an empty folder? This will ensure Code is starting with a fresh data directory, e.g. no specific settings and without any extensions running.

[bpasero]

Opening up for "help wanted" if someone can confirm on Windows.

[LeCyberDucky]

Thanks for getting back to me. I created an empty folder and did what you suggested, but the same thing happens. This first image shows what happens when I right-click VS Code in the taskbar before creating/saving my workspace:

The next image shows what I see after saving the workspace:

The name of the workspace I created is shown correctly at the top of VS Code: